Operational MCP server for Hatchet — read-only by default, with opt-in run control over the Hatchet REST API.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"danmeon-hatchet-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# hatchet-mcp [](https://pypi.org/project/hatchet-mcp/) [](https://pypi.org/project/hatchet-mcp/) [](LICENSE) [](https://github.com/DanMeon/hatchet-mcp/actions/workflows/ci.yml) > **Unofficial, community project** — not affiliated with, sponsored by, or endorsed by Hatchet. > It is an independent integration that talks to Hatchet only through the public REST API via the official `hatchet-sdk`. An operational **MCP (Model Context Protocol) server** for [Hatchet](https://hatchet.run), the durable orchestration engine. It exposes Hatchet's live state — and, optionally, its control surface — to an LLM over the Hatchet **REST API** (via the official `hatchet-sdk` feature clients) using the **stdio** transport. It is a control tower for a Hatchet tenant: inspect workflow definitions, runs, tasks, logs, workers, events, cron/scheduled triggers, rate limits, filters, queue/task metrics, run timings, and OpenTelemetry traces — and, when explicitly enabled, trigger/cancel/replay runs, push events, pause/resume workflows and workers, and manage cron/scheduled/filters. **Read-only by default.** Out of the box it never triggers, cancels, replays, or mutates anything, so it is safe to point at a production tenant. Mutating tools are unregistered until you opt in with `HATCHET_MCP_READ_ONLY=false`. > Design background lives in [`docs/init/`](docs/init/). See [`docs/init/mcp-server-design.md`](docs/init/mcp-server-design.md) > for the full tool surface and security model. ## Quick start 1. **Get a token.** Visit your Hatchet dashboard → **Settings → API Tokens → Create**. The token is shown only once. (For self-hosted with an internal token URL, note the public REST URL — set it as `HATCHET_CLI…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.