Skip to main content
Glama
chancecreate

charles-mcp

by chancecreate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to charles-mcp

No user-submitted related servers found.

    Related Servers

    • reqable-mcp

      Wanghaibo10
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-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.
      7
      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
      107 PyPI
      326
      MIT

    • 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

    • Herald

      kOlapsis
      A
      license
      Not graded
      quality
      F
      maintenance
      The self-hosted MCP bridge between Claude Chat and Claude Code.
      46
      AGPL 3.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources