Hatchable MCP
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).
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.
What you can do (tool surface)
Hatchable exposes 30+ tools. Highlights:
Project lifecycle — create_project, get_project, list_projects, fork_project, set_visibility, update_project Files — write_file, write_files, read_file, grep, list_files, patch_file, delete_file, import_file_from_url, upload_file Database — execute_sql, get_schema Deploy + observability — deploy, dry_run_deploy, run_function, run_code, view_logs, list_deployments, get_deployment, list_functions, list_cron_jobs Environment — set_env, list_env, delete_env Discovery — search_projects, search_documentation Each 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 Config
{
"mcpServers": {
"hatchable": {
"url": "https://hatchable.com/mcp"
}
}
}