Skip to main content
Glama
tianhetonghua

Charles MCP Server

by tianhetonghua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Charles MCP Server

No user-submitted related servers found.

    Related Servers

    • Charles MCP Server

      ExQA
      A
      license
      B
      quality
      B
      maintenance
      Enables 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

      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
      314
      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

    • Web2Actions

      rashidrashiii
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with websites by capturing browser traffic and exposing them as named MCP tools, requiring no public API.
      Apache 2.0
    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

    A4.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of traffic capture/analysis: filter tools focus on different fields, checkpoint tools manage timelines, and utilities cover data retrieval, throttling, and summarization. The only pair (check_keyword_exists and filter_by_keyword) is clearly linked as a required sequence, avoiding ambiguity.

    Naming Consistency4/5

    All tools use snake_case. Filter tools consistently start with 'filter_by_', while others use verb_noun patterns (e.g., harvest_data, get_raw_data). This provides predictability, though not all follow the exact same template.

    Tool Count5/5

    13 tools cover the full lifecycle of traffic interception (harvest, checkpoint management, multiple filters, raw data retrieval, network throttling, and traffic summarization) without redundancy or unnecessary scope.

    Completeness5/5

    The tool surface enables full CRUD-like operations on captured traffic: harvest (create checkpoint), list/load checkpoints (read), filter by multiple criteria, get raw data, and analyze summaries. Throttling is also included, covering common debugging needs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources