Python Tools MCP
A Model Context Protocol (MCP) server that exposes modern Python development tools.
Features
- Manage Python dependencies using
uv - Run tests with
pytestand coverage measurement - Lint and format code with
ruff - Type checking with
basedpyrightormypy - Analyze and improve code quality with tools like
vulture,radon, andbandit - Check docstring coverage with
interrogate - Profile Python code with
py-spy
Installation
uv sync
Usage
Start the server:
uvx python_tools_mcp
Then use the tools in your MCP-compatible application.
Example Tools
pytest: Run tests with optional coverageruff_check: Lint Python coderuff_format: Format Python codeuv_add: Add dependenciesuv_sync: Install dependenciescoverage_analyze: Analyze existing coverage data
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for python-tools-mcp 0.2.0
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 | Actions |
|---|---|---|---|---|
| python_tools_mcp-0.2.0.tar.gz | 20.8 kB | With provenance | Details for python_tools_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| python_tools_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for python_tools_mcp-0.2.0-py3-none-any.whl |
Total release size: 29.7 kB
Release files / python_tools_mcp-0.2.0.tar.gz
| Download URL | python_tools_mcp-0.2.0.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea983fc7220905ae0fcd3eb28674248f6e83370cba679d66268cb725c9b08fc4
|
|
BLAKE2b-256 checksum How to use checksums |
51f45bb7b4246130595f4437bcc9e88e5ab1d4db828537e17dfa698c99874753
|
| 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 Jun 12, 2025.
Transparency logRelease files / python_tools_mcp-0.2.0-py3-none-any.whl
| Download URL | python_tools_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
600c1b77cdfc16dde810bf74feca3515b04705d99305a1763e263f15ad5379af
|
|
BLAKE2b-256 checksum How to use checksums |
073dd2c53c22a701310bbe364f3961a2c1ec0fa42f77fc5f263dc68dfa6cc486
|
| 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 Jun 12, 2025.
Transparency logSecurity for python-tools-mcp 0.2.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.
Attestation for python_tools_mcp-0.2.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 Jun 12, 2025.
Transparency logA 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.
