MCP Environment & Installation Manager
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
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 24 tools
Most tools have distinct purposes targeting specific resources like profiles, env vars, installations, or MCP packages. However, some tools like 'configure-installation' and 'get-installation-settings' could potentially overlap in scope, and 'enable-auto-localize' vs 'localize-mcp-server' might cause confusion without descriptions. Overall, the set is mostly clear with minor ambiguity.
All tool names follow a consistent verb_noun pattern with hyphen-separated words (e.g., 'activate-profile', 'configure-installation', 'get-env-var'). There are no deviations in naming style, making the set highly predictable and readable.
With 24 tools, the count is borderline high for an environment manager, potentially feeling heavy. While it covers multiple aspects (profiles, env vars, installations, MCPs), it might be slightly over-scoped, risking complexity for agents.
The tool set provides comprehensive coverage for managing MCP environments, including CRUD operations for profiles, env vars, and MCP installations. Minor gaps might exist, such as missing tools for advanced configuration or error handling, but core workflows are well-covered.