Expo MCP connector
The Expo connector brings builds, workflows, documentation, TestFlight feedback and app store reviews into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works with Expo inside their own access and every action is logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Why did the latest iOS build fail?
Working in Expo with Elaichi
-
Search documentation
-
Workflow list
-
Build list
How to connect Expo to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Expo MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Expo MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Expo MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Expo MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Expo MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Expo to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Expo through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Expo is logged.
-
Mobile engineering
Find out why a build failed
Ask for the latest failed Expo build and read its logs in plain language, then start a new build once the fix is in.
-
Release
Ship a release without opening a terminal
Run the release workflow, watch its progress, and submit the finished build to TestFlight and Google Play from the same conversation.
-
QA
Triage crashes before the standup
Pull this week's TestFlight and Play Store crashes, group them by screen, and turn the worst ones into tickets.
-
Support
Answer app store reviews in bulk
Read new App Store and Play Store reviews, draft replies in your own voice, and post them. If a reply went out wrong, remove it.
-
Product
Summarize what testers are saying
Gather TestFlight feedback and store reviews from the last sprint and summarize the recurring requests and complaints.
-
Engineering
Look up Expo docs while you work
Search Expo's documentation from Cursor, get a plain answer, and add the library you need to the project without switching windows.
Try asking
- “Why did the latest iOS build fail?”
- “Summarize this week's App Store reviews and draft replies.”
- “Which TestFlight crashes showed up after yesterday's build?”
What connecting Expo gets you
6 screens from Elaichi, each doing one job for your Expo account.
Ask Elaichi to work across your apps.
Why did the latest iOS build fail?
Summarize this week's App Store reviews and draft replies.
Which TestFlight crashes showed up after yesterday's build?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about builds and reviews, get live answers.
Plain questions about Expo builds, workflows and store reviews, answered from live records.
Copy the endpoint
AI apps
One endpoint brings Expo to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Expo through one org endpoint, no SDK, no shared key.
Tool catalog
25 Expo tools, from builds to store reviews.
Builds, workflows, docs, TestFlight and store reviews covered with no custom code.
Toolboxes
Every team gets its own Expo toolbox.
Release owns builds, Support owns store reviews, each toolbox scoped to one team.
Shared connections
Share the Expo connection, never the credential.
One person connects Expo, teammates work through it without ever seeing a token.
Audit log
Every Expo action is logged with a name.
Who canceled a build or replied to a review, when, on which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Expo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch builds
Expo
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Expo
Queued
Workflows
Store reviews get answered on a schedule.
New App Store reviews are fetched, grouped, drafted into replies, approved, then posted to Expo.
Expo health
Refreshed 4 minutes ago · every 15 minutes · from the builds collection
Builds
1,284 ↓ 12%
Workflows
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Builds created
Last 14 days
By team
Share of activity
iOS release 34%
Android release 27%
Mobile core 21%
QA 18%
Collections and dashboards
Build health, computed on a schedule, no prompt.
Builds, failures and crashes over 14 days, broken down by team, with no model involved.
Why connect Expo's MCP server through Elaichi
Expo builds and runs this MCP server. Elaichi sits in front of it, so Expo's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Expo's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Expo's tools at the same Elaichi address as every other connected app. Nobody adds Expo's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Expo sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Expo's server. By default, a tool Expo does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Expo
Expo builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Expo team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Expo
All three can connect Expo to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Expo tools | Allow or restrict single Expo tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Expo call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Expo tools for your AI agents
25 tools are ready to call through Elaichi's MCP endpoint the moment you connect Expo, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Expo builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Expo to Claude?
Connect Expo in Elaichi first: pick Expo from the catalog and sign in with your Expo account over OAuth, the same way you sign in to the Expo website. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once, and Expo appears.
Does Expo work with ChatGPT and Cursor as well as Claude?
Yes. Once Expo is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Expo once and every client picks it up.
What can an AI agent actually do with my Expo data?
With Expo connected, an agent can list your builds and read their logs, start or cancel a build, submit one to the stores, and run, check or cancel a workflow. It can also pull TestFlight crashes and feedback, read App Store and Play Store reviews and crashes, post or remove a reply to a review, and search Expo's documentation. Short, concrete asks like "why did the last iOS build fail" work better than long paragraphs.
Does connecting Expo give the AI access to every project and account?
No. Everything an agent does in Expo runs as the person who signed in, so it sees only the projects, builds and store listings that person's Expo account can already see. Elaichi can narrow that further with restrictions, but it never widens it beyond what Expo itself allows.
Can I stop an agent from deleting or changing things in Expo?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Expo builds and reviews while restricting cancels, submissions or review replies. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to an Expo connection when someone leaves?
Offboarding a person in Elaichi ends their access to Expo through every client at once. If they connected a shared Expo account, the connection keeps working for everyone else on the team. Disconnecting Expo once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Expo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Expo is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Expo?
Yes. Both let Claude, ChatGPT or Cursor use Expo. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Expo call.
How is Elaichi different from Composio for Expo?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Expo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Expo in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot