getproxykit/proxykit-mcp

Overview

MCP server that lets you control a local HTTP(S) debugging proxy through MCP hosts like Claude and Cursor. It wraps ProxyKit so you can intercept, inspect, and route traffic from within your AI assistant. Distributed as a Dockerfile, so it runs in a containerized environment.

Best for

Best for
Developers who want to drive a local HTTP(S) proxy from their MCP assistant.

Use cases

• Inspect and debug HTTP(S) requests from Claude or Cursor
• Route traffic through a local proxy for testing
• Control ProxyKit behavior via MCP tool calls

How to use

Tools exposed

• PROXYKIT_CONTROL_AUTH_TOKEN_FILE
• PROXYKIT_CONTROL_AUTH_TOKEN
• PROXYKIT_MCP_TIER
• PROXYKIT_ENGINE_URL
• proxy_status
• list_traffic
• get_request
• search_traffic
• list_mock_rules
• list_rewrite_rules
• list_chaos_rules
• list_scripts
• list_sessions
• get_session
• list_findings
• get_findings_summary
• list_environments
• list_paused_breakpoints
• list_rule_packs
• get_ca_status

Tested with

Claude Desktop, Cursor

Notes

MCP server that lets you control a local HTTP(S) debugging proxy through MCP hosts like Claude and Cursor. It wraps ProxyKit so you can intercept, inspect, and route traffic from within your AI assistant. Distributed as a Dockerfile, so it runs in a containerized environment.

0 stars on GitHub. Last updated 2026-09-11. Licensed MIT.

Use cases

• Inspect and debug HTTP(S) requests from Claude or Cursor
• Route traffic through a local proxy for testing
• Control ProxyKit behavior via MCP tool calls

Pros

• Works with any MCP-compatible host
• Leverages ProxyKit’s existing proxy capabilities
• Containerized via Docker for consistent setup

Cons

• No stars yet, likely early-stage
• Requires Docker and a ProxyKit setup
• Limited to HTTP(S) debugging scenarios

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.