install_local_mcp_server
Install an MCP server whose code is cloned locally on your computer
Ask the assistant to install another MCP server for you — a published one by name, or one you have checked out on disk.
LABSCO SUMMARY
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.
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.
npx to run it, and npx or uvx available for whatever it goes on to install.
One command — npx -y @anaisbetts/mcp-installer
USE CASES
Name the published package and it is installed through npx or uvx, without opening the client's configuration file.
A server that only exists as a clone on disk has nothing to install by name. Point at the path instead and it registers the same way.
Both calls take environment variables alongside the arguments, so a server that needs a token is configured as it goes in rather than after it fails to start.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
install_local_mcp_serverInstall an MCP server whose code is cloned locally on your computer
install_repo_mcp_serverInstall an MCP server via npx or uvx
BEFORE YOU INSTALL
2 tools when we connected.
npx on PATH
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @anaisbetts/mcp-installer{
"mcpServers": {
"mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
}