plant-genomics-mcp
Related Servers
Alternatives to plant-genomics-mcp
- AlicenseAqualityAmaintenanceSearches and fetches research datasets across Zenodo, DataCite (Dryad/Figshare/Dataverse/OSF), NCBI omics archives (GEO/SRA/BioProject), and the literature (PubMed/OpenAIRE) through one normalized model — deduplicating by DOI, expanding organism queries with NCBI Taxonomy synonyms, and bridging papers to the datasets they produced. Resolves citations and open-access full text, and downloads files.6187 PyPI4MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server providing public plant bioinformatics APIs including UniProt, NCBI, InterProScan, PDB, AlphaFold, Ensembl Plants, and web-based resources like Sol Genomics and BAR, without local data. It supports gene lookups, protein summaries, structure retrieval, and functional annotations through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables functional enrichment analysis of gene lists against multiple pathway and ontology databases, plus gene/protein identifier conversion and cross-species ortholog mapping.493 npmMIT
- AlicenseNot gradedqualityAmaintenanceRead-only biomedical MCP server connecting PubMed, ClinicalTrials.gov, ClinVar, gnomAD, OncoKB, Reactome, KEGG, UniProt, PharmGKB, CPIC, OpenFDA, Monarch Initiative, GWAS Catalog, and more. One command grammar for all biomedical entities — genes, variants, diseases, drugs, trials, articles, phenotypes, pathways, proteins, diagnostics, and adverse events. 27 tools. Apache-2.0 license.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables users to look up yeast genes/loci, search genes and alleles by free text, and retrieve Gene Ontology annotations from the Saccharomyces Genome Database.194 npmMIT
- AlicenseAqualityBmaintenanceEnables unified access to 110 life science APIs and databases, including genomics, proteomics, chemistry, literature, and clinical data. Users can query genes, proteins, compounds, pathways, and more through natural language.3MIT
- AlicenseAqualityAmaintenanceGrounds gene-nomenclature work in the HUGO Gene Nomenclature Committee (HGNC) dataset, enabling resolution of gene symbols and IDs to canonical HGNC identifiers, plus cross-references and batch operations.9MIT
TDQS
Scored across 58 tools
The descriptions work hard to separate near-neighbors (e.g. 'Unlike locus_go_annotations...', 'Unlike string_interactions...'), which rescues much of the overlap. But the surface still has real duplication: tair_locus_info is explicitly 'Alias of bar_gene_summary', five synthesis tools (gene_report, analyze_locus_synth, biological_context_synth, consensus_homologs, find_homologs_synth) partially re-run the same fan-outs, and 15+ dedicated batch_* tools are subsumed by batch_locus_call.
A source-prefix convention (ensembl_plants_, bar_, batch_, locus_) is applied fairly consistently, but verb style is mixed: resource-first nouns (gramene_homologs, kegg_pathways, interpro_domains, tf_binding_motifs) sit alongside verb_noun names (get_sequence, resolve_locus_to_uniprot, blast_sequence, vep_annotate, entry_members). Suffix conventions also split (_synth suffix vs sync tools, batch_ prefix vs no batch variant for some tools), so it is readable but not predictable.
58 tools is far past a well-scoped surface for one server. Much of the bulk is mechanical batch duplication (a batch_* twin for most single-locus tools) that batch_locus_call already generalizes, plus multiple overlapping synthesis/dossier tools, so many entries do not earn a distinct place.
Coverage of the plant-genomics domain is genuinely broad: locus resolution, sequences, domains, structures, GO/PO/TO enrichment, pathways, homology/orthology, interactions, coexpression, variants, GWAS, literature, and release provenance. Minor gaps remain (no arbitrary-region sequence retrieval, no MSA/phylogenetics, expression limited to BAR eFP and ATTED-II), but agents can work around these.