reactome-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@reactome-mcpRun Reactome enrichment on TP53, EGFR, BRCA1, MDM2, CDKN1A and list the top 5 pathways."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
reactome-mcp
An MCP server that gives coding agents first-class access to the Reactome pathway database — search, look up, traverse, export to SBML/SBGN, and run gene-set pathway-enrichment analysis, all from the chat.
Built with the official Python MCP SDK (FastMCP) over stdio. It wraps both Reactome REST services:
ContentService — full-text search, entity/pathway lookup, hierarchy traversal, participants, complex subunits, interactors, and SBML/SBGN/diagram export.
AnalysisService — submit a gene/protein list and get back ranked, enriched pathways with p-value/FDR.
Because it speaks plain MCP over stdio (no vendor-specific extensions), it works with any MCP-capable agent — Claude Code, Codex, Cursor, and others. Only the registration command differs.
Quickstart
Requires uv (which manages Python ≥ 3.12 for you).
git clone https://github.com/tc2fh/reactome-mcp.git
cd reactome-mcp
uv sync # install runtime deps
uv run reactome-mcp # boots the server on stdio (Ctrl+C to exit)Then register it with your agent (see below) and ask it something like:
"Run Reactome enrichment on TP53, EGFR, BRCA1, MDM2, CDKN1A and list the 5 most significant pathways with their FDR."
Related MCP server: Oh My KEGG MCP
Register with your agent
The server is a standard stdio MCP server launched with uv run reactome-mcp. Run these from inside the cloned directory.
Claude Code
claude mcp add reactome -- uv --directory "$PWD" run reactome-mcpCodex
codex mcp add reactome -- uv --directory "$PWD" run reactome-mcp…or add a table to ~/.codex/config.toml:
[mcp_servers.reactome]
command = "uv"
args = ["run", "--directory", "/absolute/path/to/reactome-mcp", "reactome-mcp"]Cursor — add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"reactome": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/reactome-mcp", "reactome-mcp"]
}
}
}Any other MCP client (Windsurf, Cline, Zed, Pi, …) — point it at the same stdio command. A ready-to-edit example lives in .mcp.json:
{
"mcpServers": {
"reactome": {
"type": "stdio",
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/reactome-mcp", "reactome-mcp"],
"env": {}
}
}
}Tools
All tools are async, return JSON-shaped dicts (or a path string for downloads), and degrade to {"error": ...} rather than raising on HTTP/network failures.
Search & lookup
Tool | Signature | Purpose |
|
| Solr free-text search; returns flattened, highlight-stripped entries + per-type counts. |
|
| Full record for any object by stable id/dbId; size-guarded; |
|
| Batch lookup for up to 20 identifiers at once. |
Pathway hierarchy & participants
Tool | Signature | Purpose |
|
| Top-level pathways (browser entry points) for a species name/taxId. |
|
| All sub-pathways and reactions contained in a pathway (recursive). |
|
| Paths from an event up to its top-level pathway(s) — breadcrumbs. |
|
| Physical entities (+ their reference entities) in a reaction/pathway. |
|
| Which lower-level pathways contain a given molecule/complex. |
Entities, interactors, reference data
Tool | Signature | Purpose |
|
| Recursively list the subunits of a complex. |
|
| Curated IntAct protein–protein interactors for an accession. |
|
| Species annotated in Reactome (name, taxId, abbreviation). |
|
| Diseases (Disease Ontology terms) annotated in Reactome. |
Exporters
Tool | Signature | Purpose |
|
| Export a pathway/reaction to SBML or SBGN inline; head/tail truncation past |
|
| Stream an export to disk (event→sbml/sbgn, diagram/reaction/fireworks→png/svg, document→pdf). |
Enrichment analysis
Tool | Signature | Purpose |
|
| Submit a gene/protein list; returns a |
|
| Page/sort/filter a prior analysis by its token (no re-submission). |
|
| Identifiers from the submission that did not map to Reactome. |
Design notes
Reactome stable ids look like
R-HSA-69278; numeric dbIds and plain accessions (e.g.P04637) are also accepted. Path identifiers are validated so they can't escape the intended endpoint.searchstrips Reactome's Solr<span class="highlighting">markup and flattens the clusteredresults[] → entries[]shape into one list.get_entryandget_event_sbmlare size-guarded so multi-MB records / SBML never flood the chat — they point you todownload_export, which streams to disk.analyze_identifiersreturns atoken; reuse it withget_analysis_results/get_analysis_not_foundto page and inspect without re-running the analysis.
Example prompts
Search + lookup — "Search Reactome for TP53, then look up 'Transcriptional Regulation by TP53' and summarise what it does."
Enrichment — "Run Reactome enrichment on TP53, EGFR, BRCA1, MDM2, CDKN1A and list the 5 most significant pathways with their FDR."
SBML export — "Find 'Cell Cycle Checkpoints', export its SBML to ./reactome_downloads, and tell me how many species and reactions it defines."
Hierarchy — "List the top-level human pathways, then drill into 'Cell Cycle' and show its contained events."
Development
uv sync --extra dev # install test deps (pytest, pytest-asyncio, respx)
uv run pytest # offline suite — every request is mocked via respxThe suite (tests/) runs entirely offline against captured fixtures in samples/, so it needs no network. Smoke-test the live server in any of these ways:
uv run reactome-mcp # console script
uv run python -m reactome_mcp # module entry point
uv run python server.py # source-checkout shim
uv run mcp dev src/reactome_mcp/server.py # MCP Inspector dev UIreactome-mcp/
├── src/reactome_mcp/ # installable package (server.py = all tools + helpers)
├── server.py # source-checkout compatibility shim
├── tests/ # offline pytest suite (respx-mocked)
├── samples/ # captured API responses used as fixtures
├── pyproject.toml # uv-managed project
└── .mcp.json # example stdio MCP configAcknowledgements
Powered by Reactome, a free, open-source, open-access, curated and peer-reviewed pathway database. Please cite Reactome when publishing work that uses this data — see https://reactome.org/cite.
This project is not affiliated with or endorsed by the Reactome team.
License
MIT © Tien Comlekoglu
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tc2fh/reactome-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server