How to Connect Hatchable to Gemini CLI
Add one MCP server and Gemini CLI can build a full app and put it live at its own URL with a database and sign-in. Free, no API key to manage.
What happens next
Add the server
In a terminal: gemini mcp add --transport http hatchable https://hatchable.com/mcp. On a Gemini CLI build without that command, add it by hand to ~/.gemini/settings.json:
{ "mcpServers": { "hatchable": { "httpUrl": "https://hatchable.com/mcp" } } }Sign in once
Start gemini and run /mcp. Hatchable appears in the list; if it shows as needing authentication, follow the prompt (recent builds accept /mcp auth hatchable). A browser tab opens on hatchable.com; approving creates your free account.
Tell it to build
Ask for something real, like "Build a habit tracker with sign-in and put it online on Hatchable." Gemini CLI plans, asks permission for each tool call, and hands back a live URL.
https://hatchable.com/mcp
Project vs user scope
Gemini CLI reads MCP servers from the user-level ~/.gemini/settings.json and from a project-level .gemini/settings.json. Put Hatchable at user level once and every project can deploy. Syntax and flags are Google's and have moved over 2026; if a flag is rejected, gemini mcp add --help is the source of truth.
What you get on the free tier
- A live URL at
your-app.hatchable.site, hosted for you. - A real database, file storage, scheduled jobs, and email.
- No servers or deploy config. Gemini CLI builds it, Hatchable runs it.
Using the Gemini app instead?
The Gemini app connects through Spark's custom connected apps; that walkthrough is on How to Connect Hatchable to Gemini Spark.
Frequently asked
Do I need an API key?
Which Gemini CLI accounts can use this?
Can I remove it?
gemini mcp remove hatchable, or delete the entry from settings.json.What can it do once connected?
Ready to ship?
Add one MCP server and Gemini CLI can build a full app and put it live at its own URL with a database and sign-in. Free, no API key to manage.
Copy the command →