MCP Installer
# mcp-installer - A MCP Server to install MCP Servers
This server is a server that installs other MCP servers for you. Install it, and you can ask Claude to install MCP servers hosted in npm or PyPi for you. Requires `npx` and `uv` to be installed for node and Python servers respectively.
### How to install:
Put this into your `claude_desktop_config.json` (either at `~/Library/Application Support/Claude` on macOS or `C:\Users\NAME\AppData\Roaming\Claude` on Windows):
```json
"mcpServers": {
"mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
```
### Example prompts
> Hey Claude, install the MCP server named mcp-server-fetch
> Hey Claude, install the @modelcontextprotocol/server-filesystem package as an MCP server. Use ['/Users/anibetts/Desktop'] for the arguments
> Hi Claude, please install the MCP server at /Users/anibetts/code/mcp-youtube, I'm too lazy to do it myself.
> Install the server @modelcontextprotocol/server-github. Set the environment variable GITHUB_PERSONAL_ACCESS_TOKEN to '1234567890'
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one installs from local code, the other installs via package managers (npx/uvx). There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'install' as the verb and descriptive suffixes ('local_mcp_server', 'repo_mcp_server'). The naming is perfectly uniform and predictable.
With only 2 tools, the server feels thin for an 'Installer' domain. While it covers two installation methods, it lacks tools for managing installations (e.g., list, update, remove), making the surface incomplete for typical installer workflows.
The toolset is severely incomplete for an installer. It provides installation methods but lacks essential operations like listing installed servers, updating them, uninstalling, or checking status. This will cause agent failures for common management tasks.