English Français العربية

io.github.ElliotPadfield/hatchet-mcp

Official registry AI and agents

Observe and operate Hatchet workflows from an AI agent — runs, logs, trigger, cancel, replay.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package hatchet-mcp
Claude Code 
claude mcp add hatchet-mcp -e 'HATCHET_CLIENT_TOKEN=<your hatchet_client_token>' -e 'HATCHET_API_BASE=<HATCHET_API_BASE>' -e 'HATCHET_TENANT_ID=<HATCHET_TENANT_ID>' -- npx -y hatchet-mcp@0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "hatchet-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "hatchet-mcp@0.1.1"
            ],
            "env": {
                "HATCHET_CLIENT_TOKEN": "<your hatchet_client_token>",
                "HATCHET_API_BASE": "<HATCHET_API_BASE>",
                "HATCHET_TENANT_ID": "<HATCHET_TENANT_ID>"
            }
        }
    }
}

Environment variables

  • HATCHET_CLIENT_TOKEN required secret Hatchet API token (a JWT). Encodes the server URL and tenant, so it is normally the only setting required.
  • HATCHET_API_BASE Override the API base URL. Self-hosters can point this at any Hatchet instance.
  • HATCHET_TENANT_ID Override the tenant id decoded from the token.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. hatchet-mcp
  2. Install
  3. Configuration
  4. Tools
  5. Safety
  6. Development
  7. Status

hatchet-mcp

An MCP server that lets AI agents observe and operate Hatchet workflows — status, runs, logs, workers, and metrics, plus trigger / cancel / replay.

Why: Hatchet has a great API but no MCP. This wraps it so agents (Claude Code / Desktop, etc.) can see and act on workflow state.

Install

Add this to your Claude Code / Claude Desktop MCP config:

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

Get the token from the Hatchet dashboard → API tokens. The token is a JWT that encodes the server URL and tenant, so it's the only required setting.

Configuration

VariableRequiredDescription
HATCHET_CLIENT_TOKENYesHatchet API token (JWT). Encodes the server URL + tenant, so it's normally all you need.
HATCHET_API_BASENoOverride the API base URL. Self-hosters can point this at any Hatchet instance.
HATCHET_TENANT_IDNoOverride the tenant id decoded from the token.

Self-hosting? Set HATCHET_API_BASE to your own Hatchet instance and it works anywhere.

Tools

Observability (read-only)
ToolDescription
whoamiShow the resolved Hatchet tenant + server URL and confirm the token works.
list_workflowsList workflow definitions for the tenant.
list_runsList workflow runs (with an optional lookback window and filters).
get_runGet the full detail of one workflow run — status, tasks, errors.
get_run_logsGet log lines for a task by its external id.
list_workersList workers and their status.
get_queue_metricsGet task/queue metrics for the tenant (queue health).
Actions (mutate live state)
ToolDescription
trigger_workflowTrigger a new workflow run by name with a JSON input payload.
cancel_runsCancel one or more runs/tasks by external id.
replay_runsReplay/retry one or more runs/tasks by external id.

Safety

The read tools (whoami, list_workflows, list_runs, get_run, get_run_logs, list_workers, get_queue_metrics) are non-destructive.

trigger_workflow, cancel_runs, and replay_runs mutate live state — their descriptions are prefixed MUTATES LIVE STATE so agents and users know they affect real runs.

The token grants full tenant access — treat it as a secret. Never commit it to source control.

Development

pnpm install
pnpm test    # vitest
pnpm build   # tsup -> dist/index.js

TypeScript / ESM, tested with vitest.

Status

v0.1.0 — all tools verified against Hatchet Cloud; works with self-hosted instances via HATCHET_API_BASE. trigger_workflow uses the stable /workflow-runs/trigger endpoint.

Frequently asked questions

What is io.github.ElliotPadfield/hatchet-mcp?

Observe and operate Hatchet workflows from an AI agent — runs, logs, trigger, cancel, replay.

How do I install io.github.ElliotPadfield/hatchet-mcp?

It runs on your machine. In Claude Code: claude mcp add hatchet-mcp -e 'HATCHET_CLIENT_TOKEN=<your hatchet_client_token>' -e 'HATCHET_API_BASE=<HATCHET_API_BASE>' -e 'HATCHET_TENANT_ID=<HATCHET_TENANT_ID>' -- npx -y hatchet-mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.ElliotPadfield/hatchet-mcp need an API key?

Yes. It expects HATCHET_CLIENT_TOKEN, which you set in its configuration.

Is io.github.ElliotPadfield/hatchet-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.ElliotPadfield/hatchet-mcp?

It is published by ElliotPadfield. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.