npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@alivelabs/expo-orchestrator-mcp

v0.2.1

Published

Model Context Protocol server exposing the Expo CI Orchestrator API to AI agents (build, drive, screenshot iOS simulator sessions).

Readme

@alivelabs/expo-orchestrator-mcp

A Model Context Protocol server that exposes the Expo CI Orchestrator API to AI agents. It is a thin client of the orchestrator's REST API — point it at a running API and give it the master token, and an agent can build iOS apps, drive the simulator (taps/swipes/typing, or tap an element by its React Native testID), inspect the accessibility tree, and take screenshots.

Transport is stdio, so an MCP host spawns it as a subprocess.

Configuration

Two environment variables:

| Var | Required | Default | What | |-----|----------|---------|------| | EXPO_CI_API_TOKEN | ✅ | — | The orchestrator's master API token (API_TOKEN). | | EXPO_CI_API_URL | | http://localhost:3000 | Orchestrator base URL. |

Run

EXPO_CI_API_TOKEN=… bun run --filter '@alivelabs/expo-orchestrator-mcp' start

Register with an MCP client

Most clients take a command + args + env. Example (Claude Desktop / VS Code / Cursor all use this shape):

{
  "mcpServers": {
    "expo-ci": {
      "command": "bun",
      "args": ["/ABSOLUTE/PATH/alive-expo-orchestrator/apps/mcp/src/index.ts"],
      "env": {
        "EXPO_CI_API_TOKEN": "…",
        "EXPO_CI_API_URL": "http://localhost:3000"
      }
    }
  }
}

Tools

| Tool | Purpose | |------|---------| | list_simulators | List bootable simulators + the recommended default. | | create_session | Create a build session. Source: git / tarball / local. Options: simulatorName (default: recommended), appRoot (monorepo subdir), devServerUrl (⇒ Debug dev-client; omit ⇒ Release with the bundle embedded), env (extra build-time env vars, e.g. EXPO_PUBLIC_* / IOS_GOOGLE_MAPS_API_KEY). Uploads the tarball when sourceType=tarball. | | start_session | Start the build (prebuild + xcodebuild + boot + install + launch). | | get_session | Current status / timing / error. | | get_logs | Trailing build/run logs. | | screenshot | Current simulator screen as a JPEG image the agent can see. | | tap / swipe / type_text / press_button | Drive the simulator (tap/swipe coordinates are in screenshot pixels). | | tap_by_test_id | Tap the element whose React Native testID matches — resolved via the accessibility tree, no coordinates needed. | | describe_ui | Dump the frontmost app's accessibility tree as JSON (each node's identifier is its testID, frame its on-screen rect). | | create_viewer_token | Mint a session-scoped token for an end user (view + drive their session only). | | delete_session | Tear down the session. |

create_session env vars

env is a map of extra environment variables exposed to the build (names must be valid shell identifiers; ≤ 100 vars, values ≤ 8 KB). They're applied before the orchestrator's curated env, so they can never override controlled vars (PATH, BUILD_DIR, secrets, …). Use them for values your app reads at build time:

  • EXPO_PUBLIC_* → embedded into the JS bundle by Metro.
  • Native config read by a dynamic app.config.js/.ts during prebuild — e.g. IOS_GOOGLE_MAPS_API_KEY consumed via ios.config.googleMapsApiKey: process.env.IOS_GOOGLE_MAPS_API_KEY. (Static app.json can't read env; use app.config.js.)

These are not treated as secrets and may appear in verbose build logs; the orchestrator's secrets field (npm token / Apple team / signing cert) is the never-logged path.

Typical agent flow

  1. list_simulators → pick a simulatorName (or omit to use the recommended one).
  2. create_session (e.g. sourceType: "git", repoUrl, optional appRoot / devServerUrl / env).
  3. start_session → then poll get_session until completed (use get_logs on failure).
  4. See the app with screenshot; drive it with tap_by_test_id (preferred — use describe_ui to discover testIDs) or coordinate tap / type_text / swipe.
  5. Optionally create_viewer_token to hand a human a live view; delete_session when done.

Security

The server holds the master token — full control of all sessions. Keep it to the trusted host running the agent; hand end users a scoped token from create_viewer_token instead. A scoped token may only view + drive its own session (status, logs, screenshot, accessibility tree, input, tap-by-testID) — never create, start, delete, upload source, or mint further tokens. stdout is reserved for the MCP protocol; all diagnostics go to stderr.