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).2918MIT
- AlicenseAqualityBmaintenanceAn 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.7312-
- AlicenseBqualityCmaintenanceAn 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.5230Apache 2.0
TDQS
Scored across 41 tools
Most tools follow a clear entity/action or entity/relation pattern, so gene_trials, variant_trials, drug_trials, and trial_search are distinguishable by name. A few fuzzy boundaries remain: discover overlaps with the domain searches, gene_get overlaps with ensembl_lookup, and gene_articles could be confused with article_search.
The dominant convention is consistent: entity_search/entity_get pairs and entity_relation tools like disease_drugs and gene_trials all use snake_case noun-first names. Generic outliers (discover, pdb, batch_get) and source-prefixed tools (ensembl_*, gtex_*) break the pattern slightly.
41 tools is a very large surface, exceeding the 25+ threshold for 'too many' regardless of how well-named they are. The broad biomedical scope justifies some size, but many search/get/relation tools could plausibly be consolidated into parameterized endpoints to reduce agent navigation cost.
The read-only biomedical surface is unusually thorough: all major entities have search/get plus cross-entity links (trials, drugs, diseases, articles, enrichment, expression, homology). Minor gaps remain, such as no direct variant-disease or disease-article endpoint, but they are workaroundable via existing search tools.