# Expo Application Services MCP server

> Lets an AI client debug Expo builds, manage workflow runs, audit credentials, and roll out app updates via EAS.

- Repository: https://github.com/foreverworks/mcps
- Page: https://hostedmcp.org/servers/foreverworks/eas
- Transport: stdio
- Stars: 5
- License: MIT
- Latest version: 0.1.3

## Install

### Claude Code

```sh
claude mcp add --env 'EXPO_TOKEN_FILE=<EXPO_TOKEN_FILE>' eas -- npx -y @foreverworks/mcp-eas
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "eas": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-eas"
      ],
      "env": {
        "EXPO_TOKEN_FILE": "<EXPO_TOKEN_FILE>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "eas": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-eas"
      ],
      "env": {
        "EXPO_TOKEN_FILE": "<EXPO_TOKEN_FILE>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"eas","type":"stdio","command":"npx","args":["-y","@foreverworks/mcp-eas"],"env":{"EXPO_TOKEN_FILE":"<EXPO_TOKEN_FILE>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "eas": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-eas"
      ],
      "env": {
        "EXPO_TOKEN_FILE": "<EXPO_TOKEN_FILE>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add eas --env 'EXPO_TOKEN_FILE=<EXPO_TOKEN_FILE>' -- npx -y @foreverworks/mcp-eas
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.eas]
command = "npx"
args = ["-y", "@foreverworks/mcp-eas"]

[mcp_servers.eas.env]
EXPO_TOKEN_FILE = "<EXPO_TOKEN_FILE>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'EXPO_TOKEN_FILE=<EXPO_TOKEN_FILE>' eas npx -- -y @foreverworks/mcp-eas
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "eas": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-eas"
      ],
      "env": {
        "EXPO_TOKEN_FILE": "<EXPO_TOKEN_FILE>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `EXPO_TOKEN_FILE` | yes | no | Path of a file holding an Expo access token. |
| `EAS_PROJECT` | no | no | The project a call means when it names none, as @account/slug. |

## Tools (23)

- `health`
- `list_projects`
- `list_builds`
- `get_build`
- `list_workflows`
- `validate_workflow`
- `list_workflow_runs`
- `get_workflow_run`
- `wait_for_run`
- `get_job_logs`
- `list_submissions`
- `get_submission`
- `audit_credentials`
- `list_fingerprints`
- `list_updates`
- `cancel_build`
- `cancel_workflow_run`
- `set_submit_key`
- `submit_build`
- `republish_update`
- `set_rollout`
- `revert_rollout`
- `dispatch_workflow`

## FAQ

### How do I debug a failed Expo build?

You can use the server to find out why a build, workflow run, or store submission failed by accessing job logs by step and error text from Apple or Google.

### What is required to use this server?

You need an Expo account with an EAS project and an access token, ideally from a robot user with the Developer role.

### Does running workflows cost money?

Yes, dispatching a workflow runs build jobs that spend EAS build credits on your Expo plan.
