pyenv-manager-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_versionsA | List all Python versions installed locally via pyenv. |
| get_current_versionA | Get the currently active Python version (pyenv version). |
| list_available_downloadsA | List all Python versions available for installation via pyenv. |
| install_versionB | Install a specific Python version using pyenv. |
| set_global_versionA | Set the global Python version for pyenv. |
| set_local_versionA | Set the local directory Python version (.python-version). |
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 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.