Skip to main content
Glama
patrickkabwe

React Native MCP Server

by patrickkabwe

Related Servers

Alternatives to React Native MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides comprehensive React Native development assistance with expert-level automated code remediation, security vulnerability fixes, performance optimization, and production-ready code generation. Includes testing suite generation, dependency management, and accessibility compliance tools.
      13
      56 npm
      63
      MIT
    • 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
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server designed to streamline Expo and React Native development for AI assistants like Cursor and Claude. It provides a comprehensive suite of tools for project initialization, EAS builds, OTA updates, and development server management.
      1
      -
    • 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
      -

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes with no overlap. get-react-native-diff provides detailed upgrade instructions between versions, while get-react-native-stable-version simply retrieves the latest stable version number. An agent would never confuse which tool to use for which task.

    Naming Consistency5/5

    Both tools follow the exact same naming pattern: get-react-native- followed by a descriptive noun (diff, stable-version). The kebab-case is consistent throughout, and the verb 'get' is used consistently for both retrieval operations.

    Tool Count2/5

    With only 2 tools, this server feels severely underpowered for a React Native upgrade domain. While the tools work together logically, there are obvious missing operations like applying the diff, checking current version, or handling specific platform configurations separately. The scope suggests more comprehensive tooling would be appropriate.

    Completeness2/5

    The server is severely incomplete for React Native upgrade workflows. While it provides version information and a diff, there's no tool to actually execute the upgrade steps described in the diff output. Agents would be left with detailed instructions but no automated way to implement them, creating a significant gap in the operational surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues