CEDAR MCP Server
OfficialRelated Servers
Alternatives to CEDAR MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables interaction with the CEDAR (Center for Expanded Data Annotation and Retrieval) metadata repository to fetch templates and retrieve template instances. Supports querying structured metadata and biomedical data annotations through the CEDAR platform.2MIT
- AlicenseBqualityBmaintenanceEnables biomedical research workflows via MCP, including experiment and document search, PDF text extraction, evidence retrieval, and validation with provenance tracking.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables searching a synthetic healthcare document repository and saving validated document metadata through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables researchers to query DigitalBrain data catalogs, brain region profiles, gene expression summaries, and paper evidence, and download approved results through MCP-compatible clients.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to search and query a team knowledge graph, retrieve document context, upload files for indexing, explore entities and connections, and monitor workspace usage and server health.MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to search a Zotero library, read items, take notes, organize collections, and perform semantic search over PDFs.8MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: template retrieval, instance retrieval, branch-scoped term search, ontology-wide term search, branch children, class tree, stale cache cleanup, and full cache clear. The descriptions explicitly delineate scope, minimizing confusion.
Naming mixes conventions: 'get_*' verbs (get_cedar_template, get_instances_based_on_template, get_branch_children, get_ontology_class_tree) coexist with 'term_search_*' noun-first patterns and imperative cache tools ('remove_*', 'clear_*'). The inconsistency is moderate and could confuse agents.
Eight tools is well-scoped for this server's purpose: template access, instance retrieval, ontology exploration, and cache management. Each tool earns its place without redundancy or bloat.
The surface covers core workflows: fetching templates, listing instances, and discovering ontology terms. Minor gaps include lack of template search/list and direct instance-by-ID lookup, but these are likely outside the intended scope.