Nx MCP
Gives an agent the dependency graph of an Nx monorepo, so it can answer which projects a change actually affects.
What it does
Gives an agent the dependency graph of an Nx monorepo, so it can answer which projects a change actually affects. On a large workspace that question is the difference between one build and forty. Best value in repositories where the graph is the hard part; redundant in a single-app repo.
Install
Terminal
npx -y nx-mcp
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
mcp.json
{
"mcpServers": {
"nx": {
"command": "npx",
"args": [
"-y",
"nx-mcp"
]
}
}
}
When to use it
Reach for this when the task needs monorepo inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other TypeScript servers
- Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
- Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
- Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude