envmgr-mcp-server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| envmgr_listA | 列出所有已配置的环境及其连接信息。 配置文件路径:/root/.config/envmgr/envs.json(可通过 ENVMGR_CONFIG 环境变量覆盖)。 返回每个环境的:名称、类型、描述、SSH 状态、浏览器状态。密码不返回。 |
| envmgr_sshA | 通过 SSH 在指定环境上执行 shell 命令,返回命令输出。 使用场景:
注意:命令在 root 权限下执行,请谨慎使用破坏性命令。 |
| envmgr_browserA | 返回指定环境的浏览器访问 URL 和认证凭据。 输出的结构化信息可供 Playwright、chrome-devtools-mcp 等浏览器自动化工具使用。 使用流程:
|
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 3 tools
Each tool serves a distinct purpose: envmgr_list enumerates environments, envmgr_ssh executes commands, and envmgr_browser provides browser access credentials. The descriptions clearly separate these functions with no overlapping scope.
All tools share the envmgr_ prefix, making the namespace clear. The second part mixes a verb (list) with nouns (ssh, browser), which is a minor inconsistency, but the pattern remains predictable and readable.
With only three tools, the server is tightly scoped to its purpose of providing environmental access. Each tool is necessary and the count is not excessive or inadequate for the domain.
The server covers the primary lifecycle of listing environments and accessing them via SSH or browser. Minor gaps such as environment add/remove or update exist, but these are likely managed externally via config files, so the surface is sufficient for its intended use.