removing one llm round-trip from a voice caddy — Bo Kendell — Portfolio MCP Resource

removing one llm round-trip from a voice caddy is one of 6 resources on the Bo Kendell — Portfolio MCP server. Connect the server and your client can attach it as context.

by client

How to attach removing one llm round-trip from a voice caddy from your client

• Claude Code Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy run in your project directory
• Claude Desktop Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/.cursor/mcp.json
• VS Code Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy .vscode/mcp.json
• Zed Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/.config/zed/settings.json
• Windsurf Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/.codeium/windsurf/mcp_config.json
• Cline Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy ~/.gemini/settings.json
• Grok Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy .mcp.json (in your project root)
• ChatGPT Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy Settings → Connectors → Advanced → Developer mode
• Claude.ai Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy Settings → Connectors → Add custom connector
• LangChain Bo Kendell — Portfolio Resource/removing one llm round-trip from a voice caddy pip install langchain-mcp-adapters

Other resources on this server

• profile
• Swarm
• this site
• Bagman
• making the site readable to agents

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.