uniprot-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_entryC | Return a structured UniProt entry. |
| get_sequenceA | Return only the sequence metadata for an accession. |
| search_uniprotC | Search UniProtKB and return curated hits. |
| fetch_entry_flatfileC | Return the UniProt flatfile (txt or fasta) for a specific entry version. |
| map_idsC | Map identifiers between UniProt-supported namespaces. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_protein | Generate instructions for summarising a UniProt entry. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| search_help | Static help text explaining search conventions. |
TDQS
Scored across 5 tools
Tools 1-3 all fetch data for a given entry but in different formats (structured, flatfile, sequence). They are distinct enough with clear descriptions, but an agent might briefly hesitate between fetch_entry and fetch_entry_flatfile. map_ids and search_uniprot are completely separate.
All tool names follow a consistent verb_noun pattern with underscores (fetch_entry, fetch_entry_flatfile, get_sequence, map_ids, search_uniprot). No mixing of styles or abbreviations.
5 tools is an appropriate number for a focused UniProt server. It covers the main operations (entry retrieval, sequence, ID mapping, search) without being too minimal or overwhelming.
The tool set covers core UniProt workflows: retrieving entries in multiple formats, extracting sequence, ID mapping, and search. Minor gaps like batch operations or advanced query filtering exist, but these are acceptable for a basic server.