cds-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CERN_CLIENT_ID | No | Your CERN OAuth client ID for authentication | |
| CERN_CLIENT_SECRET | No | Your CERN OAuth client secret for authentication |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cds_documentsA | Search CDS documents with various filters including experiment, document type, and date range |
| get_cds_document_detailsA | Get detailed information about a specific CDS document including full abstract, authors, and metadata |
| get_cds_document_filesB | Get file information and download URLs for a specific CDS document |
| get_cds_experimentsA | Get a list of common CERN experiments that can be used for filtering searches |
| list_cds_collectionsA | Browse the hierarchical taxonomy of CERN Document Server (CDS) collections and sub-collections. Use this tool BEFORE searching if you are unsure which collection or category to search in. It returns the exact search keys that can be passed into the |
| get_cds_document_typesA | Get a list of common CDS document types that can be used for filtering searches |
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 6 tools
Each tool has a distinct purpose: details, files, filter lists (types and experiments), collection browsing, and searching. No overlap exists.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_cds_document_details, search_cds_documents), making them predictable.
With 6 tools, the set is well-scoped for a read-only document server API, covering search, retrieval, and exploration without excess.
The tool surface covers core operations: searching with filters, retrieving details and files, browsing taxonomy, and accessing filter options. No obvious gaps for the stated domain.