MCP.Market

Hatchbox MCP server

by pulsemcp.com·com.pulsemcp/hatchbox·v0.1.3·80 stars
No reviews yet

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

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

80 stars

Reviews

Write one

Nobody has reviewed Hatchbox yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Hatchbox tools (6, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • checkDeploywrite action

    Check the status and progress of a deployment activity on Hatchbox. This tool retrieves real-time information about a deployment including its current status, build logs, and any error messages. Essential for monitoring deployments and troubleshooting failures. Example response: ✅ Deployment Status: completed Activity ID: 12345 Output: [2024-01-15 10:30:00] Pulling latest code from repository... [

  • deleteEnvVarswrite action

    Delete one or more environment variables from your Rails application on Hatchbox. This tool uses the Hatchbox API to remove environment variables, which will take effect on the next deployment. Useful for cleaning up deprecated configuration or removing sensitive data. Example response: Successfully deleted environment variables: OLD_API_KEY, DEPRECATED_FLAG 23 environment variables remaining. Use

  • getEnvVar

    Retrieve a specific environment variable from your Rails application running on Hatchbox via SSH. This tool connects to your server and reads the requested environment variable directly from the running puma process. Example response: RAILS_ENV=production Or if not found: Environment variable 'NONEXISTENT_VAR' not found Use cases: - Checking the current Rails environment (RAILS_ENV) - Verifying da

  • getEnvVars

    Retrieve all environment variables from your Rails application running on Hatchbox via SSH. This tool connects to your server and reads environment variables directly from the running puma process, providing a complete view of your application's runtime configuration. Example response: Environment variables (85 total): RAILS_ENV=production DATABASE_URL=postgres://user:password@localhost/myapp_prod

  • setEnvVar

    Set or update an environment variable for your Rails application on Hatchbox. This tool uses the Hatchbox API to modify environment variables, which will be applied on the next deployment. Changes do not take effect immediately - you must trigger a deployment after setting variables. Example response: Successfully set environment variable: FEATURE_FLAG_ENABLED=true Use cases: - Enabling or disabli

  • triggerDeploywrite action

    Trigger a new deployment for your Rails application on Hatchbox. This tool initiates a deployment using Hatchbox's deployment webhook system, which will pull code from your Git repository, build assets, run migrations, and restart the application servers. Example response: Deployment triggered successfully! Activity ID: 12345 Status: pending Use checkDeploy with activity ID "12345" to monitor prog

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan41 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Hatchbox compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
80
more than 95% of 28,706 servers

What its tools let an agent do: 2 read · 2 change · 1 delete · 1 run or deploy

Install Hatchbox in Claude Code, Cursor or VS Code

Runs npx -y hatchbox-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add hatchbox -- npx -y hatchbox-mcp-server
Add to Cursor

What the publisher says

From the Hatchbox repository's README, as published. We do not edit it. Read it on GitHub

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:

  1. Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
  2. Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
  3. Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
  4. Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
  5. Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
  6. Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.

Servers Available

Productionized Servers

These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.

The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/) by the publish-mcp-registry.yml workflow.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Hatchbox: common questions

Is Hatchbox MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Hatchbox safety report
How do I install Hatchbox?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Hatchbox need an API key?
Yes. The registry entry asks for HATCHBOX_API_KEY, HATCHBOX_DEPLOY_KEY.
Is Hatchbox maintained?
The last commit was 66 days ago (2026-08-30). The latest release is v0.1.3.
How does Hatchbox compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from pulsemcp.com →