biomcp and biothings-mcp
These are ecosystem siblings—BioMCP provides a general-purpose biomedical context protocol server, while biothings-mcp implements the same MCP specification as a specialized server for the BioThings semantic web API, allowing them to coexist as alternative or complementary data sources within the same MCP client ecosystem.
About biomcp
genomoncology/biomcp
BioMCP: Biomedical Model Context Protocol
Implements a unified CLI and MCP server that federates queries across 20+ biomedical APIs (PubMed, ClinVar, UniProt, cBioPortal, etc.) with a single grammar—`search`, `get`, and cross-entity pivots eliminate API-specific syntax. Supports local study analytics (cohort, survival, co-occurrence) from cBioPortal datasets with native SVG/PNG charts, plus progressive disclosure via composable sections and batch enrichment via g:Profiler. Deploys as a standalone binary, PyPI tool, Claude Desktop MCP server, or remote HTTP service with automatic reconnection and health probes.
About biothings-mcp
longevity-genie/biothings-mcp
MCP (Model Context Protocol) server for biothings
Provides unified MCP interfaces to multiple BioThings.io biomedical databases (genes, variants, chemicals, taxa) using strongly-typed async clients, enabling AI assistants to query authoritative sources like mygene.info and myvariant.info. Supports three transport modes—stdio, HTTP streamable, and Server-Sent Events—with local file saving capabilities for downloaded sequences and annotations in FASTA, GenBank, and JSON formats. Integrates seamlessly with Claude Desktop, Cursor, and other MCP-compatible AI clients through pre-configured JSON manifests.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work