Cursor

Deploy from Cursor Composer in 30 Seconds

Add Hatchable as a Cursor MCP server. Then ask Composer to deploy — you get a live URL and a database, free. Works with Composer 2.5's new agent loop.

Add Hatchable to Cursor → Or sign up first

What happens next

Step 1

Click "Add Hatchable to Cursor"

The button above opens Cursor's MCP installer with Hatchable pre-filled. Cursor 1.0+ handles OAuth automatically.

Step 2

Sign in with OAuth

Cursor opens a browser tab for Hatchable's OAuth. No account? That signs you up — free, no card.

Step 3

Open Composer and deploy

Open Composer (Cmd/Ctrl+I), pick the latest model (Composer 2.5 if available), and ask: "Build a daily standup notes app and deploy it on Hatchable." Composer calls the right MCP tools — live URL in under a minute.

MCP URL — Cursor 1.0+ installs via OAuth; older versions paste this into ~/.cursor/mcp.json
https://hatchable.com/mcp

What's on the free tier

  • Live URL at {slug}.hatchable.site the moment Composer calls deploy.
  • Postgres database, auth, file storage, scheduled jobs — wired in, no config.
  • Free forever for personal projects.
  • Custom domain? Builder plan, $12/mo flat. Composer can wire the DNS once you upgrade. Free projects stay on {slug}.hatchable.site.

Why pair Cursor with Hatchable instead of deploying to Vercel

Vercel and similar platforms expect a git repo and a build step. Cursor Composer writes code in your editor — pushing through git, framework configs, and deploy logs is friction Composer keeps tripping on. Hatchable removes the round-trip: Composer calls deploy directly over MCP, no git push, no framework config, no npm run build. Source files are production.

You stay in Cursor. Composer can read deploy logs, query the database, run functions — all without context-switching to a dashboard.

Works with the older "Composer" too

The MCP integration doesn\'t care which Cursor model you use. Composer 2.5 is faster at planning multi-step deploys, but Composer 1.x and even Cursor\'s chat mode can call the same MCP tools. Use whatever model you prefer.

Frequently asked

Do I need Composer 2.5?
No — any Cursor 1.0+ with MCP support works. Composer 2.5 is faster and better at multi-step plans, but the integration is identical.
What's the MCP transport Cursor uses?
Streamable HTTP with OAuth. Hatchable's MCP server speaks protocol version 2025-03-26 at https://hatchable.com/mcp.
Will it use my Cursor API key budget?
Yes — Cursor bills its own LLM calls as normal. Hatchable hosting is separate and free for personal projects.
Can I see my deployed project before going public?
Yes — every project is private by default. Ask Composer to inspect logs / run functions privately, then promote when you're ready.
Can I export my project later?
Your code is standard Node + Postgres with no lock-in, and every deploy is a real git commit.
My Cursor version is older — does it still work?
Pre-1.0 Cursor can still use Hatchable via manual MCP config in ~/.cursor/mcp.json with a bearer token from your API keys page. The OAuth deeplink only works on Cursor 1.0+.

Ready to ship?

Add Hatchable as a Cursor MCP server. Then ask Composer to deploy — you get a live URL and a database, free. Works with Composer 2.5's new agent loop.

Add Hatchable to Cursor →