VEPmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vep_hgvs_singleC | Annotate a single variant using HGVS notation (genomic g., coding c., protein p.) |
| vep_hgvs_batchA | Annotate multiple variants using HGVS notation in batch |
| vep_id_singleC | Annotate a single variant using an identifier (e.g., rs1234567, COSM476) |
| vep_id_batchC | Annotate multiple variants using identifiers in batch |
| vep_region_singleC | Annotate a variant using genomic region and allele |
| vep_region_batchB | Annotate multiple variants using genomic coordinates in batch |
| get_vep_speciesA | Get list of available species for VEP annotation |
| get_consequence_typesA | Get available VEP consequence types and descriptions |
| get_assembly_infoB | Get genome assembly information for a species |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/not-a-feature/VEPmcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server