
Rush MCP Server (Rush Stack): Setup for Claude, Cursor and Other Apps
Lets Claude, Cursor and other assistants understand a Rush monorepo, check rush commands, fix pnpm lockfile conflicts and move projects.
This is the Rush Stack team's own MCP server for Rush monorepos. It gives an assistant a map of your projects and a check for rush and rushx commands, so it needs less guessing in a large repo. It can also fix lockfile conflicts and move projects.
It runs on your computer and needs the path to your Rush workspace as its first argument. The README also suggests copying the repo's .cursor folder into your project for better results.
Good for
- Teams that build with the Rush monorepo manager
- Developers whose monorepo is too big for an assistant to read whole
- Anyone who keeps hitting pnpm-lock.yaml merge conflicts
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install Rush MCP
Claude Code
- 1
Copy this prompt.
Add the Rush MCP server to Claude Code. Run this command: claude mcp add rush -- npx -y @rushstack/mcp-server /path/to/your-rush-monorepo Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js, A Rush monorepo.
Replace /path/to/your-rush-monorepo with the folder that holds rush.json. The server needs that folder as its first argument and stops without it.
Built from the package data we hold. Not yet tested by us. Source.
Tools
Gives an overview of every project in your Rush monorepo
Returns the projects in your Rush workspace and how they relate, so the assistant can answer questions about your architecture.
Try: “Give me an overview of the projects in this monorepo.”
Files ·
rush_workspace_detailsShows the full details of one Rush project
Returns the Rush details of a single project, such as its folder, in JSON.
Try: “Show me the details of the @acme/web project.”
Files ·
rush_project_detailsChecks a rush or rushx command before you run it
Checks a command against your repo's command-line.json and asks for missing project selection flags. It does not run the command.
Try: “Check that this rush build command is valid for my repo.”
Files ·
rush_command_validatorFixes a merge conflict in pnpm-lock.yaml
Runs git checkout --theirs on the lockfile, then rush update for its subspace, to regenerate it. This changes your files.
Try: “Resolve the conflict in my pnpm-lock.yaml.”
Runs code ·
rush_pnpm_lock_file_conflict_resolverMoves a project to another folder or subspace
Moves a project folder to a new path and subspace and updates rush.json and subspaces.json. If the old subspace is left empty, it deletes that subspace config folder.
Try: “Move the @acme/web project into the apps subspace.”
Delete ·
rush_migrate_project
Read from the source code
Permissions
high risk · 3 things to watch
High risk
It edits and moves files in your repo, can delete an emptied subspace folder, and runs git and rush commands for the lockfile fix. Work on a clean git branch so you can review or revert what it changes.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It can move projects and delete a folder
The migrate tool moves a project folder and, if a subspace is left empty, deletes its config folder. Commit your work first. github.com
The lockfile fix runs git and rush
It runs git checkout --theirs on the lockfile, then rush update. Check the diff afterwards. github.com
The folder argument is required
The server stops if you do not pass a workspace path. Point it at the repo you want to work on. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Sign-in and keys | No sign-in. It reads the Rush workspace folder you point it at. |
|---|
Questions
Is the Rush MCP server official?
Yes. It is published by Microsoft's Rush Stack team from the same repository as Rush, as @rushstack/mcp-server.
Does it need an API key?
No. There is no sign-in or key. You pass the path to your Rush workspace as its first argument.
Is it local or hosted?
Local. It runs on your computer over stdio and reads your Rush workspace.
Can it run in read-only mode?
No. The source has no read-only setting. Three of the five tools only read, and you can switch off the other two in your AI app.
Does it have a documentation search tool?
The README lists a rush_docs tool, but the 0.4.32 source registers five other tools and not that one.
Does it only work with Rush?
Yes. The tools read Rush files such as rush.json and command-line.json, so it is for Rush monorepos.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
@rushstack/mcp-server- Registry
- npm
- Transport
- stdio
- Auth
- None
- Version
- 0.4.32
- License
- MIT
- Last commit
- Oct 31, 2026
- Open issues
- 947
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 5Hide
- github.com · github.com
- github.com · github.com
- github.com · github.com
- github.com · github.com
- github.com · github.com