Hatchbox
Operate and ship Rails apps on Hatchbox from the agent: inspect env vars, trigger deploys, and watch process health without leaving the terminal.
Overview
com.pulsemcp/hatchbox is an MCP server for the Operate phase that inspects Hatchbox env vars, triggers deploys, and monitors Rails app processes from your agent.
What is this MCP server?
- Hatchbox API MCP over stdio (hatchbox-mcp-server v0.1.2)
- Environment variable inspection for Rails apps on Hatchbox
- Deployment triggers via HATCHBOX_DEPLOY_KEY webhook flow
- Process monitoring tied to WEB_SERVER_IP_ADDRESS context
- Four required credentials: API key, account ID, app ID, deploy key
- Server version 0.1.2
- 4 required environment variables for full functionality
- npm package identifier hatchbox-mcp-server
Community signal: 70 GitHub stars.
What problem does it solve?
You run Rails on Hatchbox but waste time in the dashboard whenever env vars, deploys, or process health need a quick check.
Who is it for?
Indie Rails founders on Hatchbox who want agent-driven ops and launch triggers from Claude Code or Cursor.
Skip if: Teams on Vercel-only stacks, Kubernetes-heavy platforms, or hosts without a Hatchbox account and API key.
What do I get? / Deliverables
Your agent can query Hatchbox and kick deploy workflows with credentials you already use for hosting.
- MCP config with four required Hatchbox environment variables
- Agent tools for env inspection and deploy triggers
- Operational prompts that reference account and app IDs safely
Recommended MCP Servers
Journey fit
Hosting control belongs on the Operate shelf because day-two env, process, and infra tasks dominate after the app exists. Infra is the canonical subphase for server IPs, environment configuration, and long-running process visibility on Hatchbox.
How it compares
Hatchbox hosting MCP control plane, not a generic Dockerfile deploy skill or local Rails generator.
Common Questions / FAQ
Who is com.pulsemcp/hatchbox for?
Solo builders and small teams running Rails on Hatchbox who use MCP agents for deploy and infrastructure tasks.
When should I use com.pulsemcp/hatchbox?
Use it during operate and ship when you need env inspection, deployment webhooks, or process monitoring without opening the Hatchbox UI.
How do I add com.pulsemcp/hatchbox to my agent?
Add the stdio server with npx -y hatchbox-mcp-server and set HATCHBOX_API_KEY, HATCHBOX_ACCOUNT_ID, HATCHBOX_APP_ID, and HATCHBOX_DEPLOY_KEY in your MCP environment.