MCP Installer
Related Servers
Alternatives to MCP Installer
No user-submitted related servers found.
Related Servers
- -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.-
- AlicenseBqualityDmaintenanceThis server is a server that installs other MCP servers for you. Install it, and you can ask Claude to install MCP servers hosted in npm or PyPi for you. Requires npx and uv to be installed for node and Python servers respectively.2137 npm1,535MIT
- AlicenseAqualityDmaintenanceA meta-MCP server that dynamically manages and invokes any MCP server on the fly, enabling runtime addition, removal, and tool invocation without restarting Claude Code.53 npmMIT
- AlicenseBqualityDmaintenanceMCP server that builds itself by creating new tools as needed based on user requests (Requires restart of Claude Desktop to use newly created tools).425-
- AlicenseBqualityAmaintenanceA meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.1666 PyPI143AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceAn MCP server that helps Claude design, scaffold, and validate MCP servers compatible with the mcp-deploy platform, enabling seamless creation and deployment of new MCP workers.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one installs from local code, the other installs via package managers (npx/uvx). There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'install' as the verb and descriptive suffixes ('local_mcp_server', 'repo_mcp_server'). The naming is perfectly uniform and predictable.
With only 2 tools, the server feels thin for an 'Installer' domain. While it covers two installation methods, it lacks tools for managing installations (e.g., list, update, remove), making the surface incomplete for typical installer workflows.
The toolset is severely incomplete for an installer. It provides installation methods but lacks essential operations like listing installed servers, updating them, uninstalling, or checking status. This will cause agent failures for common management tasks.