The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Hatchable MCP listing page.
Build and host full-stack web apps and sites on Hatchable from any MCP client. Every project gets its own Postgres database, auth, storage, domains, and cron — plus a live URL in seconds. Free tier, no credits.
| Endpoint | https://hatchable.com/mcp |
| Transport | Streamable HTTP (MCP 2025-03-26) |
| Authentication | OAuth 2.1 with PKCE and Dynamic Client Registration (RFC 7591). Bearer fallback. |
| Registry | com.hatchable/hatchable |
| Homepage | hatchable.com |
| Docs | hatchable.com/docs |
This repo is a thin connector — Hatchable's code runs on our infrastructure, not yours. There's nothing to install locally. You configure the endpoint in your MCP client and sign in with OAuth (or a bearer token).
One command, OAuth handles the rest:
Don't have Claude Code? Install it here.
https://hatchable.com/mcp, and click Add.Works on Free (1 connector), Pro, Max, Team, and Enterprise. On Team/Enterprise, an owner adds it from Organization settings → Connectors.
https://hatchable.com/mcp under MCP Server URL, keep OAuth, tick the consent box, and click Create.Requires a Plus, Pro, Business, Enterprise, or Edu plan (Developer Mode prerequisite).
https://hatchable.com/mcp, and Save.Don't have Codex? Download it here.
Paste into ~/.cursor/mcp.json:
Grab your token from hatchable.com/console/settings?tab=api-keys after signing up (10 seconds, no credit card).
Open the Command Palette (Cmd/Ctrl + Shift + P).
Select Antigravity: Manage MCP Servers, then click View raw config.
Paste and save:
Reopen Manage MCP Servers, click Authenticate on the hatchable row, and approve on hatchable.com.
Don't have Antigravity? Download from Google — free, no credit card.
Any client that supports Streamable HTTP + OAuth will work. Configure https://hatchable.com/mcp as the endpoint and let the client handle the OAuth dance. Clients that only support bearer tokens should send Authorization: Bearer <API_KEY>, where the key comes from the console. Clients that send no auth at all will receive a pending key on first initialize that they can persist for future calls.
Hatchable exposes 30+ tools. Highlights:
create_project, get_project, list_projects, fork_project, set_visibility, update_projectwrite_file, write_files, read_file, grep, list_files, patch_file, delete_file, import_file_from_url, upload_fileexecute_sql, get_schemadeploy, dry_run_deploy, run_function, run_code, view_logs, list_deployments, get_deployment, list_functions, list_cron_jobsset_env, list_env, delete_envsearch_projects, search_documentationEach project ships with Node.js 20, a dedicated Postgres database, built-in auth (email + OAuth providers), cron scheduling, object storage, and email sending. See hatchable.com/docs for the full SDK and handler contract.
server.json — MCP Registry manifest (schema version 2025-12-11), also served at hatchable.com/server.json and hatchable.com/.well-known/mcp/server.json.smithery.yaml — Smithery submission config./.well-known/oauth-authorization-server/.well-known/oauth-protected-resourceBearer tokens are scoped per-account. You can rotate or revoke them in the console.
The Dockerfile in this repo is a thin stdio-to-HTTP proxy built on mcp-remote. It exists so registries and quality scanners that expect a runnable container (Glama, Smithery, etc.) can introspect the tool surface. End users don't need to build it — configure https://hatchable.com/mcp directly in your MCP client and let the client's native HTTP transport talk to the server.
MIT. See LICENSE.