Skip to main content
hc
Submit
mcpSource-backed

Expo MCP Server for Claude

Official Expo-hosted remote MCP server for connecting Claude and other MCP clients to Expo documentation, Expo SDK guidance, EAS builds, EAS workflows, TestFlight crash and feedback data, React Native DevTools, and simulator automation for Expo projects.

by Expo · submitted by oktofeesh1·added 2026-06-04·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/expo-mcp-server
Source URLs
https://github.com/expo/expo, https://expo.dev
Safety notes
Expo MCP Server is an official remote MCP server hosted at `https://mcp.expo.dev/mcp`. It is not a HeyClaude-hosted package., The remote server uses OAuth-backed authentication. Do not paste Expo access tokens, usernames, passwords, or OAuth callback material into prompts, screenshots, public MCP configs, shell history, issue comments, or committed files., Build and workflow tools can trigger, cancel, inspect, validate, and submit EAS operations when the authenticated account has permission. Treat those as production-impacting actions for real apps., `build_submit` can submit finished builds to app stores when the project is configured for that path. Require explicit human confirmation before any store submission, release-channel change, or production distribution step., The dependency helper uses Expo's recommended install path for compatible package versions. Review generated dependency changes before committing or running the app., Local capabilities require installing `expo-mcp`, logging into Expo CLI, and starting the dev server with `EXPO_UNSTABLE_MCP_SERVER=1`. Review this environment before enabling local automation in shared machines, CI, or sensitive app projects., Simulator automation tools can tap screens, inspect views, take screenshots, collect logs, and open React Native DevTools. Keep them scoped to test apps, local simulators, or approved debugging sessions., Expo documents current local limitations, including one development server connection at a time, iOS local capability support limited to simulators, and iOS local capability support on macOS hosts.
Privacy notes
Tool results can expose Expo account data, project identifiers, app names, build history, workflow runs, workflow logs, build logs, artifacts, TestFlight crash reports, TestFlight feedback, simulator screenshots, device logs, route maps, and source-derived app structure., Expo states that data sent to Expo MCP Server is not used to train AI models and that the server does not run an AI model itself, but connected MCP clients and model providers may have separate retention and training policies., Local capabilities can proxy data from the development machine through Expo MCP Server before returning it to the connected MCP client, including screenshots and simulator-derived state., Build logs, workflow logs, crash data, and app feedback may contain customer data, user identifiers, stack traces, API endpoints, environment names, release metadata, screenshots, or secrets accidentally printed by the app., Expo access tokens, generated credentials, app-store metadata, signing setup, and project secrets should stay in secret managers or approved MCP client credential stores, not prompts or repository files., Use demo apps, synthetic accounts, simulator data, and non-production EAS projects for screenshots, examples, validation, and AI-assisted troubleshooting.
Author
Expo
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

9 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

9 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/9 ready
Account & credentials3Network & hosting2Review & approval1General320 minutes

Safety & privacy surface

Safety & privacy surface

8 safety and 6 privacy notes across 7 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.

