working-with-mcplisted

# Working with MCPProxy and MCP Tools ## Overview MCPProxy can be accessed two ways: 1. **MCP Tools** (`mcp__MCPProxy__*`) - When MCPProxy is configured as an MCP server in Claude Code 2. **HTTP API** (`curl http://localhost:8080/...`) - For debugging MCPProxy itself **This skill is for #1.** For debugging MCPProxy itself, use HTTP API approach sparingly. ## FIRST: Detect MCPProxy Connection **When user mentions MCPProxy or MCP tools:** - "check buildkite mcp" - "use slack mcp tools" - Any MCPProxy tool request **YOU MUST IMMEDIATELY:** 1. **Look at your available tools** (passive observation - don't run commands) 2. **Scan for tools starting with `mcp__MCPProxy__`** **Examples of what you're looking for:** ``` mcp__MCPProxy__retrieve_tools mcp__MCPProxy__call_tool mcp__MCPProxy__upstream_servers ``` **Decision:** - ✅ **See `mcp__MCPProxy__*` tools?** → MCPProxy is connected, use them - ❌ **Don't see `mcp__MCPProxy__*` tools?** → MCPProxy MCP server not connected **If tools are missing, IMMEDIATELY tell user:** > "MCPProxy MCP tools aren't available in this session. The MCPProxy MCP server isn't connected. > > Try the `/mcp` command and select MCPProxy to reconnect. Once reconnected, you'll have access to the `mcp__MCPProxy__*` tools." **DO NOT:** - Try bash commands like `claude mcp list` or `mcpproxy list-tools` - Try HTTP API with curl - Make multiple attempts with different approaches - Try to work around the issue **Missing `mcp__MCPProxy__*` tools = MCPProx