MCP server

ProxyKit for AI assistants

The proxykit-mcp server exposes traffic, mocks, replay, and findings as MCP tools for Claude Desktop, Cursor, and any compatible host — backed by your local engine, not the cloud.

Install MCPDownload ProxyKitCLI reference →

Installation

Choose how to connect

One-click from the desktop app, or paste JSON into your MCP host. Uninstall anytime — we keep a backup of your config.

Requirements

Per-client setup guides

Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonClaude Code.mcp.json (project root)Cursor~/.cursor/mcp.jsonCline~/.vscode/cline_mcp_settings.jsonContinue~/.continue/config.json

One-click from ProxyKit

macOSWindowsLinux

Fastest — bundled proxykit-mcp binary

Open ProxyKit → Settings → MCP server. Pick your client and click Install — we write the config and point at the bundled binary plus your local control token.

  1. Start ProxyKit so the engine writes control.token.
  2. Settings → MCP server → enable MCP.
  3. Choose Claude Desktop, Cursor, Cline, or Continue.
  4. Click Install for [client], then restart that app.

Read-only tools are enabled by default. Opt in to mutate, capture, analysis, or replay tiers in Settings before installing.

Install in Cursor

Cursor

Paste JSON or use one-click from the desktop app

  1. Adjust paths for your OS (see manual configuration below).
  2. Save the file and restart Cursor (or reload the window).
  3. ProxyKit must be running with capture available.
~/.cursor/mcp.json
{ "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" } } } }

Getting started: Ask your assistant "List my latest captured traffic in ProxyKit" or "Explain the last 500 error".

Claude Desktopclaude_desktop_config.json
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json
{ "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" } } } }

Windows: %APPDATA%\Claude\claude_desktop_config.json · Linux: ~/.config/Claude/claude_desktop_config.json

Cline (VS Code)cline_mcp_settings.json
Cline
~/.vscode/cline_mcp_settings.json
{ "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" } } } }
Continueexperimental.modelContextProtocolServers
Continue
~/.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" } } } ] } }
CLI-only (proxykit-mcp on PATH)Headless engine + MCP without the desktop UI
macOSWindowsLinux
  1. Install the CLI: brew install getproxykit/tap/proxykit-cli (or download from release.proxykit.net).
  2. Start headless: proxykit start --headless --port 8888
  3. Point MCP at the proxykit-mcp binary from the same release.
Any MCP host — mcpServers.proxykit
{ "mcpServers": { "proxykit": { "command": "proxykit-mcp", "env": { "PROXYKIT_CONTROL_AUTH_TOKEN_FILE": "~/.config/ProxyKit/control.token", "PROXYKIT_MCP_TIER": "readonly,mutate,replay" } } } }

Token path matches proxykit doctor output on your platform.

Manual configuration referenceEnvironment variables and binary paths
All hosts
  1. command — absolute path to proxykit-mcp (bundled in ProxyKit.app or on PATH from CLI).
  2. PROXYKIT_CONTROL_AUTH_TOKEN_FILE — file written by the engine (never paste the token into MCP config).
  3. PROXYKIT_MCP_TIER — comma-separated: readonly, mutate, capture, analysis, replay.
  4. Optional PROXYKIT_ENGINE_URL — defaults to http://127.0.0.1:17171.
Default binary locations
# macOS (desktop app) /Applications/ProxyKit.app/Contents/Resources/proxykit-mcp # Windows (desktop app) C:\Program Files\ProxyKit\resources\proxykit-mcp.exe # Linux (desktop app) /opt/ProxyKit/resources/proxykit-mcp
Windsurf, Zed, Claude CodeAny MCP-compatible host
Generic

Most hosts accept the same mcpServers JSON shape as Cursor. Add the proxykit block from the Cursor example to your host's MCP config file and restart.

Claude Code: use claude mcp add or project .mcp.json — same command + env block.

Capabilities

What MCP can do

Tiered tools — start read-only, opt in to mutation and capture when you trust the workflow.

Traffic inspection

List, filter, and explain captured HTTP requests without leaving the chat.

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

  • tooltraffic.list / get / explain
  • toolrules.list / create / validate
  • toolmocks / rewrites / chaos / assertions
  • toolsessions.list / compare / replay
  • toolfindings.list / triage / dismiss
  • toolredaction.suggest / apply
  • toolpacks / codegen / export

Claude Desktop · Cursor · Claude Code · Cline · Continue · Windsurf · Zed · any MCP host.

FAQ

Frequently asked questions about MCP

Installation, safety, tiers, and troubleshooting for ProxyKit MCP.

proxykit-mcp is a Model Context Protocol server that exposes your local ProxyKit engine to AI assistants. Agents can inspect traffic, manage rules, run replay, and triage findings through structured tools instead of copy-pasting HAR files.

More help

General ProxyKit questions live on the main FAQ. Capture and certificate setup: docs.

Connect your agent to real traffic

Install MCP once. Debug, mock, and replay from Claude or Cursor.

Download ProxyKitTeam pricing →