Skip to content

Expo MCP connector

The Expo connector brings builds, workflows, documentation, TestFlight feedback and app store reviews into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person works with Expo inside their own access and every action is logged.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Expo to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Expo once

  1. Open Connections, choose Add connection, and pick Expo.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Expo. Expo's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

expo
Expo
Apache Airflow
Apify
Boomi
Browserbase
Caspio
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Expo MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Expo MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Connect Expo to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Use cases

What teams do with Expo through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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?”

See all 25 Expo tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Expo, by what to check
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 $15 per user per month. 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.

AI tools

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.

See it in Elaichi

What connecting Expo gets you

6 screens from the product, each doing one job for your Expo account.

The agent

Ask about builds and reviews, get live answers.

Plain questions about Expo builds, workflows and store reviews, answered from live records.

  • builds
  • workflows
  • reviews
  • crashes

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 or Cursor

MCP clients

One endpoint brings Expo to every client.

Claude, ChatGPT and Cursor reach Expo through one org endpoint, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

25 Expo tools, from builds to store reviews.

Builds, workflows, docs, TestFlight and store reviews covered with no custom code.

  • Add library
  • Read documentation
  • Search documentation
  • Learn
ElaichiTools
Tool Action Description
Add library Add Add an Expo library to the project using expo install and attach usage instructions when available.
Read documentation Action 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.
Search documentation Search 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.
Learn Action 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.
Workflow create 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.

Toolboxes

Every team gets its own Expo toolbox.

Release owns builds, Support owns store reviews, each toolbox scoped to one team.

  • Mobile engineering
  • Release
  • QA
  • Support
ElaichiToolboxes
Name Source template Tools Created

Mobile engineering toolbox

Expo · builds and logs

Expo starter 18 Mar 4, 2026

Release toolbox

Expo · workflows and store submissions

— 9 Mar 2, 2026

QA toolbox

Expo · crashes and TestFlight feedback

— 24 Feb 27, 2026

Support toolbox

Expo · store reviews and replies

Expo starter 6 Feb 19, 2026

Product toolbox

Expo · reviews and tester feedback

— 31 Jan 30, 2026

Engineering toolbox

Expo · documentation and libraries

— 12 Jan 22, 2026

Shared connections

Share the Expo connection, never the credential.

One person connects Expo, teammates work through it without ever seeing a token.

  • iOS release
  • Android release
  • Mobile core
  • QA
ElaichiConnections
Connection Scope Status Access
EX

Expo (iOS release)

Connected by Emily Carter

Personal • Active 1 team · 6 members
EX

Expo (Android release)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
EX

Expo (Mobile core)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
EX

Expo (QA)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
EX

Expo (Support)

Connected by Ryan Hayes

Personal • Active Not shared
EX

Expo (Product)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Expo action is logged with a name.

Who canceled a build or replied to a review, when, on which resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Expo Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Expo Builds Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Expo Builds List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

Store reviews get answered on a schedule.

New App Store reviews are fetched, grouped, drafted into replies, approved, then posted to Expo.

Expo digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch builds

    Expo

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Expo

    Queued

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.

Expo health

Refreshed 4 minutes ago · every 15 minutes · from the builds collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Expo connection?

Yes. One person connects Expo in Elaichi and shares the connection with a team, and nobody else ever handles an Expo credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who canceled a build or replied to a review, not the account owner.

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 blocking cancels, submissions or review replies. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.