Connect any other AI to Homespun

Homespun's connector is a standard OAuth-protected Streamable HTTP MCP endpoint, not an integration built for one vendor. So there is no list of supported clients to be on: if your app speaks remote MCP, it works, including apps that did not exist when this page was written.

1. 1

   Find where your client adds a server

   Look for custom connectors, MCP servers, or integrations in its settings. Some clients use a settings screen, others a JSON or TOML config file. Either is fine.

2. 2

   Give it the Homespun server URL

   Wherever it asks for a remote or HTTP MCP server URL, give it https://homespun.dev/mcp. If it also asks for a transport, choose HTTP or streamable HTTP rather than SSE or stdio.

   https://homespun.dev/mcp
3. 3

   Sign in when it asks

   Leave every auth field blank. The endpoint advertises its own OAuth metadata, so the client registers itself and discovers the sign-in: you log in by email and approve the consent screen, and there is no API key or client secret anywhere.

4. 4

   Ask for an app

   Describe what you want. Your client calls the Homespun tools and hands you back a link to a real hosted app.

If your client has no remote-MCP option at all, nothing is lost: the Homespun CLI gives any coding agent the full command surface with no connector involved, and one pasted line sets it up.

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.