# Expo MCP MCP Server > **Expo MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Expo MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/expo-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Expo helps developers build, test, and distribute React Native applications. AI agents can inspect project documentation, search API references, diagnose build and runtime errors, access development tools, preview apps with Expo Go, and streamline workflows for iOS, Android, and web deployments. --- ## Details - Server ID: `expo-mcp` - Version: 1.0.0 - Tools: 50 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Expo MCP has to be in the toolset first. In order: 1. Add Expo MCP to your toolset at https://mewcp.com/mcp/expo-mcp 2. Connect your Expo MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (50) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `read_documentation` _(read)_ — 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` _(read)_ — 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… - `usage_budget_get` _(read)_ — Returns limits and available usage. Available minutes exclude active reservations. Null means there is no limit. Availability can change before the next… - `usage_budget_create` _(write)_ — Creates a usage budget with user-approved limits. Reuse the returned usageBudgetId for metered operations in the current task or conversation. - `workflow_info` _(read)_ — 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_list` _(read)_ — Lists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). - `workflow_logs` _(read)_ — 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… - `workflow_run` _(write)_ — 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_cancel` _(destructive)_ — Cancels a running EAS workflow. Use workflow_info to get the workflow run ID. - `workflow_validate` _(read)_ — Validates EAS workflow YAML syntax and configuration. Use this after creating a workflow to ensure it is valid. Provide either appId (from app.json… - `build_list` _(read)_ — 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… - `build_info` _(read)_ — Fetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details. - `build_logs` _(read)_ — Fetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available. - `build_submit` _(write)_ — 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… - `build_run` _(write)_ — 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… - `build_cancel` _(destructive)_ — Cancels an EAS build that is queued or in progress. Use build_info to check the current status first. - `sandbox_stop` _(destructive)_ — Request cancellation of the sandbox’s backing job. This can interrupt running commands. The returned status may still be STARTING or RUNNING while cancellation… - `sandbox_list` _(read)_ — List sandboxes for an EAS project, newest first. Optionally filter by status. Pass nextCursor as cursor to fetch the next page with the same project and filter. - `sandbox_create` _(write)_ — Create an EAS sandbox for a project. This starts a billable environment. Set waitForReady to wait for startup, or use sandbox_wait after creation. Execute… - `sandbox_wait` _(read)_ — Wait until a sandbox is RUNNING, STOPPED, or ERRORED. If the wait expires while STARTING, returns the last observed status. Does not create, stop, or extend… - `sandbox_exec` _(destructive)_ — Execute a shell command in a running EAS sandbox. Use sandbox_write_stdin to continue a running command. A lost response does not mean the command failed; do… - `sandbox_write_stdin` _(destructive)_ — Read output from a sandbox command session or send input to it. Output is consumed; do not automatically retry after a lost response. - `sandbox_artifact_create` _(write)_ — Upload one file from a running EAS sandbox as a sandbox artifact. Waits up to yieldTimeMs for the upload to finish and returns its status; if it is still… - `sandbox_artifact_get` _(read)_ — Read a sandbox artifact and get a new download URL. Also works after the sandbox stops. size and downloadUrl are null until the upload finishes. If they are… - `sandbox_artifact_list` _(read)_ — List the artifacts of a sandbox, newest first. Also works after the sandbox stops. Use sandbox_artifact_get to get a download URL. - `sandbox_read_file` _(read)_ — Read a UTF-8 text file or a PNG, JPEG, GIF, or WebP image from a running EAS sandbox. Images are returned as image content, up to 3000000 bytes. Text is… - `observe_versions` _(read)_ — List app versions seen by EAS Observe, with build numbers, EAS build/update IDs, event counts and unique-user counts. Use these versions and IDs to investigate… - `observe_metrics_summary` _(read)_ — Compare EAS Observe performance metrics by app version and platform. Returns event counts, min, max, median, average, p80, p90 and p99; timing values are in… - `observe_metrics` _(read)_ — Find individual EAS Observe performance samples, including the slowest startup/navigation events. Timing values are in seconds. Filter by release and platform;… - `observe_routes` _(read)_ — Compare navigation routes by cold TTR, warm TTR and TTI. Returns counts, medians and p90 in seconds, separately per platform. Defaults to most navigations… - `observe_event_names` _(read)_ — Discover custom events emitted with Observe.logEvent, with occurrence counts and first/last seen times. Returns isTruncated when the API caps the list; narrow… - `observe_events` _(read)_ — Read custom events emitted with Observe.logEvent, including properties, severity and session IDs. Omit eventName to list all custom events or use… - `observe_session` _(read)_ — Read a session’s metric samples and logs (custom events and errors). Each stream is oldest first and independently paginated; entries are sorted within this… - `simulator_start` _(write)_ — Start a billed EAS Simulator session in the cloud. Returns simulatorSessionId right away while the device boots. Poll simulator_get until status is… - `simulator_get` _(read)_ — Fetch an EAS Simulator session by id. Returns status and dashboardUrl, where you can view the device after logging in. Never returns device credentials. Set… - `simulator_list` _(read)_ — List EAS Simulator sessions for a project, newest first. Pass appId or appFullName. Filter by platform or status. Pass nextCursor as cursor to fetch the next… - `simulator_stop` _(destructive)_ — Stop an EAS Simulator session. Safe to call again: a session that already finished is returned unchanged. - `automation_tap` _(write)_ — Tap the connected device. Target: pass simulatorSessionId for an EAS Simulator session, or projectRoot for the local device through the expo-mcp tunnel. Pass… - `automation_take_screenshot` _(read)_ — Take a screenshot of the connected device. Target: pass simulatorSessionId for an EAS Simulator session, or projectRoot for the local device through the… - `automation_find_view` _(read)_ — Find a view on the connected device by React Native testID or accessibility label. Target: pass simulatorSessionId for an EAS Simulator session, or projectRoot… - `automation_type` _(destructive)_ — Type text on the connected device. Target: pass simulatorSessionId for an EAS Simulator session, or projectRoot for the local device through the expo-mcp… - `automation_scroll` _(write)_ — Scroll the connected device screen. Target: pass simulatorSessionId for an EAS Simulator session, or projectRoot for the local device through the expo-mcp… - `testflight_crashes` _(read)_ — Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace. - `testflight_feedback` _(read)_ — Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs. - `appstore_reviews` _(read)_ — Fetch public App Store customer reviews for an app (rating, title, body, reviewer, territory). For TestFlight beta feedback use testflight_feedback instead. - `appstore_reply_review` _(destructive)_ — Post or edit the public developer response to an App Store customer review. This is a write action: the response is visible to everyone on the App Store, and… - `appstore_delete_review_response` _(destructive)_ — Delete the public developer response on an App Store customer review. This is a write action: it removes the response from the App Store. No-op-safe: if the… - `playstore_crashes` _(read)_ — Fetch crash and ANR data from Google Play (Android Vitals). Without issueId, lists recent crash/ANR issues. With issueId, returns the full error report with… - `playstore_reviews` _(read)_ — Fetch user reviews from Google Play. Returns review metadata including author, star rating, device info, and comment text. Note: Google Play only exposes… - `playstore_reply_review` _(destructive)_ — Post a public developer reply to a Google Play user review, or edit the existing reply. This is a write action: the reply is visible to users on the store… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)