{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-nx-mcp","slug":"npm-nx-mcp","name":"nx-mcp","type":"mcp","url":"https://www.npmjs.com/package/nx-mcp","page_url":"https://unfragile.ai/npm-nx-mcp","categories":["mcp-servers"],"tags":["nx","monorepo","ai","mcp","model","context","protocol"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-nx-mcp__cap_0","uri":"capability://tool.use.integration.monorepo.task.graph.introspection.via.mcp","name":"monorepo task graph introspection via mcp","description":"Exposes Nx's internal task graph and project dependency metadata through the Model Context Protocol, allowing AI clients to query project structure, task definitions, and dependency relationships without direct filesystem access. Implements MCP resource handlers that serialize Nx's graph data structures into JSON-RPC responses, enabling stateless queries of monorepo topology.","intents":["I need an AI assistant to understand my monorepo's project structure and dependencies","I want Claude or another LLM to analyze which projects are affected by a code change","I need to query task definitions and their configurations programmatically through an AI interface"],"best_for":["teams using Nx monorepos who want AI-assisted code analysis and refactoring","developers building LLM agents that need to reason about monorepo topology","organizations integrating AI coding assistants with existing Nx workflows"],"limitations":["requires Nx workspace to be initialized and graph to be computed before MCP server starts","graph queries are read-only — cannot modify task definitions or project structure through MCP","performance degrades with very large monorepos (1000+ projects) due to full graph serialization"],"requires":["Nx 15.0 or higher","Node.js 16+","MCP-compatible client (Claude Desktop, custom LLM integration, etc.)"],"input_types":["JSON-RPC method calls with project names or task identifiers"],"output_types":["JSON-serialized project metadata","task graph structures","dependency relationship maps"],"categories":["tool-use-integration","monorepo-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_1","uri":"capability://automation.workflow.ai.assisted.task.execution.with.context.injection","name":"ai-assisted task execution with context injection","description":"Implements MCP tools that allow AI clients to trigger Nx task execution (build, test, lint, etc.) with automatic context injection about affected projects and dependencies. Wraps nx exec/run commands through MCP tool handlers that capture task output, exit codes, and logs, returning structured results to the AI client for decision-making.","intents":["I want an AI assistant to run tests for projects affected by my changes and report results","I need to execute a build task and have the AI analyze the output for errors","I want to delegate task execution to an AI agent that can retry or escalate based on results"],"best_for":["developers using AI coding assistants for autonomous code changes and validation","CI/CD teams building AI-powered code review and testing workflows","solo developers who want AI to handle build/test cycles during development"],"limitations":["task execution is synchronous — long-running tasks (e.g., integration tests) may timeout depending on MCP client timeout settings","no built-in caching of task results — each execution re-runs even if inputs haven't changed","requires proper environment setup (dependencies installed, credentials available) in the MCP server process"],"requires":["Nx 15.0+","Node.js 16+","all project dependencies installed (npm/yarn/pnpm)","MCP client with tool-calling support"],"input_types":["task name (string)","project filter (string or array)","configuration overrides (JSON object)"],"output_types":["task execution status (success/failure)","stdout/stderr logs (text)","exit code (integer)","structured error messages"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_2","uri":"capability://memory.knowledge.project.scoped.code.context.retrieval.for.ai.analysis","name":"project-scoped code context retrieval for ai analysis","description":"Provides MCP resources that return filtered, project-specific source code and configuration files to AI clients, implementing smart context windowing based on project boundaries and dependency relationships. Uses Nx's project metadata to determine file inclusion/exclusion, reducing irrelevant context sent to LLMs and improving token efficiency.","intents":["I want Claude to analyze only the relevant source files for a specific project without seeing unrelated monorepo code","I need to get configuration files and dependencies for a project to help an AI understand its setup","I want an AI assistant to have context about a project's structure without overwhelming it with the entire monorepo"],"best_for":["teams with large monorepos (50+ projects) who need to limit context sent to LLMs","developers using AI for code generation within specific project boundaries","organizations optimizing LLM API costs by reducing token usage per request"],"limitations":["context retrieval is static — doesn't track real-time file changes unless MCP client polls for updates","large source files (>100KB) may still exceed LLM context windows even when scoped to a project","binary files and non-text assets are excluded, limiting AI's ability to understand resource-heavy projects"],"requires":["Nx 15.0+","Node.js 16+","project source files accessible from MCP server process"],"input_types":["project name (string)","file type filter (optional, e.g., 'src', 'config')"],"output_types":["source code files (text)","configuration files (JSON/YAML/TOML)","package.json and dependency manifests","project metadata (tsconfig, eslint config, etc.)"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_3","uri":"capability://planning.reasoning.affected.projects.detection.and.change.impact.analysis","name":"affected projects detection and change impact analysis","description":"Exposes Nx's affected project detection algorithm through MCP tools, allowing AI clients to query which projects are impacted by code changes in specific files or branches. Implements handlers that call nx affected with various filters and return structured lists of affected projects, enabling AI to make informed decisions about what to test or rebuild.","intents":["I want an AI to determine which projects need testing after I modify a shared library","I need to know the impact scope of a change before asking an AI to generate fixes across the monorepo","I want an AI agent to automatically identify and run tests only for affected projects to save CI time"],"best_for":["teams using Nx for monorepo management who want AI-assisted impact analysis","CI/CD pipelines that need to optimize test runs based on change scope","developers working on shared libraries who need to understand downstream impacts"],"limitations":["affected detection requires git history — doesn't work in shallow clones or fresh repositories","accuracy depends on correct Nx project configuration and dependency declarations","branch-based affected detection requires git refs to be available (doesn't work in detached HEAD state)"],"requires":["Nx 15.0+","Node.js 16+","git repository with commit history","projects properly configured with Nx project.json files"],"input_types":["file paths (array of strings)","git branch/commit references (optional)","project filter patterns (optional)"],"output_types":["list of affected project names (array of strings)","affected project metadata (JSON)","dependency chain showing impact path"],"categories":["planning-reasoning","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_4","uri":"capability://memory.knowledge.workspace.configuration.and.plugin.metadata.exposure","name":"workspace configuration and plugin metadata exposure","description":"Provides MCP resources that expose Nx workspace configuration (nx.json, project.json files, plugin settings) and installed plugin metadata to AI clients. Serializes Nx's configuration objects and plugin registry into JSON-RPC responses, enabling AI to understand workspace-level settings, executor configurations, and available generators.","intents":["I want an AI to understand my Nx workspace configuration to generate code that follows our conventions","I need an AI assistant to know what generators and executors are available in our workspace","I want Claude to understand our monorepo's build and test configurations to make informed suggestions"],"best_for":["teams with custom Nx plugins who want AI to understand their workspace setup","organizations using AI for code generation that needs to respect workspace conventions","developers onboarding new team members with AI assistance that understands workspace structure"],"limitations":["configuration is static at MCP server startup — doesn't reflect runtime changes to nx.json","sensitive configuration (API keys, credentials) may be exposed if not filtered","custom plugin metadata requires plugins to export standard metadata format"],"requires":["Nx 15.0+","Node.js 16+","nx.json and project.json files readable from MCP server process"],"input_types":["workspace scope (optional, to filter specific projects or plugins)"],"output_types":["nx.json configuration (JSON)","project.json configurations (JSON array)","plugin registry and metadata (JSON)","executor and generator definitions (JSON)"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_5","uri":"capability://code.generation.editing.generator.invocation.and.code.scaffolding.through.ai","name":"generator invocation and code scaffolding through ai","description":"Implements MCP tools that allow AI clients to invoke Nx generators (schematics) with specified options, enabling autonomous code scaffolding and project creation. Wraps nx generate commands through tool handlers that accept generator names and option objects, execute the generator, and return results including created/modified files.","intents":["I want an AI to scaffold a new component following our project's conventions using Nx generators","I need an AI assistant to generate boilerplate code for a new service or library in our monorepo","I want Claude to create a new project with the correct structure and configuration automatically"],"best_for":["teams with custom Nx generators who want AI to use them for code scaffolding","developers using AI for rapid prototyping within Nx monorepos","organizations automating code generation workflows with AI agents"],"limitations":["generator execution is synchronous — complex generators with user prompts may timeout","requires generators to be idempotent or handle overwrite scenarios gracefully","AI may not understand all generator options without explicit documentation in workspace"],"requires":["Nx 15.0+","Node.js 16+","generators installed and available in workspace","MCP client with tool-calling support"],"input_types":["generator name (string)","generator options (JSON object)","project scope (optional)"],"output_types":["list of created files (array of strings)","list of modified files (array of strings)","generator execution status (success/failure)","error messages if generation fails"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_6","uri":"capability://planning.reasoning.dependency.graph.visualization.and.analysis.for.ai.reasoning","name":"dependency graph visualization and analysis for ai reasoning","description":"Exposes Nx's computed dependency graph through MCP resources in multiple formats (adjacency lists, edge lists, visual descriptions), enabling AI clients to reason about project relationships and identify circular dependencies or architectural issues. Implements graph serialization handlers that convert Nx's internal graph data structures into formats suitable for LLM analysis.","intents":["I want an AI to analyze our dependency graph and suggest architectural improvements","I need Claude to identify circular dependencies or problematic coupling in our monorepo","I want an AI assistant to explain the dependency relationships between projects to new team members"],"best_for":["architects using AI for monorepo design analysis and refactoring","teams with complex dependency graphs who want AI-assisted optimization","developers learning monorepo structure with AI-powered explanations"],"limitations":["graph visualization is text-based (no interactive diagrams) — large graphs may be hard for AI to reason about","graph analysis is static — doesn't detect runtime dependency issues or dynamic imports","very large graphs (1000+ projects) may exceed LLM context windows even in summarized form"],"requires":["Nx 15.0+","Node.js 16+","dependency graph computed (requires nx graph command to have run)"],"input_types":["project filter (optional, to analyze subgraph)","visualization format preference (adjacency list, edge list, text description)"],"output_types":["dependency graph in JSON format","text-based graph description","list of circular dependencies (if any)","graph statistics (node count, edge count, depth)"],"categories":["planning-reasoning","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nx-mcp__cap_7","uri":"capability://safety.moderation.lint.and.code.quality.rule.exposure.for.ai.assisted.fixes","name":"lint and code quality rule exposure for ai-assisted fixes","description":"Provides MCP resources that expose ESLint, Nx lint rules, and other code quality tool configurations to AI clients, including rule definitions, severity levels, and fix suggestions. Implements handlers that parse lint configuration files and return structured rule metadata, enabling AI to understand what violations to fix and how.","intents":["I want an AI to understand our linting rules so it can generate code that passes lint checks","I need Claude to explain why a lint error occurred and suggest fixes","I want an AI assistant to know about our custom lint rules when generating code"],"best_for":["teams with strict linting policies who want AI to respect them","developers using AI for code generation that needs to pass quality gates","organizations automating code review with AI that understands lint rules"],"limitations":["only exposes static rule definitions — doesn't run actual linting or detect violations","custom rule implementations may not be fully documented in configuration","rule severity and configuration may vary per project in monorepo"],"requires":["Nx 15.0+","Node.js 16+","ESLint or other lint tools configured in workspace"],"input_types":["project scope (optional, to get project-specific rules)","rule category filter (optional)"],"output_types":["lint rule definitions (JSON)","rule severity levels (error/warning/info)","rule descriptions and documentation","fix suggestions for common violations"],"categories":["safety-moderation","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"high","permissions":["Nx 15.0 or higher","Node.js 16+","MCP-compatible client (Claude Desktop, custom LLM integration, etc.)","Nx 15.0+","all project dependencies installed (npm/yarn/pnpm)","MCP client with tool-calling support","project source files accessible from MCP server process","git repository with commit history","projects properly configured with Nx project.json files","nx.json and project.json files readable from MCP server process"],"failure_modes":["requires Nx workspace to be initialized and graph to be computed before MCP server starts","graph queries are read-only — cannot modify task definitions or project structure through MCP","performance degrades with very large monorepos (1000+ projects) due to full graph serialization","task execution is synchronous — long-running tasks (e.g., integration tests) may timeout depending on MCP client timeout settings","no built-in caching of task results — each execution re-runs even if inputs haven't changed","requires proper environment setup (dependencies installed, credentials available) in the MCP server process","context retrieval is static — doesn't track real-time file changes unless MCP client polls for updates","large source files (>100KB) may still exceed LLM context windows even when scoped to a project","binary files and non-text assets are excluded, limiting AI's ability to understand resource-heavy projects","affected detection requires git history — doesn't work in shallow clones or fresh repositories","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.26,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.904Z","last_scraped_at":"2026-05-03T14:23:52.344Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-nx-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-nx-mcp"}},"signature":"ZeOXkPfhLGh9xY3IbaX1l5l2XViyoJ8YdKlRjP4kfHSGb5KAEStI2gyObtqSp5Op3/9LSR3xmCkiPal29p96CQ==","signedAt":"2026-06-21T23:49:34.418Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-nx-mcp","artifact":"https://unfragile.ai/npm-nx-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-nx-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}