Traffic inspection
List, filter, and explain captured HTTP requests without leaving the chat.
Claude Code + ProxyKit MCP
Let Claude Code read the traffic your app actually sends — real headers, real payloads, real failures — while it writes the fix.
Installation
Connect Claude Code
ProxyKit must be running so the engine writes its local control token — MCP talks to 127.0.0.1, never to the cloud.
Requirements
- ProxyKit desktop or CLI with a running engine
- Claude Code, restarted after the config change
Terminal
$
claude mcp add proxykit /Applications/ProxyKit.app/Contents/Resources/proxykit-mcp.mcp.json (project root)
{
"mcpServers": {
"proxykit": {
"command": "/Applications/ProxyKit.app/Contents/Resources/proxykit-mcp",
"env": {
"PROXYKIT_CONTROL_AUTH_TOKEN_FILE": "~/Library/Application Support/ProxyKit/control.token",
"PROXYKIT_MCP_TIER": "readonly"
}
}
}
}A project .mcp.json commits the server for everyone on the repo; claude mcp add configures it for you only.
- Start ProxyKit so the engine writes control.token.
- Run claude mcp add, or commit the .mcp.json block above to the repo root.
- Set PROXYKIT_MCP_TIER in the env block — readonly is the default.
- Restart Claude Code so it picks up the server.
Capabilities
What Claude Code can do with it
Tiered tools — start read-only, opt in to mutation and capture when you trust the workflow.
Rules & mocks
Create and validate mocks, rewrites, chaos rules, and assertions from conversation.
Sessions & replay
Compare sessions, replay requests, and run CI-style diffs against live endpoints.
Findings & redaction
Triage security findings and apply redaction suggestions to protect secrets.
Tiered permissions
Start read-only; opt in to mutate, capture, analysis, and replay per workspace.
Same engine as the UI
Every tool calls the local control API — no duplicated proxy logic in MCP.
Exposed tool groups
- tool
traffic.list / get / explain - tool
rules.list / create / validate - tool
mocks / rewrites / chaos / assertions - tool
sessions.list / compare / replay - tool
findings.list / triage / dismiss - tool
redaction.suggest / apply - tool
packs / codegen / export
Troubleshooting
When Claude Code does not see the tools
Both use the same command and env block. A committed .mcp.json gives every contributor the tools; claude mcp add keeps the configuration on your machine only.
Uninstall
- Run claude mcp remove proxykit, or delete the proxykit entry from .mcp.json.
- Restart Claude Code.
Other hosts
Claude Desktop · Cursor · Cline · Continue
Windsurf, Zed, and any other MCP host accept the same JSON — see the MCP overview.
Connect Claude Code to real traffic
Install MCP once. Debug, mock, and replay from your assistant.