Biomcp Ts MCP Server

Connect Biomcp Ts to Claude, Cursor or any other MCP client and it stops being a tab you switch to. BioMCP - Biomedical MCP Server in TypeScript. The biomcp ts mcp server is what makes that connection.

What the server does

A high-performance MCP server that gives LLMs access to 25 biomedical tools federated across 50+ upstream APIs — genes, variants, drugs, diseases, literature, clinical trials, and structural biology in a single integration.

• 25 tools — across 8 domains — search, retrieve, and cross-reference biomedical entities
• Section-based fetching — — entityGet(id, sections) fans out to multiple sources with per-section timeouts and graceful degradation (failed sections return { _error } instead of crashing)
• Federated article search — — queries 5 literature backends simultaneously with PMID/PMCID/DOI deduplication
• Zero-config startup — — works out of the box; optional API keys unlock higher rate limits and premium data
• 350+ unit tests — (mocked) + 90+ integration tests (live APIs via in-process MCP client, with automatic retry on 429 rate limits)

Installation

Installation goes through your MCP client rather than a global install: point it at After on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

Configuration is passed through the environment: ONCOKB_TOKEN, NCBI_API_KEY, S2_API_KEY, OPENFDA_API_KEY, NCI_API_KEY, DISGENET_API_KEY, UMLS_API_KEY, ALPHAGENOME_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by yeyuan98; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Biomcp Ts's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.