# Expo

- Registry name: `io.github.mcp-dir/expo-mcp` · version 0.1.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Code & repositories, Developer tools, Education
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.mcp-dir%2Fexpo-mcp
- Server page: https://mcpstation.net/s/io.github.mcp-dir--expo-mcp.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://api.mcp.ai/p_expo`

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html