Design Checklists MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHECKLIST_DESIGN_DATA_PATH | No | Changes the local cache location for the Checklist.design content. |
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 |
|---|---|
| get_catalog_summaryA | Return source, attribution, refresh time, total checklist and entry counts, and counts by category. |
| list_checklistsA | Browse checklist summaries. Optionally filter by category and exact text phrase. Use search_checklists for relevance-ranked discovery. |
| search_checklistsA | Search checklist names, descriptions, categories, items, suggestions, and flow steps. Results are ranked locally and include matching entry excerpts. |
| get_checklistA | Return one complete checklist, including every item, suggestion, step, image URL, related checklist, collection, and attribution. Prefer a qualified identifier such as mobile/checkout. |
| build_review_checklistA | Select the most relevant Checklist.design checklists for a described screen, component, product area, or flow and return every entry from each selected checklist. Selection is deterministic local keyword relevance, not an AI design review. |
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 5 tools
Each tool has a clearly distinct purpose: building a review checklist, retrieving catalog summary, browsing checklists, searching, and fetching a single checklist. The descriptions explicitly differentiate list vs search and build vs get, eliminating ambiguity.
All tool names follow the same verb_noun pattern (build, get, list, search, get) with consistent formatting. The pattern is predictable and intuitive.
Five tools is well-scoped for a checklist catalog server. Each tool provides a necessary function without redundancy, and the count is neither too thin nor overwhelming.
The tool set covers the full lifecycle of interacting with design checklists: browse, search, retrieve a single checklist, build a custom review, and access metadata. No obvious gaps exist for the stated domain.