← Back

Full control over your Hatchbox infrastructure — from chat

New

The Hatchbox MCP server is live in beta. Point Claude Code or Claude Desktop at your Hatchbox account, and it can read and act across all of it.

We built an MCP server for Hatchbox: @hatchbox/hatchbox-mcp, available on npm today.

This isn't a status-check bot. Claude can read and act across your whole Hatchbox account — apps, deploys, databases, servers, domains, env vars, logs — and cross-reference it against other tools you already have open in the same conversation, like GitHub.

What it looks like in practice

"Is my lumio-app running the latest code?"

Claude checks the commit Hatchbox has deployed, compares it against the latest commit on GitHub, and — if they've drifted — can trigger a deploy on Hatchbox to close the gap. One question, two systems, one answer, and an action if you want it.

What it covers

The server wraps Hatchbox's /api/v1 API with one tool per operation, so Claude can work across:

  • Apps & deploys — create, update, restart, deploy, toggle auto-deploy
  • Databases & backups — inspect app and cluster databases, create backups, attach/detach
  • Servers & clusters — inspect servers and the clusters they belong to
  • Domains & env vars — create, update, delete domains; manage environment variables
  • Logs — follow deploy, restart, and backup jobs through to completion

Every write operation is annotated so Claude (and you) can tell read-only calls apart from destructive ones before anything runs.

Setup

1. Get an API token. Log into Hatchbox, go to /api_tokens → New API Token, name it, and copy the value.

2. Point your MCP client at it. No install step — npx fetches and runs the package on demand.

Claude Code:

claude mcp add hatchbox -- npx -y @hatchbox/hatchbox-mcp

Then set HATCHBOX_BASE_URL and HATCHBOX_API_TOKEN for that server (see claude mcp add --help, or edit .mcp.json directly).

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "hatchbox": {
      "command": "npx",
      "args": ["-y", "@hatchbox/hatchbox-mcp"],
      "env": {
        "HATCHBOX_BASE_URL": "https://hatchbox.io/api/v1",
        "HATCHBOX_API_TOKEN": "your-token-here"
      }
    }
  }
}

HATCHBOX_BASE_URL is always https://hatchbox.io/api/v1 — the same for every account, not something you need to look up.

Every developer authenticates with their own Hatchbox API token. Nothing is shared across a team, and there's nothing for us to provision on our end.

A note on the token

Your API token has no scoping — it's effectively full access across your accounts, gated only by your subscription status. Treat it like a password: don't commit it, don't share it, and use your MCP client's env-var handling rather than pasting it into a prompt.

This is a beta

Claude Code support is done and verified end-to-end against production. Claude Desktop works today too, but only through the manual config above — a one-click install bundle is coming next.

That means the rough edges are still visible, and we'd rather hear about them now than after a wider release. If something's confusing, missing, or breaks, tell us — that's exactly what the beta period is for.

npm i @hatchbox/hatchbox-mcp