7 areas
  • SafetyNetwork accessExpo MCP Server is an official remote MCP server hosted at `https://mcp.expo.dev/mcp`. It is not a HeyClaude-hosted package.
  • SafetyCredentials & tokensThe remote server uses OAuth-backed authentication. Do not paste Expo access tokens, usernames, passwords, or OAuth callback material into prompts, screenshots, public MCP configs, shell history, issue comments, or committed files.
  • SafetyPermissions & scopesBuild and workflow tools can trigger, cancel, inspect, validate, and submit EAS operations when the authenticated account has permission. Treat those as production-impacting actions for real apps.
  • SafetyLocal files`build_submit` can submit finished builds to app stores when the project is configured for that path. Require explicit human confirmation before any store submission, release-channel change, or production distribution step.
  • SafetyLocal filesThe dependency helper uses Expo's recommended install path for compatible package versions. Review generated dependency changes before committing or running the app.
  • SafetyExecution & processesLocal capabilities require installing `expo-mcp`, logging into Expo CLI, and starting the dev server with `EXPO_UNSTABLE_MCP_SERVER=1`. Review this environment before enabling local automation in shared machines, CI, or sensitive app projects.
  • SafetyCredentials & tokensSimulator automation tools can tap screens, inspect views, take screenshots, collect logs, and open React Native DevTools. Keep them scoped to test apps, local simulators, or approved debugging sessions.
  • SafetyGeneralExpo documents current local limitations, including one development server connection at a time, iOS local capability support limited to simulators, and iOS local capability support on macOS hosts.
  • PrivacyExecution & processesTool results can expose Expo account data, project identifiers, app names, build history, workflow runs, workflow logs, build logs, artifacts, TestFlight crash reports, TestFlight feedback, simulator screenshots, device logs, route maps, and source-derived app structure.
  • PrivacyThird-party handlingExpo states that data sent to Expo MCP Server is not used to train AI models and that the server does not run an AI model itself, but connected MCP clients and model providers may have separate retention and training policies.
  • PrivacyGeneralLocal capabilities can proxy data from the development machine through Expo MCP Server before returning it to the connected MCP client, including screenshots and simulator-derived state.
  • PrivacyCredentials & tokensBuild logs, workflow logs, crash data, and app feedback may contain customer data, user identifiers, stack traces, API endpoints, environment names, release metadata, screenshots, or secrets accidentally printed by the app.
  • PrivacyCredentials & tokensExpo access tokens, generated credentials, app-store metadata, signing setup, and project secrets should stay in secret managers or approved MCP client credential stores, not prompts or repository files.
  • PrivacyGeneralUse demo apps, synthetic accounts, simulator data, and non-production EAS projects for screenshots, examples, validation, and AI-assisted troubleshooting.

Safety notes

  • Expo MCP Server is an official remote MCP server hosted at `https://mcp.expo.dev/mcp`. It is not a HeyClaude-hosted package.
  • The remote server uses OAuth-backed authentication. Do not paste Expo access tokens, usernames, passwords, or OAuth callback material into prompts, screenshots, public MCP configs, shell history, issue comments, or committed files.
  • Build and workflow tools can trigger, cancel, inspect, validate, and submit EAS operations when the authenticated account has permission. Treat those as production-impacting actions for real apps.
  • `build_submit` can submit finished builds to app stores when the project is configured for that path. Require explicit human confirmation before any store submission, release-channel change, or production distribution step.
  • The dependency helper uses Expo's recommended install path for compatible package versions. Review generated dependency changes before committing or running the app.
  • Local capabilities require installing `expo-mcp`, logging into Expo CLI, and starting the dev server with `EXPO_UNSTABLE_MCP_SERVER=1`. Review this environment before enabling local automation in shared machines, CI, or sensitive app projects.
  • Simulator automation tools can tap screens, inspect views, take screenshots, collect logs, and open React Native DevTools. Keep them scoped to test apps, local simulators, or approved debugging sessions.
  • Expo documents current local limitations, including one development server connection at a time, iOS local capability support limited to simulators, and iOS local capability support on macOS hosts.

Privacy notes

  • Tool results can expose Expo account data, project identifiers, app names, build history, workflow runs, workflow logs, build logs, artifacts, TestFlight crash reports, TestFlight feedback, simulator screenshots, device logs, route maps, and source-derived app structure.
  • Expo states that data sent to Expo MCP Server is not used to train AI models and that the server does not run an AI model itself, but connected MCP clients and model providers may have separate retention and training policies.
  • Local capabilities can proxy data from the development machine through Expo MCP Server before returning it to the connected MCP client, including screenshots and simulator-derived state.
  • Build logs, workflow logs, crash data, and app feedback may contain customer data, user identifiers, stack traces, API endpoints, environment names, release metadata, screenshots, or secrets accidentally printed by the app.
  • Expo access tokens, generated credentials, app-store metadata, signing setup, and project secrets should stay in secret managers or approved MCP client credential stores, not prompts or repository files.
  • Use demo apps, synthetic accounts, simulator data, and non-production EAS projects for screenshots, examples, validation, and AI-assisted troubleshooting.

