Question 1

What is Expo MCP?

Accepted Answer

It's an MCP (Model Context Protocol) server that connects Expo to your AI, giving the agent tools to act on your data, through a single remote link.

Question 2

Which AI clients does it work with?

Accepted Answer

Any MCP-compatible client: Claude (web, desktop and mobile), Cursor, ChatGPT with connectors, OpenClaw and other agents.

Question 3

Do I need to code?

Accepted Answer

No. Paste the remote URL into your client, authenticate once, and you're done. No packages to install, no code to write.

Question 4

Is it secure? Can the AI change my data?

Accepted Answer

Access is authorized by you and can be revoked anytime. Permissions follow what Expo exposes; you approve them when connecting.

Question 5

Is my customers' data stored on mcp.ai?

Accepted Answer

No. Whatever Expo returns passes through our infrastructure solely to reach the AI assistant you chose, and that content is not stored. By design we don't persist tool-call payloads: the log keeps metadata only (which tool, timestamp, status, duration, size and a hash of the arguments). Your credentials are stored encrypted and you can revoke the connection at any time. Retention periods and details are in the Privacy Policy at mcp.ai/privacy.

Question 6

Is my data used to train AI models?

Accepted Answer

No. Nothing that flows through the connector is used to train or improve AI models, nor shared with third parties for that purpose. The conversation itself, meaning your prompts and the AI's answers, is processed by the AI provider you choose (Claude, ChatGPT and the like), under their own privacy policy.

Question 7

How much does it cost?

Accepted Answer

You start free and upgrade when you need more usage. Billing and limits are managed in your mcp.ai account.

Question 8

Can I cancel anytime?

Accepted Answer

Yes. Plans are monthly and can be cancelled at any time, with no lock-in.

Expo

Tools (19)

API & agent docs

Guides and tutorials

Como oferecer um MCP dentro do seu produto

Cada usuário do seu app com o MCP dele

Frequently asked questions

Example prompts

Related tags

Expo

Tools (19)

expo_add_libraryAdd an Expo library to the project using expo install and attach usage instructions when available

expo_build_cancelCancels an EAS build that is queued or in progress. Use build_info to check the current status first.

expo_build_infoFetches 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_listLists 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_logsFetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.

expo_build_runTriggers 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.

expo_build_submitSubmits 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

expo_learnLearn 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_read_documentationFetch 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_documentationSearch 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_testflight_crashesFetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.

expo_testflight_feedbackFetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.

expo_workflow_cancelCancels a running EAS workflow. Use workflow_info to get the workflow run ID.

expo_workflow_createCreates 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 syn

expo_workflow_infoFetches 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

expo_workflow_listLists 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_logsFetches 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

expo_workflow_runTriggers 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

expo_workflow_validateValidates 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