reactome-db-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REACTOME_DB_HOST | No | MySQL endpoint host | 127.0.0.1 |
| REACTOME_DB_NAME | No | Database name | reactome_local |
| REACTOME_DB_PORT | No | MySQL endpoint port | 3306 |
| REACTOME_DB_USER | No | MySQL username | ro_user |
| REACTOME_DB_MAX_ROWS | No | Default row cap | 200 |
| REACTOME_DB_PASSWORD | No | MySQL password | |
| REACTOME_DB_POOL_SIZE | No | Max pooled connections | 4 |
| REACTOME_DB_MAX_CELL_CHARS | No | Per-cell text cap in characters | 2000 |
| REACTOME_DB_STMT_TIMEOUT_MS | No | Per-query timeout in milliseconds | 15000 |
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 |
|---|---|
| schema_overviewA | Explain the Reactome GKB schema so you can write correct SQL. |
| list_tablesA | List tables in the database with their (exact) row counts and engine. |
| describe_tableA | Show the columns of a table: name, type, nullability, key, default, extra. |
| queryA | Run a single READ-ONLY SQL statement against the Reactome DB. |
| get_objectA | Fetch a full Reactome object, assembled across its inheritance chain. |
| search_by_nameA | Search objects by |
| get_pathway_eventsA | List the ordered child events (sub-pathways & reactions) of a pathway. |
| get_participantsA | Get the inputs, outputs, and catalysts of a reaction-like event. |
| get_referrersA | Reverse lookup: which objects point AT this one (the inverse navigation REST makes awkward). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_primer_resource | The Reactome GKB schema primer (same text as `schema_overview`'s `primer`). |
TDQS
Scored across 9 tools
Each tool has a distinct purpose: schema exploration (list_tables, describe_table, schema_overview), object retrieval (get_object, search_by_name), relationship queries (get_participants, get_pathway_events, get_referrers), and raw SQL (query). No overlapping functionality.
Most tools follow a consistent verb_noun pattern (e.g., describe_table, get_object, list_tables). However, 'query' and 'schema_overview' are outliers—'query' is a bare verb and 'schema_overview' is noun_noun—but the overall pattern is mostly adhered to.
With 9 tools, the server is well-scoped for a biological database MCP server. It provides essential operations without bloat, covering schema exploration, object retrieval, relationship navigation, and custom queries.
The tool set covers the primary interactions with Reactome: exploring schema, fetching objects, searching by name, retrieving participants and pathway events, reverse lookups, and arbitrary SQL queries. No obvious gaps for typical workflows.