Summary
The dev loop, including the processes that stay alive.
Most file-editing servers stop at the write; this one keeps the dev server running and lets you read its output, which is where React build errors actually appear. It also runs arbitrary terminal commands, so point it at a project directory you are willing to hand over.
What it is
A server that hands a client a React development environment: create an application, run it, edit its files, install packages, run terminal commands, and manage the processes those commands start.
What you get
- A new React application created, optionally from a template, and its dev server started (create-react-app, run-react-app)
- Project files read and edited (read-file, edit-file)
- Npm packages installed into the project (install-package)
- Arbitrary terminal commands executed (run-command)
- Long-running processes tracked, their output read as it arrives, and stopped when finished with (list-processes, get-process-output, stop-process)
- JSON and text logs of what ran, with timestamps
Requirements
Node, with the server started from a local checkout by absolute path to index.js. Automatic installation through Smithery is also documented.
Setup effort
One command — npx -y @smithery/cli install @Streen9/react-mcp --client claude