Daniel Rosehill's MCP Installer
Related Servers
Alternatives to Daniel Rosehill's MCP Installer
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that provides easy setup and configuration for multiple AI development environments including Claude Desktop, VS Code, and Windsurf. Offers automated installation scripts and manual configuration options for seamless integration across different MCP-compatible clients.18-
- FlicenseNot gradedqualityDmaintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.11-
- AlicenseNot gradedqualityAmaintenanceEnables centralized management of MCP servers across multiple AI coding harnesses, including adding, removing, monitoring, configuring, and syncing servers with encrypted token storage.MIT
- AlicenseNot gradedqualityDmaintenanceMCP of MCPs. Automatic discovery and configure MCP servers on your local machine. Integration with Claude and Cursor.52Apache 2.0
- FlicenseAqualityCmaintenanceA robust MCP server with tools to search, install, configure, repair, and uninstall MCP servers, automating setup and maintenance across multiple AI and developer tools.417-
- -licenseNot gradedqualityNot gradedmaintenanceA meta-MCP server that helps users install and configure other MCP servers directly through Claude prompts, supporting both npm and PyPi packages.-
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.