Purpose
proxykit-mcp is the MCP (Model Context Protocol) server for ProxyKit, enabling Claude, Cursor, and any MCP host to drive a locally running ProxyKit HTTP(S) debugging proxy. Users can enter natural-language instructions in their editor to perform operations on real traffic that ProxyKit has already captured, such as "mock the checkout endpoint to fail half the time," "compare my last 500 captured requests against the baseline and summarize," "add 800 ms latency to /api/payments and replay that session."
Main capabilities
It exposes tool calls over stdio, and each tool call corresponds to an HTTP request sent to the engine control API on 127.0.0.1. The server itself does not store any traffic, nor does it communicate with anything outside the user's local machine.
Divided by permission tiers, there are 50 tools in total, grouped into five tiers:
- readonly (enabled by default) — read status.
- mutate — edit rules: create_mock_rule, update_mock_rule, delete_mock_rule, toggle_mock_rule, create_mock_from_request, create_rewrite_rule, update_rewrite_rule, delete_rewrite_rule, toggle_rewrite_rule, create_chaos_rule, update_chaos_rule, delete_chaos_rule, toggle_chaos_rule, attach_environment.
- capture — control capture: start_capture, stop_capture, clear_traffic, release_breakpoint.
- analysis — AI and analysis workflows: analyze_request, rescan_findings, dismiss_finding, restore_finding, propose_redaction_rules, run_ai_workflow, compare_sessions.
- replay — sessions, replay, and rule packs: start_session, stop_session, delete_session, replay_session, replay_request, import_rule_pack, install_rule_pack, export_rule_pack, delete_rule_pack.
How to use
The binary is distributed with every ProxyKit CLI archive and desktop app; choose either one.
After installing via Homebrew (CLI), proxykit, proxy-engine, and proxykit-mcp will appear in PATH. On Windows, it can be installed via WinGet. It is also available from the desktop app, with the binary bundled inside the app (download link:https://proxykit.net/download）。
When connecting to an MCP host, the engine writes a control.token file at startup; point the MCP server at that file and do not paste the token into the configuration. Add the corresponding configuration to the host's MCP config (such as ~/.cursor/mcp.json, Claude Desktop's claude_desktop_config.json, .mcp.json, etc.). Then start ProxyKit (desktop app or proxykit start --headless), restart the MCP host, and you can have it execute "list my recently captured traffic in ProxyKit." The specific paths for each client and the desktop app's one-click installation method are documented in https://proxykit.net/mcp。
Official website:https://proxykit.net；设置指南（所有主机）：https://proxykit.net/mcp；CLI Reference:https://proxykit.net/docs。
Security and limitations
The server is local-only: it calls 127.0.0.1:17171, and the engine binds to the loopback address and rejects non-loopback callers. Access is token-constrained: every control call carries X-Proxykit-Control-Token, and without a token there is no access. Permissions are minimized by tier: readonly is the default and can only read; any operation that modifies rules, controls capture, or replays traffic remains disabled until you explicitly allow that tier, so an agent cannot create mocks or clear captures without your authorization. Response bodies are redacted server-side before reaching the agent. The remaining tiers are selectively enabled via PROXYKIT_MCP_TIER.
Licensing
This repository (documentation, Dockerfile, registry metadata) is licensed under MIT and may be freely reused. ProxyKit itself—the proxykit-mcp binary and the engine it drives—is proprietary software (© 2026 Seyed Ahmad Sarollahi), licensed under its own terms (https://proxykit.net/terms#license）。本仓库不授予 Any rights to the ProxyKit software; the binaries are downloaded at build time from the distribution server under their own terms.
