MCP Server that wraps mitmproxy and exposes it as a tool to any MCP client, allows your AI agents to inspect traffic,...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 42/100. no security policy. 3 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Fastest way to find out if mitmproxy-mcp belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add mitmproxy-mcp -- npx mitmproxy-mcpRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove mitmproxy-mcpNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ mitmproxy-mcp ← registers here
MCP Server that wraps mitmproxy and exposes it as a tool to any MCP client, allows your AI agents to inspect traffic, filter traffic, intercept & modify traffic, request reply, set global headers, and start/stop mitmproxy as needed.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: June 5, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.