expo-mcp
by SajidAlee1
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPO_TOKEN | Yes | Authentication token for Expo/EAS actions. Create one at https://expo.dev/settings/access-tokens. | |
| EXPO_PROJECT_ROOT | No | Path to the Expo project root directory. Can also be set via --root flag. | |
| EXPO_DEV_SERVER_URL | No | Explicit Metro dev server URL. If omitted, the launcher auto-detects a local Metro/Expo server. | |
| EXPO_MCP_SERVER_URL | No | Tunnel server URL for remote MCP transport. If present, server runs in composite mode (stdio + tunnel). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues