Reactome Mcp Server

Created By
Augmented-Naturea year ago
Model Context Protocol server for accessing Reactome pathway and systems biology data.
Overview

What is Reactome MCP Server?

Reactome MCP Server is a Model Context Protocol server designed for accessing Reactome pathway and systems biology data, providing a comprehensive interface for biological research.

How to use Reactome MCP Server?

To use the Reactome MCP Server, install the server using npm, build it, and run the server. You can then configure it with various MCP clients to access the API.

Key features of Reactome MCP Server?

  • 🔍 Pathway Search: Search biological pathways by name, process, or keywords.
  • 📊 Pathway Details: Access comprehensive information about specific pathways.
  • 🧬 Gene-to-Pathways: Find pathways associated with specific genes or proteins.
  • 🦠 Disease Pathways: Explore disease-associated biological mechanisms.
  • 🌲 Pathway Hierarchy: Understand parent/child relationships and pathway structures.
  • 🧪 Pathway Participants: Get all molecules participating in pathways.
  • ⚗️ Biochemical Reactions: Detailed information on biochemical reactions.
  • 🔗 Protein Interactions: Discover molecular interactions within pathways.

Use cases of Reactome MCP Server?

  1. Systems biology research to analyze DNA repair pathways.
  2. Investigating disease mechanisms related to cancer.
  3. Supporting drug discovery by identifying pathways for drug targets.

FAQ from Reactome MCP Server?

  • Can I access all Reactome data through this server?

Yes! The server provides access to a wide range of Reactome data including pathways, reactions, and protein interactions.

  • Is there any authentication required to use the API?

No, the API does not require authentication for access.

  • What programming languages can I use to interact with the server?

You can use any programming language that can make HTTP requests to interact with the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Augmented-Nature
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago