pyenv-manager-mcp
Related Servers
Alternatives to pyenv-manager-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to manage Python environments and dependencies via uv, supporting package inspection, installation, and requirement management.4MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with Python environments, execute code, manage packages, and perform file operations within a configurable working directory.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to work with local Python environments by listing environments and installed packages, installing dependencies, and running code or scripts. Also supports reading, writing, and listing files within a sandboxed working directory.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with Python environments, run code and scripts, manage packages, and read or write files within a configured working directory.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to run Python code and scripts, manage Python environments and packages, and read or write files within an isolated working directory. It also provides prompts for common Python tasks such as function creation, refactoring, and debugging.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with Python environments, execute code or scripts, manage packages, and read/write files within an isolated working directory.-
TDQS
Scored across 6 tools
Each tool maps to a distinct pyenv operation: listing installed versions, showing the active version, listing downloadable versions, installing, and setting global/local versions. There is minimal overlap, and the descriptions clearly separate installed from available versions.
Tool names consistently follow a predictable verb_noun pattern: list_*, get_*, install_*, set_*. Even though list_available_downloads uses 'downloads' instead of 'versions', the naming style remains uniform and easy to navigate.
Six tools is a well-scoped set for a pyenv manager. Each tool covers a necessary core operation without unnecessary bloat or redundant additions.
The tool surface covers listing, installing, and setting versions, but notably lacks uninstall/remove functionality, which is a standard pyenv lifecycle operation. Agents can work around it, but version cleanup is a meaningful gap.