Skip to main content
Glama
Sign In
https://github.com/Streen9/react-mcp

https://github.com/Streen9/react-mcp

by kalivaraprasad-gonapa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run-react-app

Run a React project in development mode to preview changes and debug issues.

Instructions

Run a React application in development mode

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": {
      "projectPath": "<projectPath>"
    },
    "name": "run-react-app"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the React project folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action, without mentioning side effects like port usage, blocking behavior, or how to stop the process. This is insufficient for safe invocation.

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

Conciseness2/5

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

The description is too brief for a tool that runs a development server. It saves space but at the cost of essential context. A single sentence is insufficient.

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?

Given the complexity of running a React app (dev server, possible browser launch, process lifecycle), the description omits many details. It assumes prior knowledge and does not cover return values or post-conditions.

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%, so the description adds no value beyond the schema's parameter description. The description repeats the schema's meaning without elaboration on path requirements.

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 action ('Run') and resource ('React application') with a specific mode ('development mode'). It distinguishes from siblings like create-react-app (create) and run-command (generic).

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 versus alternatives (e.g., run-command for non-React projects) or prerequisites (e.g., dependencies installed). The description lacks explicit exclusions or context.

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