Proxyman MCP Proxyman released Proxyman MCP, a Model Context Protocol feature that lets AI assistants including Codex, Claude Code and Cursor inspect captured HTTP/HTTPS traffic and create debugging rules in the Proxyman macOS app. The integration runs an MCP HTTP server inside Proxyman on localhost with token-based authentication plus a stdio-based MCP CLI server that forwards commands to the app, and it ships with a Proxyman SKILL.md for AI agents. Proxyman advises keeping the "Redact Sensitive Data Before Sending to AI" option on for normal debugging. MCP Connect Codex, Claude Code, or Cursor to Proxyman MCP to inspect captured HTTP/HTTPS traffic and create debugging rules from your AI assistant. Proxyman MCP connects your AI assistant to the Proxyman macOS app running on your computer. Use it to inspect captured requests and responses, investigate failures, and create debugging rules. Keep Proxyman open and capture the traffic you want to investigate before asking your assistant to analyze it. 1. What is Proxyman MCP? Proxyman MCP Model Context Protocol is a feature that enables AI assistants Codex, Claude Code, Cursor, and other MCP-compatible tools to directly interact with the Proxyman macOS app. It allows AI to inspect HTTP traffic, create debugging rules, and control Proxyman - all through natural language conversations. The architecture consists of two components: - MCP HTTP Server - Runs inside Proxyman app on localhost with token-based authentication - MCP CLI Server - A stdio-based MCP server that AI tools connect to, which forwards commands to Proxyman Check out the Proxyman SKILL.md https://proxyman.com/docs/skill-md for your AI Agents ✅ Example Prompts - Show me the last 10 API requests to api.example.com - Create a breakpoint for all POST requests to /api/users - Export the failed request as a cURL command - Enable SSL proxying for .stripe.com - Create a new Script to change the status code, headers, body. - Create Map Local, Breakpoint Tools with given URL 2. Benefits | Benefit | Description | |---|---| | AI-Powered Debugging | Ask AI to analyze captured traffic, find specific requests, or explain API responses | | Hands-Free Rule Creation | Create breakpoints, map local/remote rules through conversation | | Faster Workflow | Export cURL commands, filter flows, and manage sessions without switching context | | Secure by Design | Localhost-only server with per-session token authentication | | IDE Integration | Works with Codex, Claude Code, Cursor and other MCP-compatible tools | 3. How to add Proxyman MCP 1. Enable MCP in Proxyman - Open Proxyman → Settings → MCP Tab - Turn on Enable MCP Server to start the MCP Server 2. Choose your MCP client: In Proxyman Settings → MCP, select Codex or Claude Code , then use Copy Command . For Cursor , choose Manual and add the displayed configuration to Cursor's MCP settings. 3. Use the setup below for your client and installation. The command generated by Proxyman uses the path of your installed app, which may differ from these examples. Keep Redact Sensitive Data Before Sending to AI turned on for normal debugging. Codex - Production Version: codex mcp add proxyman -- "/Applications/Proxyman.app/Contents/MacOS/mcp-server" - Setapp Version: codex mcp add proxyman -- "/Applications/Setapp/Proxyman.app/Contents/MacOS/mcp-server" Claude Code - Production Version: claude mcp add proxyman --transport stdio -- "/Applications/Proxyman.app/Contents/MacOS/mcp-server" - Setapp Version: claude mcp add proxyman --transport stdio -- "/Applications/Setapp/Proxyman.app/Contents/MacOS/mcp-server" Manual For Cursor and other MCP clients, add the configuration from Proxyman's Manual tab to the client's MCP settings. Select the configuration for your installed Proxyman app. These examples show the mcpServers entry: - Production Version: { "mcpServers": { "proxyman": { "command": "/Applications/Proxyman.app/Contents/MacOS/mcp-server" } }} - Setapp Version { "mcpServers": { "proxyman": { "command": "/Applications/Setapp/Proxyman.app/Contents/MacOS/mcp-server" } }} 1. Start using Proxyman MCP - Ensure Proxyman is running - Ask your AI assistant to interact with Proxyman, for example: "Show the latest requests to api.example.com." - If the client cannot find Proxyman, check that MCP is enabled and the configured app path is correct, then reconnect the client. If it connects but finds no flows, make a new request and use the missing-traffic checklist https://proxyman.com/docs/troubleshooting/i-couldnt-see-any-traffics-on-proxyman . 4. Available Tools The tables below list common tools. Your MCP client shows the full list of tools for your installed Proxyman version. See the Changelogs changelogs for more tools. Read-Only Tools | Tool | Description | |---|---| | get version | Returns Proxyman version and build number | | get proxy status | Returns recording state, proxy port, and SSL proxying status | | get flows | Lists captured HTTP/HTTPS flows with optional filters limit , host filter , method filter , status filter | | get flow detail | Returns full details of a specific flow including headers, body preview, query params, and cookies | | list rules | Lists all debugging rules breakpoints, map local, map remote, blacklist | | get ssl proxying list | Returns SSL proxying include/exclude domain lists | | get certificate status | Returns root certificate installation status | Write Tools | Tool | Description | Required Params | |---|---|---| | create breakpoint | Creates a breakpoint to pause/inspect matching requests | url pattern | | create map local | Returns custom responses for matching URLs | url pattern | | create map remote | Redirects requests from one URL to another | from url , to url | | create blacklist | Blocks requests matching a URL pattern | url pattern | | create scripting rule | Creates a Scripting rule with custom JavaScript | url , script content | | enable ssl proxying | Enables HTTPS decryption for a domain | domain | Session Control | Tool | Description | |---|---| | clear session | Clears all captured flows from current session | | toggle recording | Starts or stops traffic recording | Flow Operations | Tool | Description | |---|---| | export flow curl | Exports a captured request as a runnable cURL command | | filter flows | Advanced filtering with multiple criteria url, host, method, status, headers, body supporting AND/OR combinations | App Control | Tool | Description | |---|---| | open proxyman | Launches Proxyman if not running | | quit proxyman | Quits the Proxyman app | Changelogs MCP v3 Proxyman macOS ≥ 6.8.0 | Name | Description | |---|---| | get version | Get the current Proxyman macOS app version and build number | | get proxy status | Get current proxy status including recording state, port number, and SSL proxying status | | get flows | Get recent HTTP/HTTPS flows from Proxyman's active session data source | | get flow detail | Get detailed information about a specific flow including headers, body, query params, and cookies | | list rules | List all active debugging rules breakpoints, map local, map remote, blacklist, scripting, dns spoofing, network condition, whitelist | | get ssl proxying list | Get the current SSL Proxying configuration including enabled status and domain lists | | create breakpoint | Create a new breakpoint rule to pause and inspect/modify requests or responses matching a URL pattern | | create map local | Create a Map Local rule to return a custom response for matching requests | | create map remote | Create a Map Remote rule to redirect requests from one URL to another | | create blacklist | Create a Blacklist rule to block requests matching a URL pattern | | create scripting rule | Create a Scripting rule with custom JavaScript to modify requests/responses | | enable ssl proxying | Enable SSL Proxying for a specific domain to decrypt HTTPS traffic | | clear session | Clear all captured flows from the current session | | toggle recording | Start or stop recording HTTP traffic | | export flow curl | Export a captured HTTP request as a cURL command | | filter flows | Filter captured HTTP/HTTPS flows using advanced filter criteria | | get certificate status | Get the current status of Proxyman's root certificate | | install certificate | Install and trust the Proxyman root CA certificate | | uninstall certificate | Remove the Proxyman root CA certificate from the Keychain | | inject terminal | Launch a terminal app with Proxyman proxy environment variables injected | | get terminal manual command | Get a bash source command for manually setting proxy environment variables | | answer setup question | Answer setup questions about capturing HTTPS from iOS, Android, browsers, etc. | | search docs | Search the built-in Proxyman setup and troubleshooting doc index | | list setup workflows | List the supported setup workflows Proxyman MCP can guide users through | | list popular workflows | List popular setup workflows using Proxyman's curated fallback ranking | | open proxyman screen | Open a specific Proxyman guide or setup screen in the macOS app | | run guided setup | Run a one-click automation in Proxyman for browsers or Android emulators | | list reverse proxies | List configured Reverse Proxy entries | | create reverse proxy | Create a Reverse Proxy entry for localhost or custom local port routing | | generate code | Generate code from a captured HTTP flow in 18+ languages/frameworks | | create dns spoofing | Create a DNS Spoofing rule to redirect a hostname to a different IP address | | list dns spoofing | List all DNS Spoofing rules and their enabled status | | update dns spoofing | Update an existing DNS Spoofing rule | | get external proxy | Get the current External Proxy upstream proxy configuration | | set external proxy | Configure an External Proxy setting for a specific protocol kind | | toggle no caching | Toggle the No Caching feature strips cache-related headers | | inject electron | Launch an Electron app with Proxyman proxy configuration injected | | open proxyman | Launch the Proxyman macOS application | | quit proxyman | Quit the Proxyman macOS application | MCP v2 Proxyman ≥ v6.7.0 - Built-in knowledge base covering iOS, Android, browsers, terminal, VPN, localhost, and third-party libraries - New commands: answer setup question, search docs, list setup workflows, open proxyman screen, run guided setup, create reverse proxy - MCP resources and prompt templates for chat clients - Reverse proxy create/list support Security - The server binds to 127.0.0.1 only no network exposure - Per-session cryptographic token stored in ~/Library/Application Support/com.proxyman.NSProxy/mcp-handshake.json - The handshake file has 0600 permissions owner-only access - Sensitive data auth tokens, passwords, API keys is automatically redacted in responses