Medical Mcps

What is Medical Mcps?

Medical Mcps is an MCP server that integrates multiple biological and medical databases for research purposes. It provides over 100 tools across 14 APIs covering pathways, genes, variants, diseases, drugs, literature, and clinical trials.

How to use Medical Mcps?

Configure it in an MCP client (e.g., Cursor) by adding the production URL https://medical-mcps-production.up.railway.app/tools/unified/mcp to your .cursor/mcp.json. Once connected, you can call any of the 100+ tools, such as mygene_get_gene for gene information. For local development, use Docker Compose or run the server directly with uv run mcp-server.

Key features of Medical Mcps

• Unified endpoint to access all 14 APIs in one connection
• Individual API endpoints for selective tool access
• Supports local deployment via Docker Compose or Python/uv
• HTTP caching with 30-day default TTL (hishel, per-API SQLite files)
• Optional Sentry integration for error tracking and performance monitoring
• Uses Streamable HTTP transport per MCP specification

Use cases of Medical Mcps

• Retrieve pathway and gene data from Reactome, KEGG, or Pathway Commons
• Search for drug-target interactions and bioactivity data via ChEMBL
• Query clinical trial metadata from ClinicalTrials.gov and NCI
• Look up genetic variant annotations and population frequencies with MyVariant.info
• Explore drug repurposing strategies using structured playbooks

FAQ from Medical Mcps

What runtime/requirements does Medical Mcps need?

For local development, Python with uv is required; Docker Compose is recommended for quick setup.

How do I configure Medical Mcps in Cursor?

Add the production URL https://medical-mcps-production.up.railway.app/tools/unified/mcp to the mcpServers object in your .cursor/mcp.json file.

Does Medical Mcps require API keys for any services?

Yes, OMIM and NCI Clinical Trials require API keys. These are configured via environment variables or passed when initializing the respective clients.

How can I test if the production server is accessible?

Send a POST request with a JSON-RPC initialize message to the unified endpoint, e.g., using curl with the URL /tools/unified/mcp.

Can I access individual APIs separately instead of using the unified endpoint?

Yes. Each API has its own endpoint (e.g., /tools/reactome/mcp) that you can configure as a separate MCP server in your client.