Skip to main content
Glama
igorzheludkov

Metro Logs MCP

by igorzheludkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Metro Logs MCP

No user-submitted related servers found.

    Related Servers

    • React Native DevTools MCP

      V3RON
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges React Native DevTools, enabling AI assistants to debug, profile, and inspect React Native applications through a standardized protocol.
      10 npm
      4
      MIT

    • browser-console-mcp-tools

      clusslin
      A
      license
      A
      quality
      D
      maintenance
      Captures browser console messages (log, warn, error, etc.) and makes them available to AI language models like Claude Code and Gemini CLI for seamless debugging and development.
      4
      8 npm
      MIT

    • Console MCP Server

      bvelasquez
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Captures and stores console output from any process in SQLite with full-text search, enabling AI assistants to search logs, monitor errors, and analyze multi-process activity through natural language queries.
      -

    • repack-logs-mcp

      kessenma
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for tailing Re.Pack/Rspack dev server logs. Enables AI assistants to query build logs, find errors, and monitor compilation status.
      5
      7 npm
      MIT

    • reactotron-mcp

      steve228uk
      A
      license
      Not graded
      quality
      F
      maintenance
      Acts as a proxy between your app and Reactotron, enabling AI assistants to read logs, inspect state, monitor network requests, and trigger custom commands.
      21 npm
      3
      MIT
    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.4/5.0

    Scored across 64 tools

    Disambiguation3/5

    The tool set has clear groupings (Android, iOS, React Native debugging, Metro connection, etc.) with distinct purposes within each group, but there is significant overlap between similar tools across platforms (e.g., android_describe_all and ios_describe_all) and between alternative methods (e.g., ocr_screenshot vs. accessibility-based tools). Descriptions help clarify, but agents may struggle to choose between overlapping options without deep domain knowledge.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern throughout, with clear verb_noun structures (e.g., android_tap, get_logs, scan_metro). Minor deviations exist, such as ocr_screenshot using an acronym prefix and some tools having longer names (e.g., toggle_element_inspector), but the overall naming is predictable and readable.

    Tool Count2/5

    With 64 tools, the count is excessive for a single server, making it overwhelming and difficult to navigate. While the domain (React Native debugging with Android/iOS support) is broad, many tools are redundant or highly specialized, leading to a bloated interface that could be streamlined without losing functionality.

    Completeness5/5

    The tool set provides comprehensive coverage for React Native debugging, including connection management, log retrieval, network monitoring, component inspection, and device interaction for both Android and iOS. It supports full CRUD-like operations (e.g., install/launch/terminate apps, input text, swipe/tap) and handles edge cases like error recovery and OCR alternatives, leaving no obvious gaps for the intended purpose.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources