Skip to main content
Glama

Related Servers

Alternatives to mitmweb-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Connects an AI assistant to a local Firefox session so it can read pages, interact with forms, manage tabs, and investigate browser issues under user-controlled access rules.
      32
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read sanitized test context, captured requests, rules, and logs from the InterceptPilot Chrome extension, and to propose or run actions such as enabling mocks, importing collections, or capturing tabs, all locally over a secure WebSocket.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI coding agents to the RenderDoc GUI so they can read the capture already open there — the selected event, pipeline state, shaders, bound resources, buffers, render targets and pixel values — for evidence-based rendering debugging. Inspection is read-only, so agents never need to reopen the capture or change the event you have selected, and multiple agents can share one session.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to a live Roblox executor session to read console logs and errors, search and inspect the instance tree, read scripts, change properties, and run Lua, while reporting connection status on every call.
      8
      30
      4
      MIT
    • 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.
      7 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: status checks connectivity, flow_stats provides an overview, inspect_flow gives full detail, detect_auth scans authentication, list_flows lists flows, get_content fetches full bodies, search_flows performs full-text search, diff_flows compares requests, generate_code produces scripts, and replay_flow replays requests. No two tools overlap in intent; even get_content and inspect_flow differ in scope (full vs. preview).

    Naming Consistency5/5

    All tool names follow a consistent lowercase_snake_case convention with a verb-first pattern (inspect_flow, detect_auth, list_flows, get_content, search_flows, diff_flows, generate_code, replay_flow) and a few exceptions like status and flow_stats that still fit the overall style. No mixing of camelCase or different naming schemes.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a traffic capture and analysis server. Each tool covers a distinct aspect of the workflow: connectivity, overview, inspection, auth detection, listing, body retrieval, search, diffing, code generation, and replay. The count feels neither thin nor bloated.

    Completeness5/5

    The tool surface covers the full lifecycle of working with captured HTTP traffic: connect, summarize, inspect, search, compare, generate code, and replay. It also includes advanced features like auth detection and body extraction. There are no obvious dead ends—each tool feeds into the next, and the domain is thoroughly addressed.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues