expo_build_run — Expo MCP Tool
expo_build_run
(expo build run) is one of 25 tools on the
Expo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call expo_build_run from your client
- Claude Code Expo expo_build_run run in your project directory
- Claude Desktop Expo expo_build_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Expo expo_build_run ~/.cursor/mcp.json
- VS Code Expo expo_build_run .vscode/mcp.json
- Zed Expo expo_build_run ~/.config/zed/settings.json
- Windsurf Expo expo_build_run ~/.codeium/windsurf/mcp_config.json
- Cline Expo expo_build_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Expo expo_build_run ~/.gemini/settings.json
- Grok Expo expo_build_run .mcp.json (in your project root)
- ChatGPT Expo expo_build_run Settings → Connectors → Advanced → Developer mode
- Claude.ai Expo expo_build_run Settings → Connectors → Add custom connector
- LangChain Expo expo_build_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http expo-mcp https://api.mcp.ai/p_expoOther tools on this server
- expo_add_library
- expo_read_documentation
- expo_search_documentation
- expo_learn
- expo_workflow_create
- expo_workflow_info
- expo_workflow_list
- expo_workflow_logs
- expo_workflow_run
- expo_workflow_cancel
- expo_workflow_validate
- expo_build_list
- expo_build_info
- expo_build_logs
- expo_build_submit
- expo_build_cancel
- expo_testflight_crashes
- expo_testflight_feedback
- show_version
- report_bug
- connect
- toolkit_info
- marketplace
- authenticate
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.