Ship production MCP servers from any API. Point. Generate. Deploy.

Paste a repo, an OpenAPI spec, or a Postman collection. Hatch extracts every endpoint, generates typed tools, runs the test loop, and deploys to a versioned subdomain Claude Desktop and Cursor connect to instantly.

SOC 2 Type II HIPAA-ready deployments Self-hostable
⌂ acme-api / Endpoints
Regenerate Generate MCP →
Filters: Method ▾ Confidence ▾ Auth ▾ 47 endpoints · 38 selected · 6 low
GET /v1/users List all users users.js:24
POST /v1/users Create a user users.js:51
GET /v1/users/{id} Get user by ID users.js:78
PATCH /v1/users/{id} Update user users.js:112
DELETE /v1/users/{id} Delete user users.js:140
POST /v1/users/{id}/activate Activate account users.js:168
─── Possibly missed (review) ───
GET /v1/audit-log (uncertain — added) inferred
// HOW IT WORKS

From API to live MCP server in four steps.

No glue code. No hand-written tool schemas. No Docker, no Cloudflare workers, no auth proxy to babysit. Hatch handles the entire pipeline — ingestion, extraction, generation, testing, deployment.

01 · SOURCE

Connect your API

GitHub repo, OpenAPI URL, Postman collection, or raw docs. Branch + subpath supported for monorepos.

$ hatch new acme-api
github.com/acme/api
branch: main
02 · EXTRACT

Endpoints stream in

Every route, method, and schema appears live as Hatch reads the source. Low-confidence rows flagged for review.

scanning routes...
47 endpoints found
6 low confidence
03 · GENERATE

Typed tools, no edits

Hatch writes the tool name, input schema, HTTP template, and test cases per endpoint. Auto-fix loop on test failures.

generating tools...
38/38 tools generated
35 passing tests
04 · DEPLOY

Live on your subdomain

One click deploys to acme-api.mcp.hatch.dev. Versioned, rollback-able, ready for Claude Desktop.

deploying v4...
live in 12s
connected
// THE WORKBENCH

Engineer-grade primitives. No SaaS theatre.

A virtualized endpoint table that handles thousands of routes. Inline schema editors. A live job rail that follows you between pages. Designed for the developer who'd rather read JSON than a marketing landing page.

Inspect, edit, and regenerate any tool.

Each generated tool exposes its JSON Schema, HTTP template, and tests in tabs. Edit field descriptions inline. Hit ⌘↵ to regenerate the whole tool.

create_user ${env.BASE_URL}/v1/users
Schema HTTP Tests
{
"type": "object",
"description": "Create a new user record",
"properties": {
"email": {
"type": "string",
"format": "email",
"description": "Primary contact email"
},
"name": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"role": {
"type": "string",
"enum": ["admin", "member", "viewer"]
}
}

Live job rail.

Ingestion, extraction, generation, deploy — every long-running job streams its progress and logs into a rail that follows you across the app. No loading screens.

job_8f2c · generating
ETA ~38s
Ingest source 100%
Extract endpoints 100%
Generate tools 62%
Run tests
14:22:08 tool generated · list_users
14:22:11 tool generated · get_user
14:22:13 generating · update_user

Command palette everywhere.

Press ⌘K from any screen — projects, deploys, tool regeneration, rollbacks. Type > for actions, # for jobs, ? for help.

Keyboard shortcuts
// ONE-CLICK INSTALL

Connect to Claude Desktop in a single paste.

After deploy, Hatch generates a ready-to-use config for every major MCP client. The API key is masked until you reveal it, copied with one click, and rotates whenever you want.

● DEPLOYED v4 acme-api.mcp.hatch.dev
12s ago
Claude Desktop Cursor Raw JSON
{
"mcpServers": {
"acme-api": {
"url": "https://acme-api.mcp.hatch.dev/sse",
"headers": {
"X-Hatch-Key": "hk_••••••reveal"
}
}
}
}
// AVG GEN TIME
3m 42s
-18% w/w
// TOOLS GENERATED
142,381
+4.2k today
// P95 TOOL LATENCY
128ms
stable
// UPTIME · 30D
99.98%
healthy
// CAPABILITIES

Everything an MCP server needs. Nothing it doesn't.

Hatch ships with native primitives for the work you'd otherwise glue together: auth, schemas, testing, observability, versioning, and HIPAA-grade isolation.

Endpoint inference

Static + LLM-assisted route detection. Confidence-scored. Manual review for low-confidence rows.

Typed JSON schemas

Every tool input/output is a real schema. Edit field descriptions inline, regenerate on save.

HIPAA-ready isolation

Encrypted credentials store, audit-logged calls, BAA available. Single-tenant deploy on request.

Auto-fix test loop

Failed tests kick off a Claude-driven fix-and-retry. Most regenerations land green the first round.

Versioned deployments

Every deploy is a numbered version. Rollback in one click from the deployments timeline.

Themed public docs

Every server ships with a Stripe-style reference at .mcp.hatch.dev/docs. Same tokens. Zero white-label.

Real-time analytics

Calls, error rate, p95 latency, unique consumers — per tool, per server, per time range.

Webhook redeploys SOON

Auto-regenerate and redeploy on every push to main. Branch-scoped review environments.

┌─────────────────────────┐ │ <hatch /> │ └─────────────────────────┘

Ship the MCP server, not the boilerplate.

$ hatch new my-api