All servers · Monitoring & logs · Code & repositories · Education

Expo

io.github.mcp-dir/expo-mcp · v0.1.0

Measured by MCP Station

Description written by the publisher, not verified

Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig

Connect

claude mcp add --transport http expo-mcp https://api.mcp.ai/p_expo

{
  "mcpServers": {
    "expo-mcp": {
      "url": "https://api.mcp.ai/p_expo"
    }
  }
}

Tools as reported by the server

• expo_add_library
  Add an Expo library to the project using expo install and attach usage instructions when available
• expo_read_documentation
  Fetch a single Expo documentation page and return its content as markdown. Returns up to ~5000 tokens per call. Use offset to paginate through long pages.
• expo_search_documentation
  Search the official Expo documentation and return page URLs ranked by relevance for a user query. Use read_documentation to fetch the full content of specific pages, starting from the top.
• expo_learn
  Learn Expo how-to for a specific topic and remember it for future conversations. Use this to teach the assistant about specific Expo features or workflows.
• expo_workflow_create
  Creates a new EAS workflow YAML file for Expo projects or fetches workflow syntax documentation. Use this when users want to create CI/CD workflows in .eas/workflows/ or need to learn EAS workflow syntax. After creating, use workflow_validate to validate the file.
• expo_workflow_info
  Fetches detailed information about a specific EAS workflow run by ID. Use this to check the status, job results, errors, and artifacts of a workflow run. If workflow has multiple jobs, draw them in a diagram to show the dependencies between jobs.
• expo_workflow_list
  Lists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
• expo_workflow_logs
  Fetches logs for a specific job in an EAS workflow run. Call without sectionIndex or phase to get a summary of log sections (phase names and line ranges); then call again with sectionIndex or phase to fetch that section.
• expo_workflow_run
  Triggers an EAS workflow run from a git reference. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). The workflow file must exist at the specified git reference.
• expo_workflow_cancel
  Cancels a running EAS workflow. Use workflow_info to get the workflow run ID.
• expo_workflow_validate
  Validates EAS workflow YAML syntax and configuration. Use this after creating a workflow to ensure it is valid. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
• expo_build_list
  Lists EAS builds for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). Use this to see recent builds, their status, and available artifacts.
• expo_build_info
  Fetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details.
• expo_build_logs
  Fetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.
• expo_build_submit
  Submits an EAS build to the app store (Google Play Store for Android, App Store for iOS). The build must be a finished build with the appropriate distribution type. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
• expo_build_run
  Triggers a new EAS build using a build profile from eas.json. Requires a GitHub repository to be connected to the project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
• expo_build_cancel
  Cancels an EAS build that is queued or in progress. Use build_info to check the current status first.
• expo_testflight_crashes
  Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.
• expo_testflight_feedback
  Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.
• show_version
  Show the current MCP platform and adapter versions.
• report_bug
  Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
• connect
  Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
• toolkit_info
  Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
• marketplace
  The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (ev
• authenticate
  MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes

Repository · JSON · Text for agents · Registry updated 2026-08-21