Summary
Adding a server stops being a config file you edit by hand.
What it takes off you is the hand-editing and the restart-to-find-out cycle: you name the server, the arguments and the environment it needs, and it goes in. The local variant does the same for a server you have cloned and never released, which is the awkward half of writing one.
What it is
A two-call server whose only job is installing other MCP servers. One installs a published server through npx or uvx; the other registers one whose code already sits on your machine.
What you get
- A published MCP server installed by name, with the arguments and environment variables it needs
- A locally cloned MCP server installed from its path, taking the same arguments and environment
Requirements
Npx to run it, and npx or uvx available for whatever it goes on to install.
Setup effort
One command — npx -y @anaisbetts/mcp-installer