dev-env-mcp
Related Servers
Alternatives to dev-env-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityFmaintenanceAn MCP server that manages Python virtual environments using uv, allowing LLMs to reliably resolve dependencies and update virtual environments.67-
- AlicenseAqualityBmaintenanceAn MCP server that manages an IPython kernel, allowing LLMs to execute Python code in a project's virtual environment.82MIT
- AlicenseAqualityCmaintenanceA safety-first local MCP server that enables bounded file reading, text search, line-range editing with optimistic locking, and read-only git diff operations within a single code workspace.6MIT
- AlicenseBqualityBmaintenanceMCP server enabling AI assistants to inspect and manage Python environments via uv, including package management, virtual environments, Python versions, tools, and security auditing.50Apache 2.0
- FlicenseBqualityCmaintenanceProvides a minimal MCP server with safe tools for AI assistants to search project files, read files, search local documentation, and run pre-approved checks within a single project directory.4-
- FlicenseNot gradedqualityBmaintenanceA sandboxed MCP server for agents that provides file read/edit, code intelligence, search, allowlisted command execution, package lookups, persistent memory, and VPS channel clients, all confined to C:\Work.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: env_create creates a new venv, env_use selects an existing one, freeze writes requirements, pip runs pip commands, and workspace_use selects the workspace. No overlap or ambiguity.
Naming is inconsistent: env_create, env_use, and workspace_use follow a verb_noun pattern with a prefix, but freeze and pip are standalone verbs/nouns without a prefix. Mixing conventions reduces predictability.
With 5 tools, the server covers the essential operations for managing a Python virtual environment in a workspace. The count is well within the ideal range (3-15) and each tool serves a necessary function.
The tool set covers the core workflow of creating/using venvs, running pip, and freezing dependencies. Minor gaps exist: no tool to list existing venvs or delete them, but agents can work around these limitations.