Prerequisites

  • Expo account that can authenticate to the projects, builds, workflows, and EAS resources the assistant should access.
  • Expo project on the latest supported Expo SDK, or a plan to upgrade before relying on current MCP capabilities.
  • MCP-capable client with remote Streamable HTTP support, such as Claude Code, Codex, Cursor, VS Code, or another compatible client.
  • OAuth or Expo access-token authentication path approved for the project and organization.
  • EAS project identifier or app full name for build and workflow tools.
  • Connected GitHub repository and valid EAS workflow files before asking the assistant to trigger builds or workflows.
  • Optional local capability setup with Expo SDK 54 or later, `expo-mcp` installed as a dev dependency, Expo CLI login, and a running Expo dev server.
  • macOS host and iOS simulator when using iOS local automation capabilities.
  • Human approval policy for dependency installs, workflow file changes, build triggers, build cancellations, app-store submissions, and simulator automation.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "expo": {
      "url": "https://mcp.expo.dev/mcp",
      "transport": "http"
    }
  }
}

About this resource

Content

Expo MCP Server is Expo's official remote Model Context Protocol server for AI development workflows around Expo and React Native apps. It lets Claude and other MCP-capable clients fetch current Expo documentation, install Expo-compatible libraries, inspect and operate EAS builds and workflows, review TestFlight crash or feedback context, and, when local capabilities are enabled, interact with an Expo app running in a simulator.

Expo documents the remote server endpoint as:

https://mcp.expo.dev/mcp

Use it as a remote Streamable HTTP MCP server with OAuth, then add local capabilities only for projects where simulator automation and local development state are appropriate.

Source Review

These sources were reviewed on 2026-06-04. Prefer the live Expo docs over model memory for the current endpoint, authentication flow, available tools, plan requirements, local capability setup, SDK requirements, and limitations.

Features

  • Official Expo-hosted remote MCP server at https://mcp.expo.dev/mcp.
  • Streamable HTTP setup for Claude Code, Codex, Cursor, VS Code, and other MCP clients with remote MCP support.
  • OAuth authentication using Expo account credentials or an Expo personal access token through the client flow.
  • Expo documentation search and page-reading tools for current SDK, Expo Router, CNG, deep linking, libraries, workflows, and platform guidance.
  • Dependency helper that uses npx expo install semantics for known Expo-compatible package versions.
  • EAS Workflow tools for creating workflow files, validating workflow YAML, listing runs, inspecting run status, fetching logs, triggering runs, and cancelling running workflows.
  • EAS Build tools for listing builds, checking build status, fetching build logs, triggering builds, cancelling queued or running builds, and submitting finished builds to app stores.
  • TestFlight crash and feedback tools for debugging recent iOS beta reports.
  • Optional local capabilities through the expo-mcp dev dependency and an Expo dev server started with EXPO_UNSTABLE_MCP_SERVER=1.
  • Local tools for screenshots, view lookup by React Native testID, tap automation, app log collection, React Native DevTools, and Expo Router sitemap introspection.

Use Cases

  • Ask Claude to search current Expo docs before changing Expo Router, deep linking, native modules, push notifications, camera, SQLite, or CNG setup.
  • Add an Expo library with compatible dependency versions and review the patch before committing it.
  • Investigate a failed EAS build by listing recent builds, fetching the failed build logs, and summarizing the smallest likely fix.
  • Create or validate an EAS Workflow file before committing it under .eas/workflows/.
  • Trigger a known EAS workflow from an approved git ref after a human confirms the workflow name, app identifier, and release impact.
  • Review TestFlight crash reports or screenshot feedback during mobile QA.
  • Use simulator screenshots and tap automation to verify a UI fix in an Expo development build.
  • Inspect an Expo Router sitemap to confirm the app's route tree before changing navigation, linking, or auth boundaries.

Installation

Claude Code

Add the remote MCP server with HTTP transport:

claude mcp add --transport http expo https://mcp.expo.dev/mcp

Then run /mcp in Claude Code and complete Expo authentication.

Codex

Add the server to Codex with the Expo-documented remote endpoint:

codex mcp add expo --url https://mcp.expo.dev/mcp

Complete the OAuth flow with the Expo account or access token that has the least privilege needed for the project.

Optional Local Capabilities

For local simulator and React Native DevTools capabilities, install the local capability provider in an Expo SDK 54+ project and start the dev server with MCP enabled:

