Proxyman Traffic Debugging And MCP Operations

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

• The MCP client launches Proxyman's bundled mcp-server over stdio. The bridge reads a local handshake and forwards calls to an authenticated localhost server in the running app.
• Never hardcode the HTTP port or token. Each client bridge lasts only while its stdin remains open.
• Flow tools use the active workspace's sidebar-backed traffic universe. That includes flows from regular folders and, when present, saved, pinned, imported, Atlantis, and remote-device sources; results are deduplicated across folders rather than limited to the selected folder.
• List/filter results are snapshots. A flow ID can disappear after a clear, import, source change, or restart.
• Some actions are platform-specific. System proxy, Terminal injection, Electron .app injection, and app control are primarily macOS operations. Trust live discovery on Windows and Linux.

Start Every MCP Session

1. Discover tools, resources, and prompts if the client exposes discovery.
2. Call get_version to verify the bridge reaches Proxyman.
3. Call get_proxy_status to learn recording state, proxy port, and SSL Proxying state.
4. Use the smallest read operation that establishes the target: get_flows, filter_flows, a status call, or the relevant list call.
5. Read detail using returned identifiers. Do not infer IDs from names or visible order.
6. Explain any mutation and its effect, obtain consent where required, call it, then verify with a read operation.

For tool selection, read MCP tool catalog. For multi-step tasks, read MCP workflows. For Breakpoint, Map Local, Map Remote, Scripting, or overlapping modification rules, read request and response rules. For built-in knowledge, read MCP resources and prompts.

Privacy And Consent

Keep Settings > MCP > Redact Sensitive Data Before Sending to AI enabled by default. It covers common secret headers, cookies, query values, JWTs, credentials, and secret-like body fields in MCP output.