Skip to content
Grok

hatchbox for Grok

com.pulsemcp/hatchbox

MCP server for Hatchbox Rails hosting — env var inspection, deploys, and process monitoring.

client:Grok transport:stdio runtime:npm

Install hatchbox in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "hatchbox": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hatchbox-mcp-server"
      ],
      "env": {
        "HATCHBOX_API_KEY": "<HATCHBOX_API_KEY>",
        "HATCHBOX_ACCOUNT_ID": "<HATCHBOX_ACCOUNT_ID>",
        "HATCHBOX_APP_ID": "<HATCHBOX_APP_ID>",
        "HATCHBOX_DEPLOY_KEY": "<HATCHBOX_DEPLOY_KEY>",
        "WEB_SERVER_IP_ADDRESS": "<WEB_SERVER_IP_ADDRESS>",
        "SSH_KEY_PATH": "<SSH_KEY_PATH>",
        "HATCHBOX_APP_NAME": "<HATCHBOX_APP_NAME>",
        "READONLY": "<READONLY>",
        "ALLOW_DEPLOYS": "<ALLOW_DEPLOYS>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

hatchbox in other clients