BioMCP
Related Servers
Alternatives to BioMCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceThis MCP server provides 16 intelligent tools for searching, retrieving, and linking biomedical literature from PubMed and PMC. It enables LLM applications to perform complex queries, batch processing, and cross-database linking.168MIT
- AlicenseAqualityAmaintenanceAn MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).2920MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives LLMs live access to clinical trials, FDA drug recalls, adverse-event reports, drug labels, and drug-name normalization via six validated tools.6MIT
- AlicenseNot gradedqualityCmaintenanceUnified MCP server providing AI-agent-ready access to AlphaFold, PubMed, ChEMBL, Ensembl, and 37+ scientific databases.MIT
- FlicenseBqualityAmaintenanceBioMCP is an open-source MCP server that connects any AI assistant to 15 open bioinformatics databases with zero configuration. It provides 23 tools for literature, sequences, BLAST, structures, enrichment, annotations, genomes, interactions, variants, domains, compounds, and single-cell data.7329 PyPI14-
- AlicenseBqualityAmaintenanceAn MCP server that provides standardized access to biomedical knowledge bases and resources, enabling AI systems to retrieve verified information from sources like bioRxiv, EuropePMC, and various protein/gene databases.5231Apache 2.0
TDQS
Scored across 43 tools
Most tools follow a clear entity+action split (gene_/variant_/drug_/disease_/article_/trial_/geo_/sra_/genbank_/patent_ + search/get), and descriptions actively steer agents apart (e.g. drug_search explicitly says it is not a target search, use gene_drugs; gene_get vs ensembl_lookup is carved out). A few overlaps remain that will cause misselection: five routes into clinical trials (drug_trials, gene_trials, variant_trials, disease_trials, trial_search), preprint_fulltext versus article_get on a preprint DOI, and discover versus the per-entity *_search tools. Batch_get also shadows every get tool.
The dominant convention is consistent snake_case entity_verb (gene_search/gene_get, variant_trials, article_get, geo_search, patent_get), which makes the set predictable. Deviations exist: pdb is a bare noun doing search/get/download in one tool, discover and batch_get are generic verbs without an entity, and journal_metrics/gene_enrich are noun_verb or verb-only rather than entity_action.
43 tools is heavy, but the breadth is genuine (genes, variants, drugs, diseases, trials, literature, patents, PDB, GEO/SRA/GenBank, GTEx, Ensembl, config), and most domains are well-scoped search/get pairs that earn their place. Still, several convenience wrappers (gene_articles, gene_diseases, gene_drugs, gene_trials, batch_get) could be folded into generic search tools, so the surface feels larger than strictly necessary.
Coverage of the bioinformatics domain is broad and lifecycle-complete for most entities: search+get for genes, variants, drugs, diseases, trials, articles, patents, sequences, structures, with rich cross-linking hints (sra→sra_get, geo→sra, genbank_genes→gene_search). Minor gaps: Reactome enrichment is the only pathway tool and has no reverse lookup, there is no protein/UniProt target tool separate from PDB, and no batch/list-upload path except the generic batch_get and gene_enrich gene lists.