Skip to main content
Glama
Sign In
React Native Expo MCP

React Native Expo MCP

by Divagnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

expo_dev_start

Launch an Expo development server with QR code to test your app on iOS, Android, or web devices.

Instructions

Start Expo development server with QR code for device testing

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "expo_dev_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform to target (default: all)
clear_cacheNoClear Metro bundler cache
portNoPort number for dev server
qr_formatNoQR code format (default: terminal)
offlineNoRun in offline mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description does not disclose behavioral traits such as blocking nature, server lifecycle, authentication needs, or error conditions. The schema covers parameters but not runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it could be more structured (e.g., front-loading key facts). It is concise but possibly too brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 optional parameters and no output schema or annotations, the description is insufficient. It does not explain return values, side effects, or when to use this tool in a development workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema (e.g., does not explain parameter relationships or defaults beyond enum values).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Start') and identifies the resource ('Expo development server') and outcome ('QR code for device testing'). It clearly distinguishes from siblings like expo_dev_stop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (e.g., expo_build_start) or prerequisites (e.g., project setup). The description lacks context on usage conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools