Skip to main content
Glama
ah2-io

Expo Docs MCP Server

by ah2-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Expo Docs MCP Server

No user-submitted related servers found.

    Related Servers

    • expo-docs

      Ception
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables fast, offline search and retrieval of Expo documentation from local .mdx files, with tools for searching, getting content, listing sections, API references, and quick start guides.
      24 npm
      17
      MIT

    • Expo MCP Server

      CaullenOmdahl
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables programmatic interaction with Expo/React Native projects and EAS (Expo Application Services) for managing builds, publishing OTA updates, submitting apps to stores, and accessing comprehensive documentation.
      5
      MIT

    • Expo Docs MCP Server

      jaksm
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered semantic search through Expo SDK documentation across multiple versions (v51-v53 and latest), allowing developers to quickly find relevant documentation with configurable similarity scoring.
      100 npm
      2
      MIT

    • Expo

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language management of Expo and EAS projects, including SDK documentation, cloud builds, CI workflows, store submission, and TestFlight crash and feedback data.
      MIT

    • 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
    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 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: searching documentation, retrieving page content, getting API reference, and getting quick start guide. No overlap.

    Naming Consistency4/5

    Most tools follow 'get_expo_*' pattern, but 'search_expo_docs' uses 'search_' instead. Still consistent snake_case and clear verb_noun structure.

    Tool Count5/5

    Four tools is a reasonable number for a documentation-focused server, covering search, content retrieval, API reference, and quick start.

    Completeness4/5

    Core documentation needs are covered (search, page content, API reference, quick start). Missing features like listing categories or version-specific search, but these are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources