PlugWiki
nx-console logo

Nx MCP Server: Setup for Claude Code, Cursor and Other Apps

OfficialLocal
Getnpmnx-mcpnrwl/nx-console

Lets Claude, Cursor and other assistants see your Nx monorepo: its projects, tasks and generators, the Nx docs, and failed Nx Cloud CI runs.

The Nx MCP server is made by the Nx team and ships as the nx-mcp package. It runs on your computer inside your Nx workspace and answers questions about projects, tasks, generators and the Nx docs. Out of the box it runs in a minimal mode that shows 7 of the 13 tools, so add the no-minimal option if your assistant should see the full project graph.

Good for

  • Developers on an Nx monorepo who want the assistant to know the project layout
  • Teams on Nx Cloud who want the assistant to read failed CI runs and apply fixes
  • Cursor and VS Code users who already have the Nx Console extension

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install nx-console MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the nx-console MCP server to Claude Code. Run this command:
    
    claude mcp add nx-console -- npx -y nx-mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Built from the package data we hold. Not yet tested by us.

Tools

  • Looks up the Nx documentation for a question

    Searches the Nx docs and returns the sections that match your question, so the assistant answers from current docs instead of memory.

    Try: “How do I set up a task pipeline so build runs after the dependencies build?”

    Read · nx_docs

  • Shows your projects and how they depend on each other

    Gives the assistant a readable map of your workspace: projects, their links and the nx.json settings. Hidden in minimal mode.

    Try: “Which projects depend on the shared-ui library?”

    Read · nx_workspace

  • Shows the full setup of one project

    Returns one project's full configuration, including its targets and settings. Hidden in minimal mode.

    Try: “Show me the build and test targets for the checkout app.”

    Read · nx_project_details

  • Finds code generators that fit what you want to build

    Lists the Nx generators that match your request, such as ones that create a new library or component. Hidden in minimal mode.

    Try: “Which generator creates a new React library in this workspace?”

    Read · nx_generators

  • Shows the options a generator accepts

    Returns the options and defaults of one generator so the assistant fills them in correctly. Hidden in minimal mode.

    Try: “What options does the library generator take?”

    Read · nx_generator_schema

  • Lists Nx plugins you can add

    Lists plugins from the Nx core team and any plugins in your own workspace. Hidden in minimal mode.

    Try: “Which Nx plugins could I add for a Node backend?”

    Read · nx_available_plugins

  • Lists the Nx tasks running right now

    Shows which Nx commands are running in your terminals and the status of each task.

    Try: “Which Nx tasks are running right now, and has any failed?”

    Read · nx_current_running_tasks_details

  • Reads the terminal output of a running task

    Returns what a running Nx task has printed so far, so the assistant can explain an error without you pasting it.

    Try: “Why is the e2e task failing? Read its output.”

    Read · nx_current_running_task_output

  • Opens the project or task graph in your editor

    Opens the project graph or a task graph in your IDE. It needs the Nx Console extension running in an editor.

    Try: “Show me the project graph focused on the api project.”

    Read · nx_visualize_graph

  • Shows CI pipeline results from Nx Cloud

    Reads the latest CI run for your branch or an Nx Cloud link, including which tasks failed. It only works with Nx Cloud turned on.

    Try: “What failed in CI on my current branch?”

    Network · ci_information

  • Reads the log of a failed CI task

    Fetches the terminal output of one failed CI task from Nx Cloud so the assistant can find the cause. It only works with Nx Cloud turned on.

    Try: “Show me the output of the failed lint task in CI.”

    Network · ci_task_output

  • Applies or rejects a fix Nx Cloud suggested for CI

    Records your decision on a fix that Nx Cloud proposed for a failed CI run: apply it or reject it. It changes state in Nx Cloud, so review the fix first.

    Try: “The suggested CI fix looks right. Apply it.”

    Write · update_self_healing_fix

Read from the source code

Permissions

medium risk · 4 things to watch

Medium risk

It reads your workspace configuration and task output, and one tool can approve or reject suggested CI fixes on Nx Cloud. Leave that tool out with a tool filter if you want read-only access.

What it can do

Watch out for

  • One tool can approve CI fixes in Nx Cloud

    update_self_healing_fix applies or rejects a suggested fix on Nx Cloud. Exclude it with the tool filter if you only want read access. github.com

  • It reads your whole workspace layout

    The server runs in your repo and can read project configuration and running task output. Task output can contain secrets printed by your scripts. github.com

  • Minimal mode hides six tools by default

    Run with the no-minimal option if your assistant needs the project graph, generators and plugin list. github.com

  • It has a telemetry setting

    The server has a disableTelemetry option and config key. Turn it on if you do not want usage reporting. github.com

Security advisories

No published security advisories for the MCP server as of Nov 1, 2026.

1 other advisory is about the wider nx-console project, not this MCP server. See them on GitHub

Technical details
Turning on read-onlyExclude the one write tool with the tools option, for example --tools '!update_self_healing_fix', or the tools key in .nx/nx-mcp-config.json. Documented in the nx-mcp README and CLI options.
Talks toNx Cloud (CI tools only)
Sign-in and keysNo separate sign-in. Nx Cloud tools use the Nx Cloud access your workspace already has.

Questions

Is the Nx MCP server official?

Yes. It is made by the Nx team (nrwl) and lives in the Nx Console repository.

Does it need an API key?

No. It runs in your workspace with no sign-in. The CI tools only return data when your workspace uses Nx Cloud.

Do I need the Nx Console extension?

No. You can run it on its own through the package. The extension manages it for you in Cursor and VS Code, and the graph viewer tool needs an editor with the extension running.

Why do I only see a few tools?

By default it runs in minimal mode, which hides six workspace tools to save space. Start it with the no-minimal option to get all of them.

Can I make it read-only?

Almost. Only one tool writes anything: it applies or rejects a suggested CI fix on Nx Cloud. Exclude it with the tool filter or the config file in your workspace.

Does it run locally or in the cloud?

Locally. It starts in your workspace over standard input and output, or on a local port if you ask for the HTTP option. The Nx Cloud tools talk to Nx Cloud.

Information

updated Nov 2, 2026

Publisher
Official
Package
nx-mcp
Registry
npm
Transport
stdio, Streamable HTTP
Version
0.25.0
License
MIT
Last commit
Oct 30, 2026
Open issues
25
Listed in
Official MCP registry

WebsiteGitHubnpmOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. github.com · github.com
  2. github.com · github.com
  3. www.npmjs.com · npmjs.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.