A
licenseB
qualityB
maintenanceEnables 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.
47
MIT
Charles MCP Server
by heizaheiza
Related Servers
Alternatives to Charles MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Charles Proxy for HTTP traffic analysis, supporting incremental harvest, checkpoint timelines, and rich filtering tools.138MIT
- AlicenseNot gradedqualityCmaintenanceCaptures browser network traffic, analyzes API patterns, and exposes analysis tools through an MCP server for AI-assisted workflows.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze local or base64-encoded PCAP/PCAPng captures through bounded MCP tools for protocol summaries, conversations, DNS/HTTP/TLS/QUIC inspection, credential and beacon detection, entropy checks, filtering, and Zeek-compatible export.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceBridges AI assistants and network packet analysis by exposing Wireshark/TShark functionality through MCP, enabling PCAP investigation, protocol discovery, packet filtering, stream analysis, and live capture.MIT
- AlicenseAqualityCmaintenanceAn MCP server for parsing and analyzing HAR files, enabling AI assistants to inspect network traffic with automatic redaction of sensitive authentication headers.7MIT
TDQS
B3.4/5.0
Scored across 18 tools
Disambiguation3/5
There is significant overlap between tools for live vs. recorded traffic analysis, with multiple tools serving similar purposes but for different contexts (e.g., query_live_capture_entries vs. query_recorded_traffic, peek_live_capture vs. read_live_capture). However, descriptions help clarify the distinctions, such as cursor behavior and context-specific use cases, preventing complete confusion.
Naming Consistency4/5
Most tools follow a consistent snake_case pattern with descriptive verb-noun combinations (e.g., analyze_recorded_traffic, get_traffic_entry_detail). Minor deviations exist, such as 'filter_func' being less descriptive and 'charles_status' not fully adhering to the verb-noun structure, but overall naming is predictable and readable.
Tool Count4/5
With 18 tools, the count is slightly high but reasonable for a comprehensive Charles proxy server covering live capture, recorded traffic analysis, session management, and configuration. It avoids being excessive (under 25) and provides a well-scoped set for the domain, though some tools could potentially be consolidated.
Completeness5/5
The tool set offers complete coverage for Charles proxy operations, including starting/stopping live captures, querying and analyzing both live and recorded traffic, drilling into details, managing sessions and recordings, and configuring throttling and resets. No obvious gaps exist; agents can perform full lifecycle tasks from capture to inspection and management.
Maintenance
ActivityInactive
ResponsivenessWithin a week