Skip to main content
Glama
biocontext-ai

BioContextAI Knowledgebase MCP

Official
by biocontext-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to BioContextAI Knowledgebase MCP

No user-submitted related servers found.

    Related Servers

    • TogoMCP

      dbcls
      A
      license
      A
      quality
      A
      maintenance
      An 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).
      29
      16
      MIT

    • mcp-pubmed

      benoitleq
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides direct access to PubMed and PubMed Central via the NCBI E-utilities API. It enables AI models to search biomedical literature, retrieve detailed article metadata, and download open-access full texts.
      5
      MIT

    • BioMCP

      yeyuan98
      A
      license
      A
      quality
      A
      maintenance
      A high-performance MCP server that gives LLMs access to 25 biomedical tools federated across 50+ upstream APIs for genes, variants, drugs, diseases, literature, clinical trials, and structural biology.
      41
      376 npm
      12
      Apache 2.0

    • BioMCP

      qgeng1465
      F
      license
      B
      quality
      A
      maintenance
      BioMCP 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.
      73
      35 PyPI
      12
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 52 tools

    Disambiguation2/5

    The tool set spans many domains (FDA drugs, proteomics, pathways, ontologies, literature, clinical trials, grants) with overlapping search/get functions across different databases. Tools like bc_search_drugs_fda, bc_search_drugs_by_therapeutic_class, bc_get_drug_by_application_number, and bc_get_drug_label_info all relate to drug lookup but with unclear boundaries. Similarly, multiple tools for searching proteins (bc_get_uniprot_protein_info, bc_get_uniprot_id_by_protein_symbol, bc_get_string_id, bc_get_ensembl_id_from_gene_symbol) could be confused.

    Naming Consistency4/5

    Most tools follow a consistent bc_ prefix with verb_noun naming (bc_get_*, bc_search_*, bc_query_*). There are minor deviations like bc_query_open_targets_graphql vs bc_get_open_targets_graphql_schema, and bc_get_string_id vs bc_get_uniprot_id_by_protein_symbol, but overall the pattern is predictable.

    Tool Count2/5

    52 tools is excessive for a single MCP server. The server appears to be a general bioinformatics aggregator covering at least 10 distinct domains (FDA drugs, PRIDE proteomics, STRING, KEGG, Open Targets, OLS ontologies, clinical trials, literature, grants, antibodies). This would be better split into multiple focused servers.

    Completeness3/5

    The server covers many bioinformatics domains but with uneven depth. Some areas have good coverage (drugs, ontologies, clinical trials), while others are shallow (e.g., only one tool for KEGG, one for grants, one for AlphaFold). There are also gaps like no obvious way to compare drugs head-to-head or retrieve clinical trial results, and the Open Targets GraphQL tool requires external knowledge of the schema.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources