Traffic inspection
List, filter, and explain captured HTTP requests without leaving the chat.
Continue + ProxyKit MCP
Continue talks to your local ProxyKit engine over stdio — traffic, rules, and findings as tools.
Installation
Connect Continue
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
- Continue, restarted after the config change
One-click from the desktop app
Settings → MCP server → enable MCP → choose Continue → Install. ProxyKit writes the config and points at the bundled binary plus your control token. Read-only tools are enabled by default; opt in to mutate, capture, analysis, or replay first.
~/.continue/config.json
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "/Applications/ProxyKit.app/Contents/Resources/proxykit-mcp",
"env": {
"PROXYKIT_CONTROL_AUTH_TOKEN_FILE": "~/Library/Application Support/ProxyKit/control.token",
"PROXYKIT_MCP_TIER": "readonly"
}
}
}
]
}
}- Start ProxyKit so the engine writes control.token.
- Open ~/.continue/config.json.
- Add the ProxyKit object to experimental.modelContextProtocolServers.
- Restart Continue.
Capabilities
What Continue 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 Continue does not see the tools
Start ProxyKit (or proxykit start --headless) so the control API listens on 127.0.0.1:17171. Run proxykit doctor in the CLI. Confirm PROXYKIT_CONTROL_AUTH_TOKEN_FILE points at the control.token file the engine wrote.
Uninstall
- Open ~/.continue/config.json.
- Remove the ProxyKit object from experimental.modelContextProtocolServers.
- Restart Continue.
Other hosts
Claude Desktop · Claude Code · Cursor · Cline
Windsurf, Zed, and any other MCP host accept the same JSON — see the MCP overview.
Connect Continue to real traffic
Install MCP once. Debug, mock, and replay from your assistant.