mcp-alphafold
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_alphafold_predictionA | This tool retrieves all available AlphaFold models for a specified UniProt accession. It allows querying by the UniProt accession or by the CRC64 checksum of the UniProt sequence. Arguments
Example Input:
Response StructureThe response will be a list of objects, each containing detailed information about the available AlphaFold models. Example Output: |
| get_uniprot_summaryC | This tool fetches AlphaFold model predictions for a given UniProt residue range. The tool takes in a UniProt accession number (AC), entry name (ID), or CRC64 checksum and returns detailed information about the structure models available for the specified sequence range. Arguments
Example Input:
Response StructureThe response includes detailed information about the UniProt entry and its associated AlphaFold models. Example Response: |
| get_annotationsB | This tool retrieves all annotations for a specified UniProt residue range. It allows querying by the UniProt accession and the annotation type (e.g., MUTAGEN for AlphaMissense). Arguments
Example Input:
Response StructureThe response includes detailed information about the UniProt entry and its associated annotations. Example Output: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
get_alphafold_prediction and get_uniprot_summary both retrieve AlphaFold model information for a UniProt accession, with overlapping purposes. The descriptions do not clearly distinguish when to use one over the other, causing potential misselection. get_annotations is the only clearly distinct tool.
All tool names follow a consistent get_<noun> pattern using snake_case. This predictable naming convention makes the tool set easy to navigate.
With only 3 tools, the server is well-scoped and focused on AlphaFold data retrieval. Each tool has a meaningful role, even though two overlap functionally.
The server covers the core operations for AlphaFold: listing models, fetching a summary, and retrieving annotations. There are no obvious gaps for the intended domain, as structure URLs are included in responses.