Proxyman Traffic Debugging And MCP Operations

Use Proxyman MCP as a local control plane for the running Proxyman app. Start read-only, identify the relevant captured flow or current state, then make only the change the user requested.

If Proxyman tools are unavailable, use proxyman-mcp-setup. If Proxyman is absent, use proxyman-download-setup. For target-specific HTTPS configuration, use proxyman-https-capture. For current product documentation, use proxyman-debugging-tools. For shell automation, use proxyman-cli.

Sources Of Truth

Use this order whenever sources disagree:

1. The connected server's tools/list, resources/list, and prompts/list for available MCP capabilities and exact schemas.
2. Current state returned by Proxyman status/list tools.
3. Built-in MCP resources for version-matched setup, CLI, and scripting guidance.
4. Official live documentation through proxyman-debugging-tools for GUI behavior and features beyond the built-in setup index.
5. The bundled references in this skill as an orientation map.

Never invent a tool, enum, parameter, rule ID, flow ID, file path, or command flag. The stdio bridge uses strict schemas.

Mental Model