Nx MCP

{
  "mcpServers": {
    "nx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "nx-mcp"
      ]
    }
  }
}

claude mcp add --transport stdio nx-mcp -- npx -y nx-mcp

{
  "mcpServers": {
    "nx-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "nx-mcp"
      ]
    }
  }
}

{
  "servers": {
    "nx-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "nx-mcp"
      ]
    }
  }
}

Config formats checked against the official docs on Oct 7, 2026: modelcontextprotocol.io (opens in a new tab), code.claude.com (opens in a new tab), cursor.com (opens in a new tab), code.visualstudio.com (opens in a new tab).

• nx_docs

  Returns documentation sections relevant to user queries about Nx

• nx_current_running_tasks_details

  Lists currently running Nx TUI processes and task statuses

• nx_current_running_task_output

  Returns terminal output for specific running tasks

• nx_visualize_graph

  Visualizes the Nx graph (requires running IDE instance)

• nx_available_plugins

  Lists available Nx plugins from the core team and local workspace plugins

• nx_workspace_path

  Returns the path to the Nx workspace root

• nx_workspace

  Returns readable representation of project graph and nx.json configuration

• nx_project_details

  Returns complete project configuration in JSON format for a given project

• nx_generators

  Returns list of generators relevant to user queries

• nx_generator_schema

  Returns detailed JSON schema for a specific Nx generator

• ci_information

  Retrieves CI pipeline execution information for the current branch or a specific Nx Cloud URL.

• ci_task_output

  Retrieves terminal output for a specific failed CI task, using a runId from ciinformation or resolving it from the…

• update_self_healing_fix

  Apply, reject, or request a rerun for a self-healing CI fix from Nx Cloud

A Model Context Protocol server implementation for Nx. The Nx MCP server gives LLMs deep access to your monorepo’s structure: project relationships, file mappings, runnable tasks, ownership info, tech stacks, Nx generators, and even Nx documentation. With this context, LLMs can generate code tailored to your stack, understand the impact of a change, and apply modifications across connected files with precision.