➖ chore: remove nx-mcp and use native Nx CLI commands

Replace nx-mcp server tooling with native Nx CLI commands across
documentation files. Updates docs-researcher agent, CLAUDE.md, and
AGENTS.md to reference npx nx show/graph commands directly.

.claude/agents/docs-researcher.md

@@ -20,11 +20,6 @@ You are an elite documentation research specialist with expertise in rapidly loc
    - Use `get_best_practices` for Angular conventions
    - Best for: Angular APIs, components, directives, services
 
-3. **Nx MCP** (`mcp__nx-mcp__*`)
-   - Use `nx_docs` for Nx-specific documentation
-   - Use `nx_workspace` for monorepo structure understanding
-   - Best for: Nx commands, configuration, generators, executors
-
 ### Tier 2: Local Documentation (Use for ISA-specific)
 - **Read tool**: For internal library READMEs (`libs/[domain]/[layer]/[feature]/README.md`)
 - **Grep tool**: For searching code patterns and examples within the project
@@ -59,10 +54,11 @@ You are an elite documentation research specialist with expertise in rapidly loc
 
 ### Nx/Monorepo Queries
 ```
-1. Use mcp__nx-mcp__nx_docs with user query
+1. Use WebSearch or Context7 for Nx documentation
 2. IF workspace-specific:
-   - Use mcp__nx-mcp__nx_workspace for structure
-   - Use mcp__nx-mcp__nx_project_details for specific projects
+   - Use `npx nx show projects` to list projects
+   - Use `npx nx show project <name>` for project details
+   - Use `npx nx graph` for dependency visualization
 3. Extract: Commands, configuration, best practices
 ```
 

.mcp.json

@@ -4,11 +4,6 @@
       "type": "http",
       "url": "https://mcp.context7.com/mcp"
     },
-    "nx-mcp": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["nx", "mcp"]
-    },
     "angular-mcp": {
       "type": "stdio",
       "command": "npx",

AGENTS.md

@@ -3,11 +3,11 @@
 
 # General Guidelines for working with Nx
 
-- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
-- You have access to the Nx MCP server and its tools, use them to help the user
-- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
-- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
-- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
-- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+- When running tasks (build, lint, test, e2e, etc.), always use the Nx CLI (`nx run`, `nx run-many`, `nx affected`) instead of underlying tooling directly
+- Use `npx nx show projects` to list all projects in the workspace
+- Use `npx nx show project <name>` to analyze specific project structure and dependencies
+- Use `npx nx graph` to visualize project dependencies
+- For Nx documentation, use Context7 or WebSearch to find up-to-date docs
+- If the user needs help with an Nx configuration or project graph error, run `npx nx report` for diagnostic info
 
 <!-- nx configuration end-->

CLAUDE.md

@@ -185,9 +185,9 @@ Extract only what's needed, discard the rest:
 
 # General Guidelines for working with Nx
 
-- Run tasks through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of underlying tooling
-- Use `nx_workspace` tool to understand workspace architecture
-- Use `nx_project_details` for specific project structure
-- Use `nx_docs` for nx configuration questions
+- Run tasks through `nx` CLI (`nx run`, `nx run-many`, `nx affected`) instead of underlying tooling
+- Use `npx nx show projects` to list all projects in the workspace
+- Use `npx nx show project <name>` to analyze specific project structure and dependencies
+- Use `npx nx graph` to visualize project dependencies
 
 <!-- nx configuration end-->