add-mcp
MCP ServerFreeAdd MCP servers to your favorite coding agents with a single command.
Capabilities8 decomposed
interactive-mcp-server-discovery-and-installation
Medium confidenceProvides 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.
Abstracts MCP server installation behind a single interactive CLI command that handles registry lookup, dependency resolution, and agent-specific configuration writing — eliminating manual JSON editing and multi-step setup that competitors require
Faster onboarding than manual MCP server setup (which requires editing config files directly) and more discoverable than raw MCP specifications because it surfaces available servers with human-readable descriptions and guided selection
multi-agent-configuration-targeting
Medium confidenceDetects 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.
Implements agent-specific config writers that understand Claude Desktop's JSON schema, Cursor's config format, VS Code's settings.json structure, and other agent formats — enabling single-command multi-agent setup instead of per-agent manual configuration
Eliminates repetitive manual configuration across multiple agents by auto-detecting installed agents and writing format-correct configs, whereas competitors typically require separate setup steps per agent or don't support multi-agent scenarios
mcp-server-registry-querying
Medium confidenceQueries 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.
Provides a queryable registry abstraction that surfaces MCP server metadata in a structured, searchable format — enabling programmatic discovery and filtering rather than requiring users to manually browse documentation or GitHub
More discoverable than raw MCP server GitHub repos because it centralizes metadata and enables search/filtering; faster than manual documentation review because metadata is machine-readable and cached locally
dependency-resolution-and-validation
Medium confidenceAnalyzes 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.
Implements pre-flight validation that checks system state against MCP server requirements before installation, preventing failed setups and providing actionable remediation guidance — rather than letting installations fail silently or with cryptic errors
Prevents installation failures by validating dependencies upfront, whereas manual setup often results in runtime errors; more user-friendly than raw npm install because it explains what's missing and how to fix it
configuration-file-writing-and-formatting
Medium confidenceWrites 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.
Implements agent-aware config writers that understand each agent's config schema and merge logic, enabling safe, non-destructive configuration updates without manual JSON editing or risk of corruption
Safer than manual config editing because it validates syntax and creates backups; more reliable than copy-paste because it handles merging and schema compliance automatically
interactive-server-configuration-prompting
Medium confidenceGuides 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.
Implements schema-driven interactive prompting that reads MCP server configuration requirements and generates targeted prompts with validation and defaults — eliminating the need for users to manually construct config objects or read documentation
More user-friendly than manual config file editing because it guides users step-by-step; more discoverable than documentation because prompts surface required parameters inline
mcp-server-installation-command-execution
Medium confidenceExecutes 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.
Wraps npm package installation with context-aware directory selection, environment variable management, and error handling — abstracting away the complexity of installing MCP servers in the correct location for each agent
More reliable than manual npm install because it handles context selection and error reporting; more discoverable than raw npm commands because it integrates with the interactive discovery flow
installation-status-reporting-and-verification
Medium confidenceVerifies 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.
Implements post-installation verification that confirms the MCP server is executable and responsive, providing immediate feedback on installation success rather than deferring discovery of issues until the agent tries to use the server
Catches installation failures immediately rather than at runtime; more proactive than waiting for agent errors because it verifies server health as part of the installation flow
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with add-mcp, ranked by overlap. Discovered automatically through the match graph.
mcp-get
** - Command line tool for installing and managing MCP servers by **[Michael Latman](https://github.com/michaellatman)**
@smithery/cli
An NPX command to install and list Model Context Protocols from Smithery
1mcpserver
** - MCP of MCPs. Automatic discovery and configure MCP servers on your local machine. Fully REMOTE! Just use [https://mcp.1mcpserver.com/mcp/](https://mcp.1mcpserver.com/mcp/)
agent-scan
Security scanner for AI agents, MCP servers and agent skills.
install-mcp
A CLI tool to install and manage MCP servers.
AllInOneMCP
MCP of MCPs. A central hub for MCP servers. Helps you discover available MCP servers and learn how to install and use them. REMOTE! Use the url [https://mcp.pfvc.io/mcp/](https://mcp.pfvc.io/mcp/) to add the server. **Remember the final backslash\*\*.
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
- ✓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
- ✓developers exploring the MCP ecosystem and discovering new servers
- ✓builders integrating MCP server discovery into their own tools
Known 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
- ⚠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
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Package Details
About
Add MCP servers to your favorite coding agents with a single command.
Categories
Alternatives to add-mcp
Are you the builder of add-mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →