Skip to main content
Glama
React Native MCP Server

React Native MCP Server

by MrNitro360

Related Servers

Alternatives to React Native MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to inspect React Native app performance including memory, rendering, frames, and network requests, providing plain-language summaries and shareable reports.
      10 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server designed for React Native and Expo development that provides specialized tools for project scaffolding, architectural best practices, and troubleshooting. It enables AI assistants to guide users through setup, navigation configuration, and CI/CD processes using modern stacks like NativeWind and Zustand.
      13
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to inspect React Native and Expo apps through React's runtime tree, identify source locations, act on elements without coordinates, and verify outcomes with assertions and runtime evidence.
      510 npm
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI to see and operate an Expo / React Native app without an emulator, phone, or browser using real screenshots, taps, typing, scrolling, and automated bug hunting, with optional Android and iOS device control.
      9
      376 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools overlap in purpose: analyze_component, analyze_codebase_performance, analyze_codebase_comprehensive, and analyze_testing_strategy/analyze_test_coverage all perform analysis with unclear boundaries. generate_component_test and remediate_code/refactor_component also have some overlap in modifying code, though their primary intents differ.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (generate_component_test, analyze_testing_strategy, optimize_performance, debug_issue, refactor_component). Minor deviations exist with check_for_updates and get_version_info, but the overall pattern is predictable.

    Tool Count4/5

    13 tools is within the reasonable range for a developer-focused server covering analysis, testing, optimization, and maintenance. The count feels slightly heavy given the overlapping analysis tools, but each tool has a distinct enough target area to justify its presence.

    Completeness3/5

    The server covers analysis, testing, performance, architecture, debugging, updates, and remediation—a broad surface. However, there are gaps: no explicit tool for dependency management, no tool for generating new components (only tests/refactoring), and no tool for running or executing tests, which limits end-to-end workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data