Help us improve
Share bugs, ideas, or general feedback.
From Harness Mobile
Expo's hosted MCP (mcp.expo.dev, Streamable HTTP + OAuth) for EAS Build/Submit/Workflow inspection. Use when wiring or driving the Expo MCP for a React Native Expo project — listing/running builds and workflows, reading build logs, and respecting safety.two_key gating on billable build_run/build_submit/workflow_run calls.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-mobileHow this skill is triggered — by the user, by Claude, or both
Slash command
/harness-mobile:addon-expo-mcpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The agent has access to **Expo's hosted MCP** at `https://mcp.expo.dev/mcp` (Streamable HTTP + OAuth). Tools include:
Runs automated patient safety test suites for healthcare deployments, blocking on CRITICAL failures in CDSS accuracy, PHI exposure, and data integrity.
Share bugs, ideas, or general feedback.
The agent has access to Expo's hosted MCP at https://mcp.expo.dev/mcp (Streamable HTTP + OAuth). Tools include:
build_list, build_info, build_logs, build_run, build_cancel, build_submitworkflow_create, workflow_list, workflow_info, workflow_logs, workflow_run, workflow_cancel, workflow_validateOAuth via Expo accounts (reference standard post-Anodot). No EXPO_TOKEN in env. EAS paid plan required.
Calls that trigger billable resources (build_run, build_submit, workflow_run) should respect safety.two_key — if it's true, require a typed token before invoking.