mcp-installer
An MCP server that installs other MCP servers from npm and PyPI at the agent's request and writes them into the config
- 1,538 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Installs and runs third-party packages from npm and PyPI
- Edits the client config and launches arbitrary MCP servers
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-installerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Installs and runs third-party packages from npm and PyPI
- Edits the client config and launches arbitrary MCP servers
This is third-party code. Review the repository files before installing.
What it does
The installer runs as an MCP server: you connect it to a client and then ask the agent to install the server you want. It installs servers from npm and PyPI, accepts launch arguments and environment variables, and writes them into the client config. It can also wire up local servers by a path on disk. Node servers need npx, Python servers need uv.
Who it is for. For people who add MCP servers often and would rather not edit the config by hand.
Good fit when
- You want to quickly add an MCP server from npm or PyPI
- You need to install a local MCP server by its path on disk
- You want the agent to write the server into the config itself
Not a fit when
- You only need one specific server that is easier to add by hand
- The machine has neither npx nor uv
Example request
Install the server-filesystem MCP server and pass it the path to my working folderMCP
- Transport
- stdio
- Authentication
- not required
Limitations
The repository has not been updated in a long time and newer clients may use a different config schema, so some flows can fail without adjustments. It needs npx and uv. The installer runs third-party packages, so install only trusted sources.
How to disable. Remove the mcp-installer block from your client's MCP config and restart the client.
FAQ
What is needed besides the installer itself?
npx for Node servers and uv for Python ones.
Where does it install servers from?
From npm and PyPI, and locally by a given path on disk.
Discussion
No questions or reviews yet.
Related
MCP serversA universal MCP CLI client from Apify: persistent sessions, OAuth, JSON output for scripts and shell access to any MCP server for agents
An MCP builder agent that picks servers from the official registry and composes them into your own agentic MCP server.
The mcpl CLI searches tools across several MCP servers and calls them from the terminal, with OAuth sign-in done by a human
An adapter that connects an MCP client limited to local stdio servers to a remote MCP server over HTTP or SSE, with authorization
One MCP gateway instead of dozens of servers: the agent finds a tool on demand and keeps no schemas in context
A Python framework and CLI for MCP: write servers as plain functions, test tools and install servers into Claude Code, Cursor and other clients
README in short
The README explains this is an MCP server that installs other MCP servers. You add it to the client config via the npx command with the @anaisbetts/mcp-installer package, then ask the agent to install a server from npm or PyPI. The examples show how to pass arguments and environment variables and how to add a server by a local path. Node servers require npx, Python servers require uv.