MCP Server UV
A Model Context Protocol (MCP) server implementation for the UV package manager. This server provides MCP-compatible interfaces for managing Python packages and virtual environments using UV.
Features
-
Package Management
- Install, uninstall, and upgrade Python packages
- List installed packages
- Add and remove project dependencies
- Compile and sync requirements
- View dependency trees
-
Project Management
- Initialize new Python projects
- Create and update lockfiles
- Build and publish packages
- Run commands in project environment
Installation
pip install mcp-server-uv
Requirements
- Python >= 3.11
- UV >= 0.1.10
- mcp-python >= 0.1.0
Usage
The server can be used as a Model Context Protocol server in compatible environments. It provides the following tools:
Package Management Tools
uv_pip_list: List installed packagesuv_pip_install: Install Python packagesuv_pip_uninstall: Remove packages from virtual environmentuv_pip_upgrade: Upgrade Python packagesuv_pip_compile: Generate requirements.txt with hashesuv_pip_sync: Sync virtual environment with requirements.txt
Project Management Tools
uv_init: Initialize a new Python projectuv_add: Add project dependenciesuv_remove: Remove project dependenciesuv_sync: Sync project dependenciesuv_lock: Update lockfileuv_run: Run commands in project environmentuv_tree: View dependency treeuv_build: Build distribution archivesuv_publish: Publish to package index
Development
Setup Development Environment
- Clone the repository
- Install development dependencies:
uv pip install -e ".[test]"
Running Tests
pytest
Test Coverage
The project uses pytest-cov for coverage reporting. Run tests with coverage:
pytest --cov=mcp_server_uv --cov-report=term-missing
License
This project is open source and available under the MIT License.
Author
- Liu Heng (liuheng@bonree.com)
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Metadata
Release files for mcp-server-uv 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_uv-0.0.9.tar.gz | 28.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_uv-0.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.8 kB
Release files / mcp_server_uv-0.0.9.tar.gz
| Download URL | mcp_server_uv-0.0.9.tar.gz |
|---|---|
| Size | 28.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d8282564bc4edd4cd5b2fff8331a84a8886f95322762680b34ebaa8e6afb708
|
|
BLAKE2b-256 checksum How to use checksums |
be23d0b180b8b1393baab5eb8eb01aec9e2ccbfc2ad19d68c265d886f32952f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / mcp_server_uv-0.0.9-py3-none-any.whl
| Download URL | mcp_server_uv-0.0.9-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93ba907ef6729c16e450ab9cbd84187bf84edde1ede0b5f080e4582b4a6ecfce
|
|
BLAKE2b-256 checksum How to use checksums |
4b517f9f3118632b0a625dbdc48321d3a22f8a71ad12695a527c49a1422aa22e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for mcp-server-uv 0.0.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.