Design System MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPO | No | Your repository name (e.g., 'aurora') | |
| GITHUB_OWNER | No | Your GitHub username or the repository owner (e.g., 'appian-design') | |
| GITHUB_TOKEN | No | Your GitHub personal access token (generate at https://github.com/settings/tokens) | |
| INTERNAL_DOCS_TOKEN | No | GitHub token for internal repository (must have access to private repo) | |
| ENABLE_INTERNAL_DOCS | No | Enable internal documentation access (set to 'true') | |
| INTERNAL_GITHUB_REPO | No | Optional: Internal repository name (defaults to design-system-docs-internal) | |
| INTERNAL_GITHUB_OWNER | No | Optional: Internal repository owner (defaults to GITHUB_OWNER) |
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-content-sourcesA | Get information about available documentation sources and their status |
| refresh-sourcesA | Trigger manual refresh of documentation sources |
| list-categoriesA | List all design system categories |
| list-componentsB | List components in a specific category with source information |
| get-component-detailsC | Get detailed information about a specific component with source attribution |
| search-design-systemA | Search for components, layouts, or patterns by keyword with source filtering |
| get-sail-guidanceB | Get SAIL coding guidance and best practices |
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 7 tools
Each tool targets a distinct operation: component details, source info, guidance, categories, component listing, source refresh, and search. No two tools overlap in purpose.
All tools follow a verb_noun pattern, but the verbs vary (get, list, refresh, search) without a strict convention. Minor deviation from full consistency.
7 tools is well-scoped for a design system reference server. Each tool serves a clear purpose without bloat or deficiency.
Covers browsing, searching, and source management. Minor gaps: no tool for design tokens or component variants, but core functionality is present.