npx expo install expo-mcp --dev
npx expo whoami || npx expo login
EXPO_UNSTABLE_MCP_SERVER=1 npx expo start

Restart or reconnect the MCP server after starting or stopping the development server so your client sees the refreshed local tools.

Verification Checklist

  • Confirm the MCP client lists the expo server after authentication.
  • Ask the server to search or read an Expo documentation page before making a code change.
  • Use a non-production project to test build, workflow, and TestFlight queries.
  • Require human confirmation before any build_run, build_cancel, build_submit, workflow_run, or workflow_cancel request.
  • For local automation, run against a simulator or demo project first and inspect screenshots, tap targets, and collected logs before sharing them.
  • Review generated dependency, workflow, and app-code changes before commit.

Duplicate Check

This entry is scoped to Expo's official remote MCP server and optional official local capability provider. It is distinct from generic mobile app developer rules, React Native guidance, Playwright browser automation, Storybook MCP, and third-party Expo documentation MCP wrappers.

Editorial Disclosure

This catalog entry was drafted from Expo's official documentation, Expo's official changelog, and official package/repository metadata. It is not an affiliate listing, paid placement, or maintainer-verified package bundle.

#expo#mcp#eas#react-native#mobile

Source citations

Add this badge to your README

Show that Expo MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/expo-mcp-server.svg)](https://heyclau.de/entry/mcp/expo-mcp-server)

How it compares

Expo MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Expo MCP Server for Claude

Official Expo-hosted remote MCP server for connecting Claude and other MCP clients to Expo documentation, Expo SDK guidance, EAS builds, EAS workflows, TestFlight crash and feedback data, React Native DevTools, and simulator automation for Expo projects.

Open dossier
agent-device logoAgent Device MCP Server

Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps.

Open dossier
Google logoAndroid Skills MCP Server for Claude

Access AI-optimized Android development guides from Claude — search and retrieve SKILL.md content covering Jetpack Compose, Navigation 3, CameraX, AGP 9, App Functions, Edge-to-Edge, Android Profilers, XR, Google Play, and the Android CLI — with the Android Skills MCP server.

Open dossier
iOS Simulator MCP Server

MCP server for controlling iOS simulators from AI agents, including simulator discovery, UI taps, typing, swipes, accessibility inspection, screenshots, video recording, app install, and app launch.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1—oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand—agent-device logoagent-deviceGoogle logoGoogle—
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorExpoCallstackJaewoong Eum (skydoves)Joshua Yoes
Added2026-06-042026-06-062026-06-182026-06-05
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Expo MCP Server is an official remote MCP server hosted at `https://mcp.expo.dev/mcp`. It is not a HeyClaude-hosted package. The remote server uses OAuth-backed authentication. Do not paste Expo access tokens, usernames, passwords, or OAuth callback material into prompts, screenshots, public MCP configs, shell history, issue comments, or committed files. Build and workflow tools can trigger, cancel, inspect, validate, and submit EAS operations when the authenticated account has permission. Treat those as production-impacting actions for real apps. `build_submit` can submit finished builds to app stores when the project is configured for that path. Require explicit human confirmation before any store submission, release-channel change, or production distribution step. The dependency helper uses Expo's recommended install path for compatible package versions. Review generated dependency changes before committing or running the app. Local capabilities require installing `expo-mcp`, logging into Expo CLI, and starting the dev server with `EXPO_UNSTABLE_MCP_SERVER=1`. Review this environment before enabling local automation in shared machines, CI, or sensitive app projects. Simulator automation tools can tap screens, inspect views, take screenshots, collect logs, and open React Native DevTools. Keep them scoped to test apps, local simulators, or approved debugging sessions. Expo documents current local limitations, including one development server connection at a time, iOS local capability support limited to simulators, and iOS local capability support on macOS hosts.✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP. Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions. Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files. Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work. Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.✓The server runs entirely offline — no network requests are made during queries. All skill content is bundled with the npm package.✓Use version 1.3.3 or newer. The upstream security policy documents command-injection vulnerabilities in older versions and states that they were fixed in v1.3.3. The server invokes simulator, IDB, and host commands to tap, type, swipe, screenshot, record video, install apps, launch apps, and stop recordings. Filter high-risk or noisy tools with `IOS_SIMULATOR_MCP_FILTERED_TOOLS` when an agent should only inspect UI state. App install and launch tools can execute simulator app code, change simulator state, and interact with test credentials or local development services. Screenshots and recordings can overwrite or create files in configured output directories; review paths before letting an agent write artifacts.
Privacy notes✓Tool results can expose Expo account data, project identifiers, app names, build history, workflow runs, workflow logs, build logs, artifacts, TestFlight crash reports, TestFlight feedback, simulator screenshots, device logs, route maps, and source-derived app structure. Expo states that data sent to Expo MCP Server is not used to train AI models and that the server does not run an AI model itself, but connected MCP clients and model providers may have separate retention and training policies. Local capabilities can proxy data from the development machine through Expo MCP Server before returning it to the connected MCP client, including screenshots and simulator-derived state. Build logs, workflow logs, crash data, and app feedback may contain customer data, user identifiers, stack traces, API endpoints, environment names, release metadata, screenshots, or secrets accidentally printed by the app. Expo access tokens, generated credentials, app-store metadata, signing setup, and project secrets should stay in secret managers or approved MCP client credential stores, not prompts or repository files. Use demo apps, synthetic accounts, simulator data, and non-production EAS projects for screenshots, examples, validation, and AI-assisted troubleshooting.✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials. macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts. Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing. Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.✓No API keys, user data, or query content is sent to any external service. All lookups happen locally against the bundled skill snapshot.✓Tool results may expose app screens, accessibility labels, text fields, screenshots, videos, bundle identifiers, simulator UDIDs, file paths, output directories, app paths, and environment variables. Simulator apps may contain test accounts, customer fixtures, tokens, unreleased UI, internal URLs, logs, or private feature flags. MCP transcripts, client logs, screenshots, videos, and saved artifacts can retain sensitive UI and app-state data outside the simulator. Do not share recordings, screenshots, simulator data, app bundles, UDIDs, or output directories from proprietary apps unless the team has approved that disclosure.
Prerequisites
  • Expo account that can authenticate to the projects, builds, workflows, and EAS resources the assistant should access.
  • Expo project on the latest supported Expo SDK, or a plan to upgrade before relying on current MCP capabilities.
  • MCP-capable client with remote Streamable HTTP support, such as Claude Code, Codex, Cursor, VS Code, or another compatible client.
  • OAuth or Expo access-token authentication path approved for the project and organization.
  • Node.js 22 or newer and `agent-device` installed globally or project-locally.
  • Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets.
  • Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate.
  • Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • macOS with Xcode and iOS simulators installed.
  • Node.js and npx available for running the npm package.
  • Facebook IDB installed and available on PATH, or configured through `IOS_SIMULATOR_MCP_IDB_PATH`.
  • A booted simulator, or permission for the agent to open and interact with Simulator.
Install
claude mcp add --transport http expo https://mcp.expo.dev/mcp
claude mcp add --transport stdio --scope user agent-device -- agent-device mcp
claude mcp add android-skills -- npx -y android-skills-mcp
claude mcp add ios-simulator -- npx -y ios-simulator-mcp
Config
{
  "mcpServers": {
    "expo": {
      "url": "https://mcp.expo.dev/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "agent-device": {
      "command": "agent-device",
      "args": ["mcp"]
    }
  }
}
{
  "mcpServers": {
    "android-skills": {
      "command": "npx",
      "args": ["-y", "android-skills-mcp"]
    }
  }
}
{
  "mcpServers": {
    "ios-simulator": {
      "command": "npx",
      "args": ["-y", "ios-simulator-mcp"],
      "env": {
        "IOS_SIMULATOR_MCP_FILTERED_TOOLS": "screenshot,record_video,stop_recording",
        "IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR": "SIMULATOR_OUTPUT_DIR",
        "IOS_SIMULATOR_MCP_IDB_PATH": "IDB_EXECUTABLE_PATH"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Building In-Process MCP Tools with the Claude Agent SDK

Define in-process MCP tools for the Claude Agent SDK with createSdkMcpServer and the tool helper, then wire them into query.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Choose the Right Claude Extension Surface

Decide when to use Claude subagents, skills, commands, hooks, or MCP.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by MkDev11

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.