Nx Mcp

What is Nx Mcp?

Nx Mcp is a Model Context Protocol server that gives large language models deep access to an Nx monorepo’s structure: project relationships, file mappings, runnable tasks, ownership info, tech stacks, Nx generators, and Nx documentation. It helps AI generate code tailored to the workspace’s stack, understand change impact, and apply modifications across connected files.

How to use Nx Mcp?

You can run the server via npx nx-mcp@latest (stdio) or with --sse and --port flags for HTTP transport. Alternatively, install the Nx Console extension in Cursor, which manages the server automatically. The server runs in minimal mode by default; use --no-minimal to expose all tools. A JSON config file can be placed at .nx/nx-mcp-config.json.

Key features of Nx Mcp

• Gives LLMs workspace project graph and nx.json configuration
• Exposes task execution details and terminal output
• Provides Nx documentation snippets relevant to queries
• Visualizes the Nx graph (requires running IDE)
• Nx Cloud CI tools: pipeline info, failed task output, self-healing fix management
• Minimal mode reduces tool clutter by hiding overlapping analysis tools

Use cases of Nx Mcp

• AI generates code that respects monorepo project boundaries and dependencies
• Developers get context-aware code modifications across connected projects
• Understand the impact of changes by querying the project graph
• Debug CI failures by retrieving task output from Nx Cloud runs
• Automate Nx generator usage based on developer natural language requests

FAQ from Nx Mcp

What tools are hidden in minimal mode?

The following are hidden: nx_available_plugins, nx_workspace_path, nx_workspace, nx_project_details, nx_generators, and nx_generator_schema. Use the --no-minimal flag to show them.

Do I need Nx Cloud to use all tools?

Nx Cloud tools (ci_information, ci_task_output, update_self_healing_fix) and the CI Pipeline Execution resources are only available when the workspace is connected to Nx Cloud.

How do I configure the server when I can’t pass CLI args?

Place a JSON configuration file at .nx/nx-mcp-config.json in your workspace root. All keys are optional; CLI arguments take precedence over file values.

What transports are supported?

The server supports stdio by default, and SSE (with --sse and --port flags) for HTTP transport with multiple concurrent connections.

Where does my workspace data live?

The server reads local workspace files (project graph, nx.json, etc.) and optionally communicates with Nx Cloud CI endpoints. No data is sent outside your environment unless you use Nx Cloud features.