Homespun

Connect Gemini to Homespun

Gemini CLI speaks streamable HTTP and discovers the sign-in from the server itself, so one command is the entire setup and there is no auth block to write alongside it.

This is Gemini CLI, not the Gemini app. The consumer Gemini app does not accept arbitrary custom MCP connectors: custom MCP arrived inside Gemini Spark against a curated set of partner connectors, and connecting an MCP server of your own is a Gemini Enterprise feature. There is no URL you can paste into the Gemini app to reach Homespun today, so if that is where you are, skip to Claude, which takes the connector URL directly and works on a phone.

  1. Register the connector

    Run the mcp add command. It writes the entry to ~/.gemini/settings.json, or to .gemini/settings.json if you would rather scope it to one project.

    gemini mcp add --transport http homespun https://homespun.dev/mcp

  2. Sign in

    The first call opens your browser on the Homespun sign-in: log in with your email magic link and approve the consent screen. Gemini CLI caches the token and refreshes it for you.

  3. Ask for the app you want

    Describe the app in your own words. Gemini builds it, deploys it to Homespun, and hands back a link you can open on any device and share with anyone.

No API key and no client secret: the connector advertises its own OAuth metadata and the client registers itself. If you would rather not use a connector at all, the Homespun CLI gives any agent the full command surface instead.

If something goes wrong

The two most common snags are a blocked pop-up (the sign-in opens in a new window) and a client that needs a restart before new tools show up. The full troubleshooting list covers the rest, and the docs site explains what a connection can and cannot do.

What to build first

Describe what you want in your own words and your AI builds it. If you would rather start from something proven, install one from the template gallery and change it from the chat.