{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-mcp-installer","slug":"mcp-installer","name":"MCP Installer","type":"mcp","url":"https://github.com/anaisbetts/mcp-installer","page_url":"https://unfragile.ai/mcp-installer","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-mcp-installer__cap_0","uri":"capability://tool.use.integration.npm.based.mcp.server.installation.from.remote.repositories","name":"npm-based mcp server installation from remote repositories","description":"Installs MCP servers published to npm registries by invoking npx with the package name, automatically resolving dependencies and downloading binaries. The system parses the package name, constructs an npx command with optional arguments and environment variables, executes it in a subprocess, and streams output back to Claude. This approach leverages npm's existing package resolution and caching mechanisms rather than implementing custom dependency management.","intents":["Install an MCP server from npm without manually editing Claude Desktop config files","Install a scoped npm package like @modelcontextprotocol/server-filesystem with custom arguments","Install an MCP server and pass environment variables (API keys, tokens) at installation time"],"best_for":["Claude Desktop users wanting to extend capabilities via natural language","Teams automating MCP server provisioning across multiple machines","Developers building MCP server packages for npm distribution"],"limitations":["Requires npm or Node.js to be installed and in PATH; fails silently if npx is unavailable","No built-in version pinning — always installs latest unless user specifies @version in package name","Cannot validate that installed package is actually a valid MCP server before registration","Subprocess execution adds ~500ms-2s latency depending on package size and network"],"requires":["Node.js 14+ with npm installed and accessible in system PATH","Claude Desktop application with MCP server support","Write permissions to Claude Desktop configuration directory (~/.config/Claude/claude_desktop_config.json on Linux/Mac, %APPDATA%\\Claude on Windows)"],"input_types":["text (package name, e.g., 'mcp-server-fetch' or '@modelcontextprotocol/server-filesystem')","text (optional arguments array, e.g., ['--port', '3000'])","text (optional environment variables object, e.g., {'API_KEY': 'xyz'})"],"output_types":["text (installation status messages and subprocess output)","structured data (updated Claude Desktop configuration JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_1","uri":"capability://tool.use.integration.pypi.based.mcp.server.installation.from.remote.repositories","name":"pypi-based mcp server installation from remote repositories","description":"Installs MCP servers published to PyPI by invoking the `uv` package manager (a fast Rust-based Python package installer) with the package name, handling Python dependency resolution and virtual environment setup. The system constructs a uv command with optional arguments and environment variables, executes it as a subprocess, and registers the installed server in Claude Desktop's configuration. This approach uses uv instead of pip for faster, more reliable dependency resolution.","intents":["Install a Python-based MCP server from PyPI without manual configuration","Install a PyPI package with custom command-line arguments passed to the server","Install a Python MCP server and inject environment variables (API credentials) at installation time"],"best_for":["Claude Desktop users wanting Python-based MCP servers (e.g., data processing, ML tools)","Teams with Python-heavy infrastructure preferring PyPI packages over npm","Developers building MCP servers in Python for distribution via PyPI"],"limitations":["Requires `uv` package manager to be installed; falls back to pip if uv unavailable (slower)","No version pinning by default — installs latest PyPI version unless user specifies ==version","Python virtual environment isolation not explicitly managed — relies on uv's default behavior","Cannot validate installed package exports valid MCP server interface before registration","Subprocess execution adds ~1-3s latency for Python package installation and dependency resolution"],"requires":["Python 3.8+ installed and in system PATH","uv package manager installed (https://github.com/astral-sh/uv) or pip as fallback","Claude Desktop application with MCP server support","Write permissions to Claude Desktop configuration directory"],"input_types":["text (PyPI package name, e.g., 'mcp-server-postgres' or 'anthropic-mcp')","text (optional arguments array)","text (optional environment variables object)"],"output_types":["text (installation status and uv/pip output)","structured data (updated Claude Desktop configuration JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_2","uri":"capability://tool.use.integration.local.filesystem.based.mcp.server.installation","name":"local filesystem-based mcp server installation","description":"Installs MCP servers from local directories on the user's machine by reading the server's package.json or pyproject.toml, validating the directory structure, and registering it in Claude Desktop's configuration without downloading or copying files. The system locates the configuration file based on OS, parses the existing MCP server list, appends the new local server entry with its command and arguments, and writes the updated config back. This approach enables development workflows where users test MCP servers before publishing to registries.","intents":["Install a locally-developed MCP server from a directory path for testing in Claude Desktop","Register a custom MCP server built in-house without publishing to npm or PyPI","Point Claude Desktop to a local MCP server directory with custom startup arguments"],"best_for":["MCP server developers testing their implementations locally before publishing","Enterprise teams running custom MCP servers from internal repositories","Users wanting to fork and modify existing MCP servers for local use"],"limitations":["No automatic dependency installation — assumes local directory already has dependencies installed (npm install or pip install must be run separately)","No validation that the directory contains a valid MCP server implementation — registration succeeds even if server is broken","Absolute file paths in configuration are not portable across machines or user accounts","No automatic updates — if local server code changes, Claude Desktop must be restarted to pick up changes","Requires write permissions to both the local server directory and Claude Desktop config"],"requires":["Local directory containing MCP server code with package.json (Node.js) or pyproject.toml (Python)","Dependencies already installed in local directory (npm install or pip install completed)","Claude Desktop application with MCP server support","Write permissions to Claude Desktop configuration directory and the local server directory"],"input_types":["text (absolute or relative file path to local MCP server directory, e.g., '/home/user/my-mcp-server' or './local-servers/my-server')","text (optional arguments array to pass to server startup)","text (optional environment variables object)"],"output_types":["text (installation status and validation messages)","structured data (updated Claude Desktop configuration JSON with local server entry)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_3","uri":"capability://automation.workflow.claude.desktop.configuration.file.management.with.os.aware.path.resolution","name":"claude desktop configuration file management with os-aware path resolution","description":"Automatically locates and updates Claude Desktop's configuration file across Windows, macOS, and Linux by detecting the operating system and constructing the correct path to the MCP server configuration JSON. The system reads the existing configuration, parses the MCP server list, appends or updates the new server entry with its command, arguments, and environment variables, and writes the updated JSON back with proper formatting. This abstraction eliminates manual config file editing and handles OS-specific path differences transparently.","intents":["Automatically register an installed MCP server in Claude Desktop without manually editing config files","Update Claude Desktop configuration across different operating systems (Windows, macOS, Linux) with a single code path","Ensure MCP server configuration persists across Claude Desktop restarts and updates"],"best_for":["MCP server installers and provisioning tools that need to register servers in Claude Desktop","Teams automating MCP server deployment across heterogeneous OS environments","Claude Desktop users who want to avoid manual JSON editing and potential syntax errors"],"limitations":["Requires Claude Desktop to be installed in standard location; custom installations may not be detected","No backup of original configuration — if write fails partway through, config may be corrupted (no atomic writes)","No conflict detection — if two MCP servers have the same name, the second silently overwrites the first","Configuration changes require Claude Desktop restart to take effect; no hot-reload","No validation that MCP server command is actually executable before registration"],"requires":["Claude Desktop application installed in standard location (~/Library/Application Support/Claude on macOS, %APPDATA%\\Claude on Windows, ~/.config/Claude on Linux)","Write permissions to Claude Desktop configuration directory","Valid JSON syntax in existing claude_desktop_config.json (tool will fail if config is malformed)"],"input_types":["structured data (MCP server configuration object with name, command, args, env)","text (operating system identifier for path resolution)"],"output_types":["structured data (updated claude_desktop_config.json with new MCP server entry)","text (status messages indicating success or failure)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_4","uri":"capability://tool.use.integration.mcp.server.installation.with.custom.arguments.and.environment.variable.injection","name":"mcp server installation with custom arguments and environment variable injection","description":"Passes custom command-line arguments and environment variables to MCP servers during installation, enabling servers to be configured with startup parameters (ports, data directories) and credentials (API keys, tokens) without requiring post-installation manual configuration. The system accepts optional arguments array and environment variables object, constructs the appropriate command (npx, uv, or local) with these parameters, executes the server startup, and registers the configured server in Claude Desktop. This approach enables parameterized server installation workflows.","intents":["Install an MCP server and configure it with custom arguments (e.g., --port 3000, --data-dir /path/to/data) in a single step","Inject environment variables (API keys, database credentials) into an MCP server at installation time","Install multiple instances of the same MCP server with different configurations and arguments"],"best_for":["Teams deploying MCP servers with environment-specific configuration (dev, staging, prod)","Users installing MCP servers that require API credentials or custom startup parameters","Automation scripts provisioning MCP servers with parameterized configurations"],"limitations":["Arguments and environment variables are stored in plaintext in Claude Desktop config file — sensitive credentials are not encrypted","No validation that provided arguments are valid for the target MCP server — invalid args fail silently at runtime","Environment variables are not scoped — they apply globally to the MCP server process, not per-request","No support for secrets management or credential rotation — credentials must be manually updated in config","Arguments and env vars are not escaped — special characters or spaces may cause command parsing errors"],"requires":["Knowledge of target MCP server's supported command-line arguments and environment variables","For environment variables: understanding of how the target server reads and uses env vars","Write permissions to Claude Desktop configuration directory"],"input_types":["text (optional arguments array, e.g., ['--port', '3000', '--data-dir', '/data'])","text (optional environment variables object, e.g., {'API_KEY': 'xyz', 'DB_URL': 'postgres://...'})"],"output_types":["structured data (updated Claude Desktop configuration with arguments and env vars registered)","text (status messages confirming argument/env var registration)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_5","uri":"capability://planning.reasoning.mcp.server.installation.request.parsing.and.validation","name":"mcp server installation request parsing and validation","description":"Parses natural language requests from Claude to extract MCP server name, installation source (npm, PyPI, or local path), optional arguments, and environment variables, then validates that the request contains sufficient information to proceed with installation. The system uses Claude's tool schema to define expected input parameters (server name, source type, args, env), validates that required fields are present, and routes the request to the appropriate installation handler (npm, PyPI, or local). This abstraction enables Claude to understand and execute installation requests in natural language.","intents":["Allow Claude to understand user requests like 'Install the mcp-server-fetch package' and extract the package name","Parse requests with optional arguments like 'Install mcp-server-postgres with args [--port, 5432]'","Validate that installation requests contain enough information before attempting installation"],"best_for":["Claude Desktop users issuing natural language installation requests","MCP server installation workflows where Claude acts as the interface","Automation systems that need to parse and validate installation requests before execution"],"limitations":["Relies on Claude's ability to extract structured data from natural language — ambiguous requests may be misinterpreted","No fuzzy matching for package names — typos in package names are not corrected or suggested","Cannot distinguish between npm and PyPI packages with the same name without explicit user indication","No validation that extracted package name actually exists in npm or PyPI registries","Error messages for invalid requests may be unclear to non-technical users"],"requires":["Claude Desktop with MCP server support","MCP Installer tool registered in Claude Desktop configuration","User providing clear indication of installation source (npm, PyPI, or local path)"],"input_types":["text (natural language request from Claude, e.g., 'Install mcp-server-fetch')","text (optional arguments and environment variables embedded in request)"],"output_types":["structured data (parsed installation request with server name, source, args, env)","text (validation error messages if request is incomplete or invalid)"],"categories":["planning-reasoning","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-mcp-installer__cap_6","uri":"capability://automation.workflow.subprocess.execution.with.output.streaming.and.error.handling","name":"subprocess execution with output streaming and error handling","description":"Executes package manager commands (npx, uv) and local server startup as subprocesses, streams their output back to Claude in real-time, and captures exit codes and error messages for error reporting. The system spawns a child process with the constructed command, pipes stdout/stderr to the MCP response stream, monitors the process for completion, and returns the exit code and final status. This approach enables users to see installation progress and diagnose failures without waiting for the entire operation to complete.","intents":["Show users real-time installation progress (downloading packages, resolving dependencies) as it happens","Capture and report installation errors (network failures, missing dependencies) with detailed error messages","Enable users to interrupt long-running installations if needed"],"best_for":["Interactive installation workflows where users want to see progress in real-time","Debugging MCP server installation failures by examining subprocess output","Long-running installations where users need feedback that the process is still running"],"limitations":["Subprocess output is not captured if the process is backgrounded — only interactive execution is supported","No timeout mechanism — if subprocess hangs, the installation will hang indefinitely","Output streaming adds latency compared to buffering entire output and returning at end","Error messages from subprocess are raw and may not be user-friendly (e.g., npm error codes)","No support for interactive subprocess input — cannot respond to prompts during installation"],"requires":["Node.js or Python subprocess execution capability (available in most environments)","Network connectivity for downloading packages from npm or PyPI","Sufficient disk space for package downloads and installation"],"input_types":["text (command to execute, e.g., 'npx mcp-server-fetch')","text (optional arguments and environment variables)"],"output_types":["text (streamed subprocess output including stdout and stderr)","structured data (exit code and final status)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ with npm installed and accessible in system PATH","Claude Desktop application with MCP server support","Write permissions to Claude Desktop configuration directory (~/.config/Claude/claude_desktop_config.json on Linux/Mac, %APPDATA%\\Claude on Windows)","Python 3.8+ installed and in system PATH","uv package manager installed (https://github.com/astral-sh/uv) or pip as fallback","Write permissions to Claude Desktop configuration directory","Local directory containing MCP server code with package.json (Node.js) or pyproject.toml (Python)","Dependencies already installed in local directory (npm install or pip install completed)","Write permissions to Claude Desktop configuration directory and the local server directory","Claude Desktop application installed in standard location (~/Library/Application Support/Claude on macOS, %APPDATA%\\Claude on Windows, ~/.config/Claude on Linux)"],"failure_modes":["Requires npm or Node.js to be installed and in PATH; fails silently if npx is unavailable","No built-in version pinning — always installs latest unless user specifies @version in package name","Cannot validate that installed package is actually a valid MCP server before registration","Subprocess execution adds ~500ms-2s latency depending on package size and network","Requires `uv` package manager to be installed; falls back to pip if uv unavailable (slower)","No version pinning by default — installs latest PyPI version unless user specifies ==version","Python virtual environment isolation not explicitly managed — relies on uv's default behavior","Cannot validate installed package exports valid MCP server interface before registration","Subprocess execution adds ~1-3s latency for Python package installation and dependency resolution","No automatic dependency installation — assumes local directory already has dependencies installed (npm install or pip install must be run separately)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.39999999999999997,"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-06-17T09:51:03.578Z","last_scraped_at":"2026-05-03T14:00:15.503Z","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=mcp-installer","compare_url":"https://unfragile.ai/compare?artifact=mcp-installer"}},"signature":"yyoa65H03KWRHjU4kCE2kp+IspU9gMzgVRYBvo/LuDVxDnOkLfYgf/Qu0QP0xw4ZqUp2B4KkMs5ozw5JR0upAw==","signedAt":"2026-06-22T05:19:06.046Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/mcp-installer","artifact":"https://unfragile.ai/mcp-installer","verify":"https://unfragile.ai/api/v1/verify?slug=mcp-installer","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"}}