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

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

React MCP (Model Context Protocol)

A powerful server implementation that enables Claude AI to interact with React applications through the Model Context Protocol.

Sample Usage

Related MCP server: MCP-Claude Code Bridge

Overview

React MCP provides a bridge between Claude AI and the React ecosystem, allowing Claude to:

  • Create new React applications

  • Run React development servers

  • Manage files and directories

  • Install npm packages

  • Execute terminal commands

  • Track and manage long-running processes

This server implements the Model Context Protocol, providing Claude with the ability to perform real-world actions in the development environment.

Features

  • React Project Management

    • Create new React applications with optional templates

    • Run development servers

    • Manage dependencies

  • File Operations

    • Read and write files

    • Edit React components and configuration

  • Process Management

    • Start and monitor long-running processes

    • Track process output in real-time

    • Terminate processes when needed

  • Command Execution

    • Run arbitrary terminal commands

    • Install npm packages

    • Execute development tasks

  • Comprehensive Logging

    • Detailed JSON and text logs

    • Process tracking with timestamps

    • Execution history

Installation

Installing via Smithery

To install React MCP for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @Streen9/react-mcp --client claude

Manual Installation

  1. Clone this repository

  2. Install dependencies:

npm install

Usage

Add this in claude_desktop_config:

{
  "mcpServers": {
    "react-mcp": {
      "command": "node",
      "args": [
        "C:/Users/kalip/OneDrive/Desktop/react-mcp/index.js"
      ]
    },
  }
}

The server runs on the stdio transport, allowing it to be used with Desktop Claude APP as a Model Context Protocol tool.

Available Tools

create-react-app

Creates a new React application.

Parameters:

  • name (required): Name of the React app

  • template (optional): Template to use (e.g., typescript, cra-template-pwa)

  • directory (optional): Base directory to create the app in (defaults to home directory)

run-react-app

Runs a React application in development mode.

Parameters:

  • projectPath (required): Path to the React project folder

run-command

Runs a terminal command.

Parameters:

  • command (required): Command to execute

  • directory (optional): Directory to run the command in (defaults to current directory)

get-process-output

Gets the output from a running or completed process.

Parameters:

  • processId (required): ID of the process to get output from

stop-process

Stops a running process.

Parameters:

  • processId (required): ID of the process to stop

list-processes

Lists all running processes.

edit-file

Creates or edits a file.

Parameters:

  • filePath (required): Path to the file to edit

  • content (required): Content to write to the file

read-file

Reads the contents of a file.

Parameters:

  • filePath (required): Path to the file to read

install-package

Installs a npm package in a project.

Parameters:

  • packageName (required): Name of the package to install (can include version)

  • directory (optional): Directory of the project (defaults to current directory)

  • dev (optional): Whether to install as a dev dependency

check-installation-status

Checks the status of a package installation process.

Parameters:

  • processId (required): ID of the installation process to check

Logging

The server maintains detailed logs in the logs directory:

  • react-mcp-logs.json: Structured JSON logs

  • react-mcp-logs.txt: Human-readable text logs

Architecture

The server uses the following key components:

  • Model Context Protocol SDK: For communication with Claude AI

  • StdioServerTransport: For I/O through standard input/output

  • Zod: For schema validation and type safety

  • Child Process: For spawning and managing external processes

License

MIT

Author

@streen9

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Available Tools

9 tools
create-react-appC

Create a new React application

Inputs: name (required), template, directory.

edit-fileC

Create or edit a file

Inputs: content (required), filePath (required).

get-process-outputB

Get the output from a running or completed process

Inputs: processId (required).

install-packageC

Install a npm package in a project

Inputs: packageName (required), dev, directory.

list-processesA

List all running processes

Inputs: no named parameters.

read-fileB

Read the contents of a file

Inputs: filePath (required).

run-commandC

Run a terminal command

Inputs: command (required), directory.

run-react-appC

Run a React application in development mode

Inputs: projectPath (required).

stop-processB

Stop a running process

Inputs: processId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are mostly distinct: process management (list, stop, get output), file operations (read/edit), and React-specific actions (create/run app) are clearly separated. However, 'run-react-app' and generic 'run-command' could be confused if an agent doesn't read descriptions, and 'run-command' overlaps slightly with the dev server startup.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., stop-process, create-react-app, list-processes). No deviations or mixed conventions, making the naming predictable and intuitive.

    Tool Count5/5

    With 9 tools, the server covers the core React development workflow (create, run, manage processes, edit files, install packages) without redundancy. Each tool serves a clear purpose and the count is well within the ideal 3-15 range.

    Completeness4/5

    The toolset covers the essential React development lifecycle: project creation, dev server management, file editing, package installation, and process monitoring. Minor gaps like build/test commands or file deletion are missing but agents can work around them using run-command or edit-file.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers