VEPmcp
VEPmcp is a Model Context Protocol (MCP) server for the Ensembl Variant Effect Predictor (VEP) API. It enables annotation and effect prediction of genetic variants, with full support for batch and single queries, and is designed for seamless integration with MCP-compatible clients (e.g., Claude Desktop, VS Code MCP extension).
Features
- Annotate variants using Ensembl VEP (HGVS, variant ID, or genomic region)
- Batch and single variant support
- Retrieve available species, consequence types, and assembly info
- Fast, robust, and rate-limited HTTP client
- JSON-RPC 2.0 over stdio for easy integration with AI tools and editors
Installation
pip install -e .
# or, when available (soon):
pip install VEPmcp
Usage
Command Line
VEPmcp --help
VEPmcp --test-connection # Test Ensembl API connectivity
VEPmcp --test-mode # Run server in test mode with sample requests
As an MCP Server
Run the server (for use with MCP clients):
VEPmcp
The server communicates via stdio using JSON-RPC 2.0.
Supported Tools
vep_hgvs_single/vep_hgvs_batch: Annotate by HGVS notationvep_id_single/vep_id_batch: Annotate by variant ID (e.g., rsID)vep_region_single/vep_region_batch: Annotate by genomic regionget_vep_species: List available speciesget_consequence_types: List consequence typesget_assembly_info: Get assembly info for a species
Example MCP Client Configurations
Claude Desktop
{
"mcp_servers": {
"vepmcp": {
"command": "VEPmcp",
"args": [],
"env": {}
}
}
}
VS Code MCP Extension
{
"mcp.servers": {
"vepmcp": {
"command": "VEPmcp",
"args": [],
"env": {},
"cwd": "${workspaceFolder}"
}
}
}
Example Usage
Prompt your MCP client with:
"Annotate the variant rs56116432 in humans using VEP"
Testing
VEPmcp --test-connection— check API connectivityVEPmcp --test-mode— run server in test modepython run_tests.py --mode all --verbose— run all unit/integration testspython run_tests.py --mode ci— run CI pipeline (linting + type checking + unit tests)
Continuous Integration
This project uses GitHub Actions for automated testing on every pull request. The CI pipeline includes:
- Linting with Ruff
- Type checking with MyPy
- Unit and integration tests across Python 3.9-3.13
- Security scanning
- Code coverage reporting
Troubleshooting
- Ensure VEPmcp is installed and in your PATH
- Check internet connectivity for Ensembl API access
- Use
--verbosefor detailed logs
Development
pip install -e .[dev]
python run_tests.py --mode ci # Run linting, type checking, and unit tests
python run_tests.py --mode all --verbose # Run all tests including integration
Local Testing Commands
# Linting and formatting
python run_tests.py --mode lint
# Type checking
python run_tests.py --mode type
# Unit tests only
python run_tests.py --mode unit --verbose
# Integration tests (requires internet)
python run_tests.py --mode integration --verbose
License
MIT License — see LICENSE
Contributing
- Fork and branch
- Make changes and add tests
- Run the test suite
- Submit a pull request
Support
For issues and questions, use the GitHub issue tracker.
Metadata
Release files for VEPmcp 0.1.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 | |
|---|---|---|---|---|
| vepmcp-0.1.0.tar.gz | 15.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vepmcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.8 kB
Release files / vepmcp-0.1.0.tar.gz
| Download URL | vepmcp-0.1.0.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bab2f1c60c7ed310af1aa31efe64100cedfdaa0abaed0e3bca2940fd8876f825
|
|
BLAKE2b-256 checksum How to use checksums |
9a233e0035a50a1718fe31f84e897fb70e7001b247ce087b4ba810baf1cec6af
|
| 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 Jul 16, 2025.
Transparency logRelease files / vepmcp-0.1.0-py3-none-any.whl
| Download URL | vepmcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfdb086760a30127b10d66ef24c6d6357dc86a2e626a76d8512432bc06b72959
|
|
BLAKE2b-256 checksum How to use checksums |
fca50297e77471d72ef45722e4eebea6cb23475a798a0095da6e7e7efd70b11d
|
| 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 Jul 16, 2025.
Transparency logSecurity for VEPmcp 0.1.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 vepmcp-0.1.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 Jul 16, 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.