venv-mcp-server
by sparfenyuk
README.md
# venv-mcp-server
- [venv-mcp-server](#venv-mcp-server)
- [Integrations](#integrations)
- [Cline / Claude Desktop](#cline--claude-desktop)
- [Command-line arguments](#command-line-arguments)
The MCP server which solves the following problem: LLMs are not able to resolve dependencies and update the virtual environment on their own **reliably**. With simple list of tools, `venv-mcp-server` makes it possible.
## Integrations
### Cline / Claude Desktop
```json
{
"mcpServers": {
"venv-management-for-my-project": {
"command": "uvx",
"args": [
"--from=git+https://github.com/sparfenyuk/venv-mcp-server.git",
"venv-mcp-server"
]
}
}
}
```
## Command-line arguments
```terminal
$ uvx --from git+https://github.com/sparfenyuk/venv-mcp-server.git venv-mcp-server --help
usage: venv-mcp-server [-h] [--uv-path UV_PATH]
A MCP server to manage a virtual environment in the given location using 'uv'
options:
-h, --help show this help message and exit
--uv-path UV_PATH Path to uv executable. Default is the 'uv' command in your PATH.
```
TDQS
B3.2/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: init, add/remove packages (singular/plural), sync, and run commands. No overlap or ambiguity.
Naming Consistency4/5
All tools use snake_case and follow a verb_noun pattern (add_package, remove_package, run_in_venv), but 'init' and 'sync' are single words, which is a minor deviation.
Tool Count5/5
6 tools cover the essential operations for virtual environment management (init, add, remove, sync, run). No excess or deficiency.
Completeness4/5
Covers core workflows: init, add/remove packages, sync, run commands. Missing operations like listing installed packages or updating packages, but not critical.
Maintenance
ActivityInactive
ResponsivenessUnresponsive