MCP Installer: Let Claude Install Its Own Tools

Stop editing JSON configs every time you want to try a new MCP server. This meta-installer lets you ask Claude directly to install other MCP servers through natural language - no more manual configuration, no more hunting down exact package names or argument formats.

Skip the Configuration Dance

You know the drill: find an interesting MCP server, figure out the exact package name, dig through docs for the right arguments, manually edit your claude_desktop_config.json, restart Claude, hope you didn't break the JSON syntax. It's tedious busywork that breaks your flow.

MCP Installer turns this into a conversation. Install it once, then ask Claude to handle the rest:

"Hey Claude, install the MCP server named mcp-server-fetch"

"Install @modelcontextprotocol/server-filesystem and use ['/Users/me/projects'] for the arguments"

"Install the server @modelcontextprotocol/server-github and set GITHUB_PERSONAL_ACCESS_TOKEN to my token"

Claude handles the installation, configuration, and environment setup. You stay focused on building.

Beyond Package Managers

This isn't just another package installer. It supports multiple installation sources:

• npm packages: Standard MCP servers published to npm
• PyPI packages: Python-based MCP servers via uv
• Local repositories: Your own MCP servers under development
• GitHub repos: Install directly from any public repository

Each source gets the same conversational treatment. Whether you're installing a published server or testing your own development build, Claude handles the complexity.

Real Workflow Acceleration

Rapid prototyping: "Install the filesystem server for this project directory, then add the GitHub server with my token." Two sentences replace 10 minutes of JSON editing.

Team onboarding: New team members ask Claude to install your stack of internal MCP servers instead of following a 20-step setup guide.

Environment-specific setups: Different projects need different MCP servers. Ask Claude to install project-specific tooling without polluting your global config.

Development iteration: Testing a new MCP server you're building? Ask Claude to install it from your local repo, iterate, then ask Claude to reinstall the updated version.

Installation & Usage

Add this to your claude_desktop_config.json:

"mcpServers": {
  "mcp-installer": {
    "command": "npx",
    "args": ["@anaisbetts/mcp-installer"]
  }
}

Then restart Claude and start asking for installations. The installer requires npx for Node.js servers and uv for Python servers.

Why This Matters

MCP servers are powerful, but configuration friction kills experimentation. This installer removes that friction entirely. Instead of context-switching to edit configs, you maintain flow by asking Claude to install what you need.

The result is faster exploration of the MCP ecosystem, easier team collaboration, and more time building instead of configuring. It's the difference between "I should try that MCP server sometime" and "Claude, install that server now."