mcp-installer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| install_repo_mcp_serverC | Install an MCP server via npx or uvx |
| install_local_mcp_serverC | Install an MCP server whose code is cloned locally on your computer |
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 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.