STRING-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_identifiersC | Map protein identifiers to STRING IDs. |
| get_network_interactionsC | Retrieve STRING interaction edges. |
| get_functional_enrichmentC | Perform GO / pathway enrichment on a protein set. |
| get_functional_annotationC | Retrieve all functional annotations for proteins. |
| get_interaction_partnersC | Retrieve interaction partners for given proteins. |
| get_homologyB | Get homology information for proteins. |
| get_homology_bestC | Get best homology matches for proteins. |
| get_ppi_enrichmentC | Get protein-protein interaction enrichment statistics. |
| get_version_infoB | Return the current STRING database version. |
| get_network_imageC | Return URL of STRING network image |
| get_enrichment_figureC | Return URL of enrichment scatter figure |
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 11 tools
Most tools have clearly distinct purposes, such as get_functional_annotation for annotations and get_network_interactions for edges. However, get_homology and get_homology_best could be confused, as both retrieve homology information with only subtle differences in scope.
All tools follow a consistent verb_noun pattern with 'get_' or 'map_' prefixes, such as get_enrichment_figure and map_identifiers. There are no deviations in naming conventions, making the set highly predictable and readable.
With 11 tools, the count is well-scoped for a protein interaction and enrichment analysis server. Each tool appears to serve a specific, non-redundant function, fitting within the typical 3-15 tool range for such domains.
The tool set covers core protein analysis workflows, including enrichment, homology, interactions, and identifier mapping. A minor gap exists in lacking update or delete operations, but this is reasonable for a retrieval-focused database server, and agents can work around this.