Homespun

Connect Cursor to Homespun

Cursor, Windsurf, Cline and VS Code Copilot all configure MCP servers from a JSON file, and they all accept the same entry. Add the block below to your MCP configuration, reload the editor, and approve the sign-in when the client opens it.

  1. Open your MCP configuration

    In Cursor, open Settings and then MCP, and edit the servers JSON. Windsurf, Cline and VS Code Copilot each have an equivalent MCP servers file.

  2. Add the Homespun server

    Add an entry named homespun with type http and the hosted Homespun URL, then save the file.

    {
  "mcpServers": {
    "homespun": { "type": "http", "url": "https://homespun.dev/mcp" }
  }
}

  3. Reload and authorize

    Reload the editor so it picks up the new server. The client opens the Homespun sign-in the first time it calls the connector: sign in by email and approve the consent screen.

  4. Build and deploy

    Ask your editor's agent for the app you want. It deploys to Homespun and gives you back a shareable link, then keeps working on the app as you use it.

Any other client works the same way. Wherever an app asks for a remote or HTTP MCP server URL, give it https://homespun.dev/mcp: it advertises its own OAuth metadata, so the client discovers the sign-in flow by itself.

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.