Daniel Rosehill's MCP Installer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CACHE_DIR | No | Cache directory | ~/.cache/mcp-installer |
| MCP_CACHE_TTL | No | Cache TTL in seconds | 3600 |
| MCP_REGISTRY_URL | No | Override registry URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mcpsB | List all available MCPs in the registry. Can filter by category or show only essential MCPs. |
| list_installedB | Show what MCPs are already installed in a specific client or all clients. |
| install_mcpB | Install a single MCP to a client. If secrets are required, they must be provided. |
| install_allA | Install all MCPs (or just essential ones) to a client. Skips MCPs that need secrets unless provided. |
| sync_registryA | Update the local registry cache from GitHub. Use this to get the latest MCP list. |
| uninstall_mcpC | Remove an MCP from a client configuration. |
| get_infoB | Get information about the installer, registry URL, cache location, and supported clients. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: get_info provides metadata, install_all and install_mcp handle bulk vs. single installations, list_installed and list_mcps show different data sources, sync_registry updates the cache, and uninstall_mcp removes MCPs. The descriptions make it easy to differentiate between similar-sounding tools like list_installed (client-side) and list_mcps (registry).
All tool names follow a consistent verb_noun pattern using snake_case, such as get_info, install_all, list_installed, and sync_registry. There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.
With 7 tools, the server is well-scoped for an MCP installer, covering core operations like installation, listing, syncing, and uninstallation without being too sparse or bloated. Each tool serves a clear, necessary function in the workflow, and the count aligns with typical server sizes of 3-15 tools.
The tool set provides complete coverage for the MCP installer domain, including metadata retrieval (get_info), installation (install_all, install_mcp), inventory management (list_installed, list_mcps), updates (sync_registry), and removal (uninstall_mcp). There are no obvious gaps, as all essential CRUD-like operations for managing MCP installations are present.