Skip to main content
Glama
MrNitro360

React Native MCP Server

by MrNitro360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to React Native MCP Server

No user-submitted related servers found.

    Related Servers

    • rn-devtools-mcp

      Ehab-Aqili
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect React Native app performance including memory, rendering, frames, and network requests, providing plain-language summaries and shareable reports.
      2
      MIT

    • React Native Expo MCP

      ZaharGusyatin
      F
      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
      -

    • react-native-toolkit

      ItamiForge
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with accurate, version-aware documentation for React Native, Expo, React Navigation, and Ignite by automatically detecting project dependencies and fetching matching documentation.
      12
      MIT

    • Dendro

      RooneyTech
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to deeply analyze and visualize React and React Native codebases locally through 36 free MCP tools for component trees, complexity scoring, navigation, data flow, health audits, and interactive tracing.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    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
    ResponsivenessUnresponsive

    Resources