Skip to main content
Glama
Divagnz

React Native Expo MCP

by Divagnz

Related Servers

Alternatives to React Native Expo MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides development and debugging tools for Expo-based React Native applications, enabling developers to manage Expo servers, capture logs, and manipulate project files.
      5
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables real-time debugging and inspection of running React Native apps, providing access to console logs, errors, network requests, navigation state, storage, and performance profiling.
      1
      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
      Not graded
      quality
      C
      maintenance
      A secure local MCP server that allows AI assistants to inspect and diagnose Expo-based React Native projects, offering read-only tools for project summary, doctor checks, dependency validation, and public config retrieval.
      2
      -

    TDQS

    A3.5/5.0

    Scored across 33 tools

    Disambiguation5/5

    Each tool targets a distinct area: analysis, building, EAS, dev server, testing, etc. Even closely related tools like the various analysis tools are clearly scoped (comprehensive vs. performance vs. component vs. testing). No ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, often with a domain prefix (e.g., analyze_, eas_, expo_). No mixed conventions or vague verbs. Highly predictable.

    Tool Count4/5

    33 tools is high but justifies the broad scope of React Native/Expo development. Some meta-tools (check_for_updates, get_version_info) are minor but not excessive. Overall, each tool earns its place.

    Completeness5/5

    Covers the full lifecycle: project creation, dev server control, local and cloud builds, app store submission, OTA updates, comprehensive analysis, testing, debugging, dependency management, and upgrades. No obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues