Deploy a Gemini CLI app to production
Gemini CLI is Google's open-source terminal agent — it edits files, runs commands, and supports MCP servers. Like every coding agent, it stops at working code. Launchmatic is the deploy step: one command (or one MCP tool call) from the repo Gemini wrote to a public URL with SSL and Postgres.
Why Launchmatic for Gemini CLI
Gemini CLI's free tier makes it a favorite for weekend projects — exactly the projects that stall at 'how do I host this?'. Launchmatic's free tier matches: no credit card, Nixpacks auto-detects whatever stack Gemini chose, and the MCP server closes the loop so the agent can ship its own work.
Deploy in 5 steps
- 1Run Gemini CLI in your project:
gemini. - 2When it's done, push to GitHub:
git init && git add . && git commit -m "init" && gh repo create --private --push. - 3Install the Launchmatic CLI:
npm i -g @launchmatic/cli. - 4Authenticate:
lm login. - 5Bind the repo:
lm init(single service) orlm monorepo init(workspace). - 6Deploy:
lm deploy— or register the MCP server (see snippet) and ask Gemini to deploy for you.
Add Launchmatic to `~/.gemini/settings.json` so Gemini CLI can deploy via MCP:
{
"mcpServers": {
"launchmatic": {
"httpUrl": "https://launchmatic.io/mcp"
}
}
}FAQ
Does Gemini CLI work with Launchmatic's MCP server?+
Yes — Gemini CLI supports remote MCP servers over streamable HTTP. Add https://launchmatic.io/mcp to mcpServers in ~/.gemini/settings.json and Gemini can deploy, read logs, and manage env vars as tool calls.
Ready to deploy?
Free to start. No credit card. Auto-SSL on custom domains, managed Postgres, and per-branch preview deploys included.
This guide is part of our complete vibe coding hosting guide — how to take any AI-built app to production.