uniprot-unipressed-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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uniprot_searchA | Search the UniProt protein database using query syntax. Args: query: UniProt query string. Examples: - gene:BRCA1 - Search by gene name - organism_id:9606 - Human proteins (NCBI taxonomy ID) - (gene:BRCA*) AND (organism_id:10090) - Mouse BRCA genes with wildcard - length:[500 TO 700] - Proteins of specific length range - keyword:kinase - By UniProt keyword - family:serpin - By protein family - ec:3.2.1.23 - By enzyme classification - database:pfam - With Pfam cross-references - reviewed:true - Only Swiss-Prot reviewed entries Returns: When response_format='json': JSON object with: - results: Array of matching protein entries - total: Total number of matching entries (if available) - nextCursor: Cursor string for retrieving the next page (if more results exist) See https://www.uniprot.org/help/query-fields for full query syntax documentation. |
| uniprot_fetchA | Fetch specific protein entries by their UniProt accession IDs. Args: ids: List of UniProt accession IDs to fetch. Examples: - ["P62988"] - Single protein - ["A0A0C5B5G6", "A0A1B0GTW7"] - Multiple proteins Returns: When response_format='json': JSON object with: - results: Array of fetched protein entries - found: Number of entries successfully retrieved - requested: Number of IDs that were requested |
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 2 tools
Each tool has a clearly distinct purpose: uniprot_fetch retrieves specific entries by IDs, while uniprot_search performs complex queries. There is no overlap in functionality.
Both tool names follow a consistent verb_noun pattern with snake_case (uniprot_fetch, uniprot_search), making them predictable and easy to understand.
With only 2 tools, the server is very thin for the vast UniProt domain. While fetch and search are core operations, the lack of other tools (e.g., for updates or batch operations) makes it feel limited.
The server covers basic retrieval operations (fetch by ID and search) but lacks any write or update functionality. For a read-only interface this might be acceptable, but tools for batch processing or data submission are missing.