Visa Design System MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-design-tokensC | Get design tokens with optional category filtering |
| search-design-tokensC | Search design tokens by name or value |
| get-design-token-detailsC | Get detailed information about a specific design token |
| get-design-token-categoriesB | Get all available design token categories |
| get-componentsC | Get all components with optional filtering |
| get-component-detailsB | Get detailed information about a specific component |
| get-component-examplesC | Get code examples for a specific component |
| search-componentsC | Search components by name, description, or other criteria |
| get-guidelinesC | Get design guidelines with optional category filtering |
| get-guideline-detailsB | Get detailed information about a specific guideline |
| search-guidelinesC | Search guidelines by content, title, or tags |
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 11 tools
Most tools have distinct purposes targeting different resources (components, design tokens, guidelines) and actions (get vs. search). However, get-components and search-components could be slightly confusing as both retrieve components, though search adds filtering capabilities.
All tools follow a consistent verb-noun pattern with hyphens (e.g., get-component-details, search-design-tokens). The naming is uniform across all 11 tools, making them predictable and easy to understand.
With 11 tools, the count is well-scoped for a design system server covering components, design tokens, and guidelines. Each tool serves a clear purpose without redundancy, fitting the domain appropriately.
The toolset provides comprehensive read/search coverage for components, design tokens, and guidelines, including details, examples, and filtering. A minor gap is the lack of write/update tools (e.g., create or modify resources), but this is reasonable for a design system focused on retrieval.