My MCP Installer

You deploy and manage MCPs across machines with a centralized MCP Server. It fetches a registry, installs MCPs on your preferred clients, and prompts you for secrets when API keys are required, making it easy to set up and keep multiple MCPs synchronized across your workflow.

How to use

Configure your MCP server in your MCP client settings to connect to the central registry and start installing MCPs on your devices.

In Claude Code, add your MCP server configuration to your settings so the client can discover and install MCPs. You will reference the MCP registry and specify how to run MCPs from the client.

Typical usage patterns include listing available MCPs, installing all essential MCPs, or installing a specific MCP by its identifier. When a MCP requires an API key, you will be prompted to provide the secret value.

How to install

Prerequisites: you need Node.js and npm installed, and access to Claude Code or a compatible MCP client capable of loading MCP configurations.

1. Create or update your Claude Code configuration to register the MCP server.

2. Use the MCP client commands to explore and install MCPs. For example, you can list available MCPs, install all essential MCPs, or install a specific MCP by its identifier.

3. When installing an MCP that requires a secret, provide the required keys (for example, a Google API key) when prompted by the client.

Configuration

{
  "mcpServers": {
    "my_mcps": {
      "command": "npx",
      "args": ["-y", "daniel-rosehill-mcps"]
    }
  }
}

Environment and registry information

Environment variables help customize how the MCP server fetches and caches its registry. You can override the registry URL and set cache preferences.

# Example environment variable settings
MCP_REGISTRY_URL=https://raw.githubusercontent.com/danielrosehill/mcp-registry/main/registry.json
MCP_CACHE_DIR=~/.cache/mcp-installer
MCP_CACHE_TTL=3600

Notes and tips

The MCP server is designed to fetch your MCP registry from a remote source, install MCPs on named clients, and prompt for required secrets when necessary. It supports multiple clients and can refresh its registry to stay up to date.

Keep your API keys and secrets secure. Use environment-protected storage or secure prompts when the MCPs request credentials.

Troubleshooting

If an MCP fails to install, verify that the MCP identifier is correct and that the client is configured to connect to the MCP server. Check that the required environment variables are set and that the registry URL is reachable.

Security considerations

Only install MCPs from trusted registries and ensure secrets are provided through secure prompts or safe storage mechanisms. Limit access to the MCP server configuration to authorized users.

Examples

Install all essential MCPs to a client in one step using the MCP client: list all MCPs, then run install_all essential_only=true, and finally install a specific MCP by its ID if needed.

Available tools

list_mcps

List all MCPs in the registry with optional filters for category or essential status.

list_installed

Show MCPs currently installed for a targeted client.

install_mcp

Install a single MCP to a selected client.

install_all

Install all MCPs or only essential MCPs to a client.

sync_registry

Refresh the local registry by pulling updates from the registry source.

uninstall_mcp

Remove an MCP from a client.

get_info

Show installer information and supported clients.