envmgr-mcp-server
Related Servers
Alternatives to envmgr-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceManages multiple SSH servers through a local workspace with MCP tools, executing commands and transferring files securely with credential isolation.91MIT
- AlicenseAqualityBmaintenanceEnables AI clients to securely execute remote commands and transfer files over SSH through standardized MCP tools, with multi-host management, flexible authentication, and an admin console.519 npm3ISC
- GPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to store encrypted SSH host credentials and execute remote commands over pooled SSH connections, including single commands, prompt-answering interactive runs, and multi-step playbooks. Hosts can be listed, created, updated, and deleted through tools, with credentials kept server-side and never echoed back.8664 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP clients to securely execute shell commands, manage files, and access remote devices or SSH hosts through centralized authentication, routing, and auditing.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list hosts, run commands, and orchestrate fleet automation over SSH, with per-host opt-in and approval-gated actions while keeping credentials secure.4MIT
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.