Skip to main content
Glama
ExQA

Charles MCP Server

by ExQA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Charles MCP Server

No user-submitted related servers found.

    Related Servers

    • Charles MCP Server

      heizaheiza
      A
      license
      B
      quality
      B
      maintenance
      Integrates 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.
      18
      64 PyPI
      312
      MIT

    • proxypin-mcp

      k186
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to analyze real-time HTTP(S) traffic captured by ProxyPin, with tools to browse, search, and inspect requests and responses, as well as access saved history sessions.
      7 npm
      4
      MIT

    • whistle.agent-mcp

      wilsonyiyi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI assistants to directly search and inspect Whistle-captured HTTP, HTTPS, and WebSocket traffic, including full session details, timing, and frame analysis, without modifying Whistle configuration.
      9 npm
      MIT

    • har-mcp

      karimi-mohammad
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to locally parse and analyze HAR files through read-only MCP tools, including searching requests, discovering endpoints, tracing values, detecting auth and API patterns, comparing requests, and exporting redacted cURL commands.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 47 tools

    Disambiguation3/5

    Many tools have intentionally duplicated surfaces across live/history/reverse planes (read_live_capture vs reverse_read_live_entries, query_recorded_traffic vs analyze_recorded_traffic vs reverse_query_entries, mock_* vs mock_rule_*), and descriptions carry most of the burden. Prefixes like mock_ and reverse_ help, but an agent could easily select the wrong capture/read/query variant without reading deeply.

    Naming Consistency4/5

    Most tools follow a consistent [domain]_[verb]_[object] pattern (start_live_capture, mock_get, reverse_replay_entry), and the mock_/reverse_ prefixes make families recognizable. Minor deviations like throttling, reset_environment, charles_status, and mock_dispatcher break the verb-first pattern but do not obscure meaning.

    Tool Count2/5

    47 tools is well into the 'too many' range and reflects substantial duplication: several near-parallel subsystems (live/history/reverse/mock-rule) each re-implement list/read/query/stop-style operations. The broad Charles domain justifies many tools, but consolidation would meaningfully improve the surface.

    Completeness4/5

    The surface is broad and covers the main lifecycle: live capture, saved recordings, filtering/detail drill-down, mocking, replay, reverse analysis, and environment control. Minor gaps such as no way to start/quit Charles or delete recordings/imports can be worked around, but they are not fatal dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources