{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-add-mcp","slug":"npm-add-mcp","name":"add-mcp","type":"mcp","url":"https://www.npmjs.com/package/add-mcp","page_url":"https://unfragile.ai/npm-add-mcp","categories":["mcp-servers"],"tags":["cli","mcp","model-context-protocol","ai-agents","antigravity","cline","claude-code","claude-desktop","codex","cursor","github-copilot-cli","gemini-cli","goose","mcporter","opencode","vscode","zed"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-add-mcp__cap_0","uri":"capability://tool.use.integration.interactive.mcp.server.discovery.and.installation","name":"interactive-mcp-server-discovery-and-installation","description":"Provides a CLI-driven interactive discovery flow that identifies available MCP servers from a curated registry, presents them with metadata (description, capabilities, configuration requirements), and guides users through installation with dependency resolution. Uses a registry-based lookup pattern combined with interactive prompts to abstract away manual configuration complexity.","intents":["I want to add an MCP server to my coding agent without manually editing config files","Show me what MCP servers are available and help me pick the right one for my use case","I need to install an MCP server and have all its dependencies set up automatically"],"best_for":["developers using Claude Desktop, Cursor, VS Code, or other MCP-compatible agents who want frictionless server onboarding","non-technical users who want to extend their AI coding agents without touching configuration files","teams standardizing MCP server deployments across multiple agents"],"limitations":["Registry-dependent — only servers in the curated registry can be discovered; custom/private MCP servers require manual configuration","Single-command installation may not handle complex multi-step setup for servers with external dependencies (databases, services)","No built-in validation that installed servers are compatible with the target agent version"],"requires":["Node.js 16+ (npm or yarn package manager)","One of: Claude Desktop, Cursor, VS Code with MCP extension, Cline, or other MCP-compatible agent","Write access to agent configuration directory (~/.config or equivalent)"],"input_types":["CLI arguments (optional server name or filter)","Interactive user selections from prompted menu"],"output_types":["Installed MCP server with configuration written to agent config","Console output confirming installation status and next steps"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_1","uri":"capability://tool.use.integration.multi.agent.configuration.targeting","name":"multi-agent-configuration-targeting","description":"Detects installed coding agents (Claude Desktop, Cursor, VS Code, Cline, Zed, etc.) on the user's system and routes MCP server configuration to the correct agent-specific config file format and location. Uses filesystem scanning and agent-specific config schema knowledge to write configurations that each agent can parse and load.","intents":["I use multiple coding agents and want to add the same MCP server to all of them at once","Automatically detect which agents I have installed and configure them","I switched from Cursor to Claude Desktop and need to migrate my MCP servers"],"best_for":["power users who use multiple coding agents (Cursor + Claude Desktop + VS Code) and want consistent MCP server availability across all","teams managing MCP deployments across heterogeneous agent ecosystems","developers evaluating different agents who need quick setup/teardown"],"limitations":["Agent detection relies on standard installation paths — non-standard installations or portable versions may not be detected","Config schema differences between agents mean some servers may not work identically across all targets (e.g., environment variable handling)","No rollback mechanism if configuration write fails partway through multi-agent installation"],"requires":["Node.js 16+","At least one MCP-compatible agent installed in standard location","Filesystem read/write permissions to agent config directories"],"input_types":["CLI flag or interactive prompt to select target agents","MCP server name or configuration object"],"output_types":["Agent-specific config files updated with MCP server entry","Installation report showing which agents were configured successfully"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_2","uri":"capability://search.retrieval.mcp.server.registry.querying","name":"mcp-server-registry-querying","description":"Queries a centralized MCP server registry (likely maintained by Anthropic or community) to retrieve available servers, their metadata (name, description, capabilities, configuration parameters), and installation instructions. Uses HTTP-based registry API calls with caching to avoid repeated network requests and provide fast discovery.","intents":["What MCP servers are available and what can they do?","Find an MCP server that provides [specific capability, e.g., file system access, web search]","Get the latest version and installation instructions for a specific MCP server"],"best_for":["developers exploring the MCP ecosystem and discovering new servers","builders integrating MCP server discovery into their own tools","users who want to stay up-to-date with new MCP servers as they're released"],"limitations":["Registry availability is a hard dependency — offline mode is not supported","Registry only includes servers that maintainers have submitted; private/internal MCP servers are not discoverable","Metadata quality depends on registry maintainers; incomplete or outdated descriptions may mislead users","No built-in filtering by agent compatibility — a server in the registry may not work with all agents"],"requires":["Network connectivity to reach the MCP registry API","Node.js 16+"],"input_types":["Search query (server name, keyword, or capability)","Optional filters (category, language, maintainer)"],"output_types":["JSON array of server metadata objects","Human-readable formatted list for CLI display"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_3","uri":"capability://automation.workflow.dependency.resolution.and.validation","name":"dependency-resolution-and-validation","description":"Analyzes MCP server requirements (Node.js version, system dependencies, environment variables, optional tools) and validates that the target system meets them before installation. Performs version checks, binary availability checks, and environment variable validation to prevent failed installations. May suggest remediation steps if dependencies are missing.","intents":["Before installing an MCP server, check if my system has all required dependencies","I got an error installing an MCP server — help me understand what's missing","Automatically install or suggest how to install missing system dependencies"],"best_for":["developers on heterogeneous systems (macOS, Linux, Windows) who want to avoid installation failures","teams setting up MCP servers in CI/CD or containerized environments where dependency availability is critical","non-technical users who need clear error messages and remediation guidance"],"limitations":["Validation is static and declarative — cannot detect runtime issues that only surface after server startup","System dependency detection is OS-specific and may miss edge cases (e.g., custom build configurations)","Cannot automatically install system-level dependencies on all platforms (e.g., requires sudo on Linux, may fail on locked-down systems)","No support for optional dependencies — treats all declared dependencies as required"],"requires":["Node.js 16+","Access to system PATH to check for binary availability","Ability to read environment variables"],"input_types":["MCP server metadata (dependency declarations)","Current system state (Node.js version, installed binaries, environment)"],"output_types":["Validation report (pass/fail per dependency)","Remediation suggestions (e.g., 'Install Node.js 18+', 'Set OPENAI_API_KEY environment variable')","Installation blockers or warnings"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_4","uri":"capability://automation.workflow.configuration.file.writing.and.formatting","name":"configuration-file-writing-and-formatting","description":"Writes MCP server configuration to agent-specific config files (JSON, YAML, or other formats) with proper formatting, indentation, and schema compliance. Handles config merging (adding new servers to existing configs without overwriting), backup creation, and validation that written configs are parseable by the target agent.","intents":["Add an MCP server to my agent's config without manually editing JSON","I accidentally broke my config file — restore from backup and try again","Ensure my config changes are valid before the agent tries to load them"],"best_for":["users who are uncomfortable editing JSON/YAML config files manually","teams that want to automate MCP server provisioning without manual config management","developers building tools that programmatically manage MCP server configurations"],"limitations":["Config schema validation is agent-specific and may lag behind agent updates","Backup creation adds disk I/O overhead; backups are not automatically cleaned up (disk space management is user's responsibility)","Merge logic assumes config structure is well-formed; corrupted configs may not merge correctly","No support for config templating or variable substitution — all values must be concrete"],"requires":["Node.js 16+","Write access to agent config directory","Agent config file must exist (or tool creates it from template)"],"input_types":["MCP server configuration object (name, command, args, environment)","Target agent type (Claude Desktop, Cursor, etc.)","Optional: backup flag"],"output_types":["Updated agent config file (JSON/YAML)","Backup of previous config (if enabled)","Validation report confirming config is parseable"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_5","uri":"capability://automation.workflow.interactive.server.configuration.prompting","name":"interactive-server-configuration-prompting","description":"Guides users through configuring MCP server parameters (command, arguments, environment variables, resource limits) via interactive CLI prompts with sensible defaults and validation. Collects required configuration, validates inputs, and generates the final config object without requiring users to understand MCP server configuration syntax.","intents":["I want to add an MCP server but don't know what configuration parameters it needs","Help me set environment variables (like API keys) for my MCP server","Validate that my MCP server configuration is correct before saving it"],"best_for":["non-technical users who want to configure MCP servers without reading documentation","developers who want to avoid manual config file editing","teams onboarding new developers to MCP server setup"],"limitations":["Interactive prompts are CLI-only; no GUI support for complex configuration scenarios","Validation is basic (type checking, required fields) — does not validate that config will actually work at runtime","No support for complex nested configuration structures; only flat key-value pairs","Prompts may be verbose for servers with many configuration options, leading to user fatigue"],"requires":["Node.js 16+","Interactive terminal (TTY) — does not work in non-interactive environments (CI/CD, piped input)"],"input_types":["User responses to interactive prompts (text input, yes/no selections)","MCP server configuration schema (parameter names, types, descriptions)"],"output_types":["Validated configuration object","Formatted config ready to write to agent config file"],"categories":["automation-workflow","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_6","uri":"capability://automation.workflow.mcp.server.installation.command.execution","name":"mcp-server-installation-command-execution","description":"Executes the installation command for an MCP server (typically npm install or similar) in the appropriate context (global, local, or agent-specific directory) with proper error handling, output capture, and status reporting. Manages process spawning, environment variable passing, and timeout handling to ensure reliable installation.","intents":["Install an MCP server and all its dependencies with a single command","Run the MCP server installation in the correct directory/context","Get clear feedback on whether the installation succeeded or failed"],"best_for":["developers who want to automate MCP server installation without manual npm commands","CI/CD pipelines provisioning MCP servers in containerized or cloud environments","teams standardizing MCP server deployment across multiple machines"],"limitations":["Installation success depends on npm registry availability and network connectivity","No rollback mechanism if installation partially succeeds but server is non-functional","Timeout handling is fixed; long-running installations may be terminated prematurely","Error messages from npm are passed through as-is; may be cryptic for non-technical users"],"requires":["Node.js 16+ with npm or yarn","Network connectivity to npm registry","Write access to installation directory"],"input_types":["MCP server name or package identifier","Installation context (global, local, agent-specific)","Optional: npm flags or custom installation command"],"output_types":["Installation status (success/failure)","Captured stdout/stderr from installation process","Installed package version and location"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-add-mcp__cap_7","uri":"capability://automation.workflow.installation.status.reporting.and.verification","name":"installation-status-reporting-and-verification","description":"Verifies that an installed MCP server is functional by checking that the server binary/script exists, is executable, and can be invoked successfully (e.g., responds to --version or --help). Reports installation status with clear success/failure messages and suggests next steps or troubleshooting actions.","intents":["Confirm that my MCP server installation was successful","Check if an MCP server is properly installed and ready to use","Get troubleshooting guidance if an MCP server installation failed"],"best_for":["users who want confidence that their MCP server is ready before using it","CI/CD pipelines that need to verify MCP server availability before running tests","support teams diagnosing MCP server installation issues"],"limitations":["Verification is shallow — checks only that the binary exists and is executable, not that it's fully functional","Cannot detect runtime issues that only surface when the agent actually tries to use the server","Verification may fail for servers that don't support --version or --help flags","No built-in diagnostics for common failure modes (missing dependencies, permission issues, etc.)"],"requires":["Node.js 16+","Ability to execute binaries and check file permissions"],"input_types":["MCP server name or installation path","Agent configuration (to verify server is registered)"],"output_types":["Verification status (success/failure)","Details on what was checked (binary existence, executability, version output)","Troubleshooting suggestions if verification failed"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+ (npm or yarn package manager)","One of: Claude Desktop, Cursor, VS Code with MCP extension, Cline, or other MCP-compatible agent","Write access to agent configuration directory (~/.config or equivalent)","Node.js 16+","At least one MCP-compatible agent installed in standard location","Filesystem read/write permissions to agent config directories","Network connectivity to reach the MCP registry API","Access to system PATH to check for binary availability","Ability to read environment variables","Write access to agent config directory"],"failure_modes":["Registry-dependent — only servers in the curated registry can be discovered; custom/private MCP servers require manual configuration","Single-command installation may not handle complex multi-step setup for servers with external dependencies (databases, services)","No built-in validation that installed servers are compatible with the target agent version","Agent detection relies on standard installation paths — non-standard installations or portable versions may not be detected","Config schema differences between agents mean some servers may not work identically across all targets (e.g., environment variable handling)","No rollback mechanism if configuration write fails partway through multi-agent installation","Registry availability is a hard dependency — offline mode is not supported","Registry only includes servers that maintainers have submitted; private/internal MCP servers are not discoverable","Metadata quality depends on registry maintainers; incomplete or outdated descriptions may mislead users","No built-in filtering by agent compatibility — a server in the registry may not work with all agents","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.902Z","last_scraped_at":"2026-05-03T14:23:51.839Z","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-add-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-add-mcp"}},"signature":"oOFZa9+er95/zaPVS32QCOdIlZGS3vHvUBGO2PxOmeWfrYI5to4vaSJaZL0CbfEB6lvXs0Un+mAC3nY1/cPLBA==","signedAt":"2026-06-22T01:52:56.000Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-add-mcp","artifact":"https://unfragile.ai/npm-add-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-add-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"}}