homespun_guide — Homespun MCP Prompt

homespun_guide is one of 1 prompt on the Homespun MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke homespun_guide from your client

• Claude Code Homespun Prompt/homespun_guide run in your project directory
• Claude Desktop Homespun Prompt/homespun_guide ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Homespun Prompt/homespun_guide ~/.cursor/mcp.json
• VS Code Homespun Prompt/homespun_guide .vscode/mcp.json
• Zed Homespun Prompt/homespun_guide ~/.config/zed/settings.json
• Windsurf Homespun Prompt/homespun_guide ~/.codeium/windsurf/mcp_config.json
• Cline Homespun Prompt/homespun_guide ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Homespun Prompt/homespun_guide ~/.gemini/settings.json
• Grok Homespun Prompt/homespun_guide .mcp.json (in your project root)
• ChatGPT Homespun Prompt/homespun_guide Settings → Connectors → Advanced → Developer mode
• Claude.ai Homespun Prompt/homespun_guide Settings → Connectors → Add custom connector
• LangChain Homespun Prompt/homespun_guide pip install langchain-mcp-adapters

Homespun also offers 1 resource — data you attach as context, where a prompt is something you run.

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.