https://github.com/Streen9/react-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create-react-appC | Create a new React application |
| run-react-appC | Run a React application in development mode |
| run-commandC | Run a terminal command |
| get-process-outputB | Get the output from a running or completed process |
| stop-processB | Stop a running process |
| list-processesA | List all running processes |
| edit-fileC | Create or edit a file |
| read-fileB | Read the contents of a file |
| install-packageC | Install a npm package in a project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.