Back to Browse

Hatchet MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

hatchet-mcp is a well-structured MCP server for the Hatchet workflow API with proper authentication, clear permission scoping, and good security practices. The code properly handles credentials via environment variables, implements error handling that avoids token leakage, and uses input validation with Zod. Minor observations around error handling breadth and logging do not materially impact security. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 2 high severity). Package verification found 1 issue.

7 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Hatchet API token (a JWT). Encodes the server URL and tenant, so it is normally the only setting required.Required

Environment variable: HATCHET_CLIENT_TOKEN

Override the API base URL. Self-hosters can point this at any Hatchet instance.Optional

Environment variable: HATCHET_API_BASE

Override the tenant id decoded from the token.Optional

Environment variable: HATCHET_TENANT_ID

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-elliotpadfield-hatchet-mcp": {
      "env": {
        "HATCHET_API_BASE": "your-hatchet-api-base-here",
        "HATCHET_TENANT_ID": "your-hatchet-tenant-id-here",
        "HATCHET_CLIENT_TOKEN": "your-hatchet-client-token-here"
      },
      "args": [
        "-y",
        "hatchet-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

hatchet-mcp

CI npm version license: MIT

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.

Reviews

No reviews yet

Be the first to review this server!