Biologist MCP Server
Related Servers
Alternatives to Biologist MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and traverse spec genomes via MCP tools, providing structured access to entities, relationships, and graph data.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to run hybrid retrieval, build token-budgeted attributed context packs, answer questions with citation and groundedness-gated release, explore temporal graph entities, evaluate claim support, and ingest screened, embedded documents through typed MCP tools.Apache 2.0
- FlicenseBqualityBmaintenanceEnables AI agents to query an air-gapped enterprise knowledge vault via seven MCP tools for deterministic and hybrid retrieval, entity graph traversal, context compression, archive inspection, onboarding scans, and node status.7-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to persistently store and semantically search shared knowledge via MCP tools.2MIT
- AlicenseBqualityBmaintenanceEnables AI agents to query, manipulate, cluster, and synthesize physics domain models—including particle groups, subatomic particles, quantum states, and cluster reports—through MCP tools, resources, and prompts over stdio.511MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search an organization's data ecosystem, explore table- and column-level lineage, retrieve usage queries, manage metadata such as tags, owners, domains, and terms, and work with knowledge documents through MCP tools.Apache 2.0
TDQS
Scored across 51 tools
The tool set is organized by resource, but several tools have overlapping boundaries: get_platform_status and get_settings both expose embedding/LLM configuration, while create_*, upsert_*_batch, and populate_* provide three different creation paths for biomes, species, and organisms. report_summary/sub_report/cluster_report tools are distinguishable, but the sheer number of similarly named lifecycle tools increases misselection risk.
Most names follow a clear snake_case verb_noun pattern (list_biomes, create_species, delete_organism, generate_organism_embedding). There are minor deviations such as the bare 'search' and some noun-heavy report names, but the convention is generally predictable.
At 51 tools, the surface is heavy for any MCP server and includes many near-parallel CRUD, batch, populate, embedding, snapshot, reporting, job, and system tools. The domain is broad, but the count still feels excessive relative to the core workflow.
The server covers full CRUD lifecycles for biomes, species, organisms, cluster snapshots, and reports, plus embedding, job, search, and system operations. Minor gaps exist (for example, no direct update/delete for cluster groups, and snapshot immutability is intentional), but the main workflows are well supported.