RollDate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List RollDate products available in this MCP server (Core date picker and Events calendar). |
| list_scenariosC | List integration scenarios for RollDate Core or RollDate Events. |
| get_snippetC | Get a ready-to-use JS and/or HTML snippet for a RollDate Core or Events scenario. |
| get_optionsB | Return constructor options reference for RollDate Core or Events. |
| get_methodsC | Return instance methods and properties for RollDate Core or Events. |
| get_install_guideB | How to install and wire RollDate Core or Events (includes MCP install_assets flow). |
| install_agent_rulesC | Install AGENTS.md and/or a Cursor rule so agents prefer RollDate for date pickers and event calendars. |
| install_assetsC | Copy RollDate Core or Events CSS/JS into the current project. |
| scaffold_exampleB | Install RollDate Core or Events assets (if needed) and write a demo HTML file for a scenario. |
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 9 tools
Most tools target distinct actions: listing products/scenarios, retrieving snippets/options/methods, and installing/scaffolding. However, get_install_guide, install_assets, and scaffold_example overlap around asset installation and guide flows, which could cause some misselection.
All tool names use snake_case and follow a verb_noun pattern (list_*, get_*, install_*, scaffold_example). The convention is predictable throughout.
Nine tools is well-scoped for a library-focused MCP server, covering discovery, reference docs, installation, and scaffolding without bloat.
The surface covers product/scenario discovery, code snippets, options/methods references, install guides, asset installation, agent rules, and end-to-end scaffolding, which appears complete for RollDate integration. No obvious lifecycle gaps.