STRING MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_string_idsA | Map protein names, synonyms, and UniProt identifiers to STRING identifiers. Species parameter uses NCBI taxon IDs (e.g., 9606 for human, 10090 for mouse). |
| get_networkC | Retrieve protein-protein interaction network for given proteins. Returns network edges with confidence scores. |
| get_interaction_partnersA | Get all STRING interaction partners for your proteins. Returns a list of interacting proteins with confidence scores. |
| get_enrichmentC | Perform functional enrichment analysis for a set of proteins. Tests for over-representation in Gene Ontology terms, KEGG pathways, etc. |
| get_ppi_enrichmentB | Test if your protein set has more interactions than expected by chance. Returns enrichment p-value. |
| get_homologyC | Get homology information for proteins across species using STRING. |
| get_homology_bestC | Get the best homology match for proteins in a target species. |
| resolve_proteinsC | Resolve protein names to their preferred names in STRING database. |
| get_versionB | Get the current version of the STRING database. |
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 9 tools
Most tools have distinct purposes, such as get_enrichment for functional analysis and get_network for interaction networks. However, get_homology and get_homology_best could be confused as they both handle homology, with the latter being a more specific version, creating minor ambiguity.
All tool names follow a consistent verb_noun pattern starting with 'get_' or 'resolve_', such as get_enrichment and resolve_proteins. This uniformity makes the set predictable and easy to navigate.
With 9 tools, the server is well-scoped for protein analysis tasks, covering key operations like enrichment, homology, interactions, and ID mapping. Each tool serves a clear purpose without being overwhelming.
The tool set covers essential protein analysis workflows, including enrichment, homology, interactions, and ID resolution. A minor gap exists in lacking update or delete operations, but this is reasonable for a read-focused database query server.