Skip to main content
Glama
Sign In
React Native Expo MCP

React Native Expo MCP

by Divagnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

expo_create_app

Initialize a new Expo/React Native project with customizable templates, skipping prompts and installing dependencies as needed.

Instructions

Create a new Expo/React Native project with template support

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_name": "<project_name>"
    },
    "name": "expo_create_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYesName of the new project
templateNoProject template (blank, tabs, bare, etc.)
npmNoUse npm instead of yarn
installNoInstall dependencies (default: true)
yesNoSkip all prompts (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description only states 'create' without disclosing side effects, permissions, or behavior on existing projects.

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

Conciseness3/5

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

The description is a single concise sentence but lacks structure such as front-loading key requirements or separating essential from optional details.

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?

No output schema and no annotation, and the description does not explain return values, success/failure behavior, or prerequisites, leaving gaps for a creation tool.

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 coverage is 100% with descriptions for all parameters, and the description does not add additional semantic value beyond what's in the schema.

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 clearly states the verb 'Create' and the resource 'Expo/React Native project' and mentions template support, distinguishing it from sibling tools like expo_install or eas_build.

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

Usage Guidelines3/5

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

Implied usage for creating a new project, but no explicit guidance on when to use or avoid this tool compared to alternatives.

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