charles-mcp
Related Servers
Alternatives to charles-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceHTTP(S) and WebSocket debugging proxy, like Proxyman or Charles, that AI agents drive over MCP: summarize captured traffic, read requests with secrets masked, diff a working request against a failing one, mock responses, set breakpoints and throttle the network.201MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that brings Reqable's captured HTTP traffic into Claude Code conversations, enabling querying, searching, waiting for, and analyzing requests without requiring Reqable Pro.7MIT
- AlicenseBqualityCmaintenanceIntegrates Charles Proxy with MCP clients to provide real-time and historical network traffic capture and structured analysis. It features a summary-first approach that filters noise and desensitizes data for efficient, low-token agent debugging and monitoring.18330MIT

ProxyKit-mcpofficial
AlicenseBqualityBmaintenanceMCP server for ProxyKit — drive a local HTTP(S) debugging proxy from Claude, Cursor, and any MCP host.50MIT- AlicenseBqualityBmaintenanceEnables AI agents to connect to Charles Proxy for live and historical traffic analysis, summary-first insights, request detail inspection, and data-driven mock creation via Map Local/Remote.47MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read, decode, and analyze traffic captured by Charles Proxy 5.2.2, covering live capture, saved session files, and body decoding across JSON, compressed, form, multipart, protobuf, and WebSocket payloads. It also supports reverse-engineering workflows that replay requests and mutate fields to determine which signature, timestamp, or token parameters the server actually enforces.3MIT
TDQS
Scored across 7 tools
The tools mostly target distinct inspection needs: status, compact listing, single request, single response, search, aggregate summary, and lifecycle events. Some overlap exists between list_requests, search_traffic, and watch_requests, but their descriptions clarify filtering, bounded search, and cursor-based event pulling respectively.
All names use consistent snake_case and a clear verb_noun pattern such as get_status, list_requests, get_request, and search_traffic. The set is predictable and easy to scan.
Seven tools is well-scoped for a traffic inspection server, covering listing, detail views, search, summary, status, and event watching without obvious redundancy. Each tool has a clear place in the inspection workflow.
The surface covers the core read-only inspection lifecycle, including status, captured requests, request/response details, search, summary, and live event polling. It lacks control or maintenance operations such as starting/stopping recording, clearing traffic, or exporting captures, but those may be intentionally out of scope.