Pinned Tweet
1/ Full control over your Hatchbox infrastructure — from chat.
We built an MCP server for Hatchbox. It's live in beta today.
Hatchbox.io retweeted
If you noticed your @hatchboxio auto-deploys not running, GitHub's having issues with webhooks again. 🤷♂️
Hatchbox.io retweeted
We've had a number of successful migrations from Heroku over to @hatchboxio using the skill that ships with our MCP server. Check it out here: github.com/hatchboxio/hatchb…
Hatchbox.io retweeted
You can now deploy Campfire to your @hatchboxio cluster in a single prompt with our MCP. 🎉
The only upstream change I had to make was to support the REDIS_URL env var which is now merged.
Hatchbox.io retweeted
I'm jumping on @remote_ruby to talk @GoRails and the plan forward for @hatchboxio. Anything you guys want us to cover?
Hatchbox.io retweeted
Replying to @collin_jilbert @hatchboxio
we just switched over from Heroku and more than once, someone on my team has said "support from Hatchbox has been amazing".
So thank you for the great support and product!
Hatchbox.io retweeted
You can use build and deploy scripts from your Git repo with @hatchboxio. Keep them version controlled and organized with everything else. 👍
Hatchbox.io retweeted
Small ship from bed in London, kids finally asleep: trips.joelgaff.com → cucamonga.app. DNS in Cloudflare, hostname allowlist patched on GitHub mobile, @hatchboxio auto-deployed. This is what Rails 8 + Hatchbox + a phone can do in ~15 minutes.
My inbox was a mess of travel confirmations and I could never find anything.
Flight confirmations. Hotel bookings. Car rentals. All buried.
So I built trips.joelgaff.com — forward any confirmation email and it builds your itinerary automatically.
6/ It's in beta — Claude Code is fully wired up, Claude Desktop works via manual config today (one-click install coming next).
Rough edges may still be visible.
hatchbox.io/announcements/11…
5/ Every developer authenticates with their own Hatchbox API token. Nothing shared across a team, nothing for us to provision.
4/ What it covers:
Apps & deploys | Databases & backups | Servers & clusters | Domains & env vars | Logs
One tool per operation, each flagged read-only or destructive, so Claude — and you — always know what's safe before it runs.
3/ Example:
"Is my lumio-app running the latest code?"
Claude checks the commit Hatchbox has deployed, compares it to the latest commit on GitHub, and triggers a deploy to close the gap if it's behind.
One question, two systems, one action.
2/ Some "AI + infra" tools stop at status checks: "is my app up?"
This one reads AND acts. Claude can inspect and operate your whole Hatchbox account — apps, databases, servers, domains, logs — and actually run the deploy, not just tell you one is needed.
Hatchbox.io retweeted
Teaser of what we've been working on @hatchboxio











