CEDAR MCP Serverofficial
A
licenseA
qualityA
maintenanceEnables interaction with the CEDAR metadata repository, including fetching templates, searching BioPortal ontology terms, and managing template instances.
8
MIT
CEDAR MCP Server
Related Servers
Alternatives to CEDAR MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables LLMs and AI agents to search a biomedical knowledge graph for concepts and study variables, traverse semantic relationships, and look up BioData Catalyst PIC-SURE paths for cohort building.-
- AlicenseBqualityBmaintenanceEnables biomedical research workflows via MCP, including experiment and document search, PDF text extraction, evidence retrieval, and validation with provenance tracking.10MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and AI agents to query a biomedical knowledge graph stored in RedisGraph, with tools for concept search, synonym enrichment, and study variable discovery through semantic relationships.-
- FlicenseAqualityDmaintenanceEnables interaction with synthetic NIH-style clinical research data through tools for searching publications, querying patient metadata, analyzing AAA measurements, and retrieving protocol guidance.5-
- AlicenseAqualityDmaintenanceEnables interaction with REDCap instances for managing research data, projects, and files through natural language.383,280 PyPI1MIT
TDQS
A3.6/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: get_instances_based_on_template retrieves paginated instances of a template, while get_template fetches the template itself. There is no overlap in functionality, and an agent can easily differentiate between them based on their descriptions and intended use cases.
Naming Consistency5/5
Both tools follow a consistent verb_noun naming pattern: get_instances_based_on_template and get_template. They use snake_case uniformly, and the verb 'get' is applied consistently to indicate retrieval operations, making the naming predictable and easy to understand.
Tool Count2/5
With only 2 tools, this server feels too thin for its apparent domain of interacting with a CEDAR repository. While the tools cover template and instance retrieval, there are likely missing operations such as creating, updating, or deleting templates/instances, which limits the server's utility and scope.
Completeness2/5
The server is severely incomplete for a CEDAR repository interface. It only provides read operations (get_template and get_instances_based_on_template) with no support for create, update, delete, or other essential actions like searching or managing metadata. This leaves significant gaps that will hinder agent workflows and limit functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues