Skip to main content

uv-mcp

A Model Context Protocol (MCP) server for interacting with Python installations via uv, the fast Python package installer.

Overview

uv-mcp provides LLMs with direct access to inspect and manage Python environments through the uv package manager. This allows AI assistants to help with Python dependency management, environment inspection, and troubleshooting tasks.

Features

  • Environment Inspection: Query installed packages and their versions
  • Dependency Resolution: Check compatibility between packages
  • Environment Comparison: Identify differences between local and cloud/production environments
  • Requirement Management: Parse and validate requirements files
  • Package Information: Retrieve metadata about PyPI packages
  • Virtual Environment Management: Create and manage virtual environments

How It Works

uv-mcp implements the Model Context Protocol to expose Python environment data and package management functionality through standardized resources and tools.

Resources

  • python:packages://installed - List of all installed packages and versions
  • python:packages://outdated - List of installed packages with newer versions available
  • python:packages://{package_name}/latest - Latest versions available for a package
  • python:packages://{package_name}/dependencies - List of dependencies for a specific package
  • python:requirements://{file_path} - Parsed content of requirements files

Tools

  • uv_run(command: str[]) - Run a command or script
  • uv_init() - Create a new project
  • uv_add(package_name: str, version: Optional[str]) - Add dependencies to the project
  • uv_remove(package_name: str) - Remove dependencies from the project
  • uv_sync(dry_run: bool) - Install all declared dependencies, uninstall anything not declared
  • uv_lock() - Update the project's lockfile
  • pip(command: str[]) - Run a pip command
  • pip_install(package_name: str, version: Optional[str]) - Install a package using pip
  • pip_uninstall(package_name: str) - Uninstall a package using pip
  • pip_list() - List all installed packages using pip

Usage

To start the server:

uvx uv-mcp

Development

This project is built with the MCP Python SDK and uv.

Metadata

Release files for uv-mcp 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for uv-mcp 0.3.0
File Size Uploaded Provenance
uv_mcp-0.3.0.tar.gz 27.7 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for uv-mcp 0.3.0
File Interpreter ABI Platform
uv_mcp-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 33.8 kB

Release files / uv_mcp-0.3.0.tar.gz

Download URL uv_mcp-0.3.0.tar.gz
Size 27.7 kB
Tags Source
SHA-256 checksum
How to use checksums
9d562e7aea361d0deeb845749e1550eb6d69160242f6c2333eab14f33da536b7
BLAKE2b-256 checksum
How to use checksums
e9a6c481b3cc52cb4dab2bd8ac4662a1105fe3ff32c7b632926850104b3c568f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 26, 2025.

Transparency log

Release files / uv_mcp-0.3.0-py3-none-any.whl

Download URL uv_mcp-0.3.0-py3-none-any.whl
Size 6.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b2ed61782046c25c82dc15ba5841d4ce42d7fc2f06c78da8c8f579fa0f216668
BLAKE2b-256 checksum
How to use checksums
343098df462df0c26d6e99b7f2b45e2092e51eec4b7e2d2465a8e0fd5443863a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 26, 2025.

Transparency log

Security for uv-mcp 0.3.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for uv_mcp-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 26, 2025.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page