protogrid

Search / io.github.mcp-dir/expo-mcp

Expo

R0· no sign-in

Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig

v0.1.0 · active · repository · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality83good
Trust91of 100
Uptime, 30 days98%
Latency p50169 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "expo-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_expo"
    }
  }
}
claude mcp add --transport http expo-mcp https://api.mcp.ai/p_expo
[mcp_servers.expo-mcp]
url = "https://api.mcp.ai/p_expo"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "expo-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_expo",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "expo-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_expo"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=expo-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLm1jcC5haS9wX2V4cG8ifQ%3D%3D"
}
{
  "servers": {
    "expo-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_expo"
    }
  }
}
{
  "mcpServers": {
    "expo-mcp": {
      "httpUrl": "https://api.mcp.ai/p_expo"
    }
  }
}
extensions:
  "expo-mcp":
    enabled: true
    name: "expo-mcp"
    type: streamable_http
    uri: "https://api.mcp.ai/p_expo"
    timeout: 300

Quality 83 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene93 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations25 of 25 tools declare readOnlyHint or destructiveHint
  • pass
    tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
  • pass
    tools.token_costabout 3,765 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability75 · weight 15
  • warn
    stability.changes100 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

25 tools, about 3,765 tokens to load them all · tool set 751d564fe0c7 · tools last changed 2026-10-15 · checked 2026-10-20 13:17 UTC

Tool changes

  • authenticateadded

    MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

  • marketplaceadded

    The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

  • toolkit_infoadded

    Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

  • connectadded

    Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

  • report_bugadded

    Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

  • show_versionadded

    Show the current MCP platform and adapter versions.

  • expo_testflight_feedbackadded

    Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.

  • expo_testflight_crashesadded

    Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.

  • expo_build_canceladded

    Cancels an EAS build that is queued or in progress. Use build_info to check the current status first.

  • expo_build_runadded

    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 "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 91 / 100

provenance80
liveness99
freshness85
hygiene100

+repository +namespace-matches-repo +reachable +uptime-98% ~updated-60d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://api.mcp.ai/p_expo streamable-httpnoneyes98%169 ms2025-11-252026-10-20

Tools (25)

authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
connectread-onlyReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
expo_add_libraryAdd an Expo library to the project using expo install and attach usage instructions when available
expo_build_cancelCancels an EAS build that is queued or in progress. Use build_info to check the current status first.
expo_build_inforead-onlyFetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details.
expo_build_listread-onlyLists 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 builds, their status, and available artifacts.
expo_build_logsread-onlyFetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.
expo_build_runTriggers 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 "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
expo_build_submitSubmits 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 type. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
expo_learnread-onlyLearn 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.
expo_read_documentationread-onlyFetch 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.
expo_search_documentationread-onlySearch 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.
expo_testflight_crashesread-onlyFetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.
expo_testflight_feedbackread-onlyFetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.
expo_workflow_cancelCancels a running EAS workflow. Use workflow_info to get the workflow run ID.
expo_workflow_createCreates 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.
expo_workflow_inforead-onlyFetches 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 has multiple jobs, draw them in a diagram to show the dependencies between jobs.
expo_workflow_listread-onlyLists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
expo_workflow_logsread-onlyFetches 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 call again with sectionIndex or phase to fetch that section.
expo_workflow_runTriggers 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 file must exist at the specified git reference.
expo_workflow_validateread-onlyValidates EAS workflow YAML syntax and configuration. Use this after creating a workflow to ensure it is valid. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show_versionread-onlyShow the current MCP platform and adapter versions.
toolkit_inforead-onlyReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Schemas: list_tools.

Similar MCP servers

More from io.github.mcp-dir

And 1,107 more from this publisher.

Official server.json
{
  "name": "io.github.mcp-dir/expo-mcp",
  "title": "Expo",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.mcp.ai/p_expo",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/mcp-dir/expo-mcp",
    "source": "github"
  },
  "description": "Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig"
}