Skip to main content
Glama
mattlemmone

Expo MCP Server

by mattlemmone

Related Servers

Alternatives to Expo MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      C
      quality
      D
      maintenance
      An extensible Model Context Protocol server that enables AI assistants like Claude to generate React Native components and perform development tasks through a standardized interface.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A proxy server that enables AI assistants to run and interact with command-line applications like Expo through the Model Context Protocol (MCP), capturing logs and allowing keypress forwarding.
      25 npm
      12
      MIT
    • 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
      -
    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that provides tooling support for Ember.js development, allowing developers to execute CLI commands, run codemods, access documentation, and discover community resources.
      7
      268 npm
      28
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: listFiles lists directory contents, listTools lists server tools, readFile reads entire files, tailFile reads file tails, and writeFile writes files. An agent can easily distinguish between these operations.

    Naming Consistency5/5

    All tool names follow a consistent verbNoun pattern in camelCase (e.g., listFiles, readFile, writeFile). The naming is predictable and uniform across all five tools.

    Tool Count5/5

    With 5 tools, this server is well-scoped for basic file operations. Each tool serves a clear and necessary function, making the count appropriate for the domain without being too sparse or bloated.

    Completeness3/5

    The toolset covers core file operations (list, read, write) but has notable gaps for a file management domain, such as no deleteFile, moveFile, or createDirectory tools. This limits agent workflows, though basic tasks are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues