Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
Scored across 25 tools
The build_* and workflow_* groups are cleanly separated, but `authenticate` and `connect` both touch credential/connection flows, and `expo_learn` overlaps conceptually with `expo_search_documentation`/`expo_read_documentation`. The monolithic `marketplace` tool also bundles many sub-capabilities into one entry, adding ambiguity.
Most Expo tools share an `expo_` prefix and several follow a clear `expo_build_<verb>` / `expo_workflow_<verb>` pattern, which helps readability. However, documentation tools use `expo_<verb>_documentation`, TestFlight tools drop the verb, and six platform tools (`connect`, `marketplace`, `toolkit_info`, etc.) break the naming convention entirely.
25 tools is on the heavy side, and the server mixes Expo-specific build/workflow/TestFlight/documentation tools with generic platform tools like `marketplace`, `report_bug`, and `show_version`. Each tool is arguably useful, but the overall surface feels larger than the 'Expo' name implies.
Build and workflow lifecycle coverage is strong: builds cover run/list/info/logs/cancel/submit, and workflows cover create/validate/run/list/info/logs/cancel. Minor gaps exist, such as no library removal, no workflow file update/delete tool, and no EAS Update publishing, but the core workflows are usable without dead ends.
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: "" } after the user pastes, or with no args to get the link.
Inputs: token.
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.
Inputs: no named parameters.
Add an Expo library to the project using expo install and attach usage instructions when available
Inputs: libraryName (required), projectRoot (required).
Cancels an EAS build that is queued or in progress. Use build_info to check the current status first.
Inputs: buildId (required).
Fetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details.
Inputs: buildId (required).
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.
Inputs: appId, limit, status, platform, +1 more.
Fetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.
Inputs: buildId (required).
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").
Inputs: gitRef (required), platform (required), buildProfile (required), appId, +4 more.
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").
Inputs: buildId (required), platform (required), appId, track, +2 more.
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.
Inputs: topic (required).
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.
Inputs: url (required), offset.
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.
Inputs: query (required).
Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.
Inputs: bundleId (required), limit, crashId.
Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.
Inputs: bundleId (required), limit.
Cancels a running EAS workflow. Use workflow_info to get the workflow run ID.
Inputs: workflowRunId (required).
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.
Inputs: action (required), fileName, projectRoot, workflowYaml.
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.
Inputs: workflowRunId (required).
Lists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
Inputs: appId, limit, status, appFullName.
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.
Inputs: jobKey (required), workflowRunId (required), phase, sectionIndex.
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.
Inputs: gitRef (required), fileName (required), appId, appFullName.
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").
Inputs: workflowYaml (required), appId, appFullName.
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 (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uplo…
Your Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f
Add one secure layer between your agents and this server.
