cdisc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDISC_API_KEY | Yes | A CDISC Library personal API key. Obtain one at https://library.cdisc.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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List all available CDISC standards and their published versions. Use this first to discover available versions before querying specific content. |
| search_cdiscB | Search across all CDISC standards by keyword. Args: query: Search keyword, e.g. "adverse event", "AEDECOD", "demographics" |
| get_sdtm_domainsA | List all SDTM domains for a given version. Args: version: SDTM-IG version, e.g. "3.4", "3.3". Use list_products() first. |
| get_sdtm_domain_variablesB | Get all variables defined in an SDTM domain. Args: version: SDTM-IG version, e.g. "3.4" domain: Two-letter domain code, e.g. "DM", "AE", "LB" |
| get_sdtm_variableB | Get the full definition of a specific SDTM variable. Args: version: SDTM-IG version, e.g. "3.4" domain: Domain code, e.g. "AE" variable: Variable name, e.g. "AETERM", "AEDECOD" |
| get_adam_datastructuresB | List all ADaM data structures for a given version. Args: version: ADaM version, e.g. "1.3", "2.1" |
| get_adam_variableB | Get the definition of a specific ADaM variable. Args: version: ADaM version, e.g. "1.3" data_structure: Data structure name, e.g. "ADSL", "ADAE" variable: Variable name, e.g. "USUBJID", "AVAL" |
| get_cdash_domainsB | List all CDASH domains for a given version. Args: version: CDASH version, e.g. "2.0", "1.1" |
| get_cdash_domain_fieldsB | Get all data collection fields for a CDASH domain. Args: version: CDASH version, e.g. "2.0" domain: Domain code, e.g. "DM", "AE", "VS" |
| list_ct_packagesA | List all available CDISC Controlled Terminology packages with release dates. |
| get_codelistA | Get a specific Controlled Terminology codelist definition. Args: package_id: CT package identifier, e.g. "sdtmct-2024-03-29" codelist_id: Codelist concept ID or submission value, e.g. "C66781", "AGEU" |
| get_codelist_termsB | List all valid terms in a CT codelist (max 100 shown, check has_more). Args: package_id: CT package identifier codelist_id: Codelist concept ID or submission value |
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 12 tools
Each tool has a clearly distinct purpose targeting specific CDISC standards (ADaM, CDASH, SDTM, Controlled Terminology) with no overlap. The tools are organized by standard type and operation level (list domains vs. get specific variables), making them easily distinguishable.
All tools follow a consistent verb_noun pattern with clear prefixes indicating the standard (get_adam_, get_cdash_, get_sdtm_, get_codelist_, list_, search_). The naming is highly predictable and follows the same snake_case convention throughout.
12 tools is well-scoped for a CDISC standards lookup server, covering multiple standards (ADaM, CDASH, SDTM, CT) with appropriate granularity. Each tool serves a specific purpose without redundancy, and the count supports comprehensive querying without being overwhelming.
The toolset provides excellent coverage for querying CDISC standards metadata, with list operations for discovery and get operations for detailed information. Minor gaps exist (e.g., no update/create/delete tools, but that's appropriate for a read-only reference server), and the search tool helps bridge any remaining gaps.