MCP.so
ログイン

Hatchet MCP Server

@ElliotPadfield

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

トランスポート

stdio

作者

ElliotPadfield

投稿者

Elliot Padfield

Hatchet MCP Server について

MCP server for Hatchet — let AI agents observe and operate your workflows: runs, logs, workers, metrics, plus trigger/cancel/replay. Single-token setup, npx-installable.

Hatchet MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "hatchet": {
      "command": "npx",
      "args": [
        "-y",
        "hatchet-mcp"
      ],
      "env": {
        "HATCHET_CLIENT_TOKEN": "<your-hatchet-api-token>"
      }
    }
  }
}

Hatchet MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Hatchet MCP?

Hatchet MCP is a server that allows AI agents, such as Claude Code or Claude Desktop, to observe and operate Hatchet workflows. It wraps the Hatchet API to provide status, runs, logs, workers, and metrics, plus the ability to trigger, cancel, and replay runs.

How to use Hatchet MCP?

Add the server to your MCP configuration using npx -y hatchet-mcp with the required environment variable HATCHET_CLIENT_TOKEN (obtained from the Hatchet dashboard under API tokens). Optionally set HATCHET_API_BASE for self-hosted instances and HATCHET_TENANT_ID to override the tenant decoded from the token. Once configured, agents can invoke the provided tools to interact with Hatchet workflows.

Key features of Hatchet MCP

  • Read-only observability tools for workflows, runs, logs, workers, and queue metrics
  • Action tools to trigger, cancel, and replay workflow runs
  • Single environment variable (HATCHET_CLIENT_TOKEN) encodes server URL and tenant
  • Works with Hatchet Cloud and self-hosted instances via HATCHET_API_BASE
  • Built with TypeScript and ESM, tested with vitest

Use cases of Hatchet MCP

  • Monitor workflow run status, tasks, and errors via an AI assistant
  • Trigger new workflow runs by name with a JSON input payload
  • Cancel or replay one or more runs or tasks by external ID
  • Inspect worker health and queue metrics to assess system load
  • Debug tasks by fetching log lines during incident response

よくある質問

1

How do I get the HATCHET_CLIENT_TOKEN?

Obtain the token from the Hatchet dashboard under API tokens. It is a JWT that encodes the server URL and tenant, making it the only required setting.

2

Can I use Hatchet MCP with a self-hosted Hatchet instance?

Yes. Set the `HATCHET_API_BASE` environment variable to point at your own Hatchet instance and the server will work anywhere.

3

Which tools modify live state?

The tools `trigger_workflow`, `cancel_runs`, and `replay_runs` mutate live state. Their descriptions are prefixed with “MUTATES LIVE STATE” so agents and users know they affect real runs.

4

Is the token safe to share or commit?

No. The token grants full tenant access; treat it as a secret and never commit it to source control.

5

What is the current status of the package?

Version 0.1.0. All tools have been verified against Hatchet Cloud and work with self-hosted instances. The `trigger_workflow` tool uses the stable `/workflow-runs/trigger` endpoint.

コメント

「開発者ツール」の他のコンテンツ