Skip to content
mcp/harbor

Claude Desktop Homespun Prompt/homespun_guide

How to: Claude Desktop Homespun homespun_guide

client:Claude Desktop transport:streamable-http prompt:homespun_guide

Add Homespun to Claude Desktop

  1. 01

    Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "homespun": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://homespun.dev/mcp"
      ]
    }
  }
}
  1. 02

    Save the file and restart Claude Desktop.

  2. 03

    homespun_guide is surfaced in the attachment menu, under the server's name. Unlike a tool, you invoke it deliberately — Claude Desktop will not call it for you.

  3. 04

    If it does not appear, check that Homespun is connected and that you are looking at its prompts rather than its tools.

Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs

Set these first

Homespun will not start until these are set, so it never reaches Claude Desktop.

  • HOMESPUN_API_KEY
  • HOMESPUN_URL
  • HOMESPUN_AGENT_NAME
  • HOMESPUN_REGISTER_SECRET

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.

Homespun MCP server