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.-
- AlicenseBqualityDmaintenanceA meta-server that allows Claude to install other MCP servers from npm or PyPi, enabling easy expansion of Claude's capabilities with external tools.2142 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching and filtering a directory of over 34,000 MCP servers by keyword, category, language, and hosting type, then generates ready-to-paste configuration for Claude Desktop, Cursor, Windsurf, Zed, and Claude Code. Also lets an AI assistant discover and recommend servers conversationally and produce their install configs.MIT
- 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-
- AlicenseAqualityDmaintenanceAn MCP server for discovering Claude Code skills, plugins, and MCP servers by searching 15,000+ resources from 17 registries, GitHub, and the web with zero setup.322 npm3MIT
- AlicenseNot gradedqualityDmaintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.11MIT
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. It covers basic installation methods but lacks tools for managing installed servers (e.g., list, update, remove), which limits its utility.
The toolset is severely incomplete for an installer. It provides installation but no lifecycle management (e.g., uninstall, list, update, configure). This will cause agent failures when trying to manage servers beyond initial installation.