CEDAR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CEDAR_API_KEY | Yes | Your CEDAR API key from cedar.metadatacenter.org | |
| BIOPORTAL_API_KEY | Yes | Your BioPortal API key from bioportal.bioontology.org |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_templateB | Get a template from the CEDAR repository. Args: template_id: The template ID or full URL from CEDAR repository (e.g., "https://repo.metadatacenter.org/templates/e019284e-48d1-4494-bc83-ddefd28dfbac") Returns: Template data from CEDAR, cleaned and transformed |
| get_instances_based_on_templateA | Get template instances that belong to the input template ID with pagination support. This tool searches for instances of a given template and fetches their complete content in paginated chunks to avoid token limit issues. Args: template_id: The template ID or full URL from CEDAR repository (e.g., "https://repo.metadatacenter.org/templates/e019284e-48d1-4494-bc83-ddefd28dfbac") limit: Number of instances to return per page (min: 1, max: 100, default: 10) offset: Starting position for pagination (default: 0) Returns: Dictionary containing: - instances: List of template instances for this page - pagination: Pagination metadata (total_count, current_page, etc.) - errors: List of any errors encountered during fetching |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
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.
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.
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.