Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"optics": {
"args": [
"/absolute/path/to/optics-mcp/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for the Optics Design System, enabling LLMs to understand and work with design tokens, components, and documentation from https://docs.optics.rolemodel.design.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'optics-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked optics-mcp against OSV.dev.
Click any tool to inspect its schema.
system-overviewSystem overview for understanding Optics design system
optics://system-overview
documentation-introductionIntroduction to Optics documentation
optics://documentation/introduction
documentation-getting-startedGetting started guide
optics://documentation/getting-started
documentation-design-tokensDesign tokens documentation
optics://documentation/design-tokens
documentation-color-systemColor system documentation
optics://documentation/color-system
documentation-spacingSpacing documentation
optics://documentation/spacing
documentation-typographyTypography documentation
optics://documentation/typography
documentation-componentsComponents documentation
optics://documentation/components
documentation-accessibilityAccessibility documentation
optics://documentation/accessibility
tokens-allAll design tokens
optics://tokens/all
tokens-colorColor tokens
optics://tokens/color
tokens-spacingSpacing tokens
optics://tokens/spacing
tokens-typographyTypography tokens
optics://tokens/typography
components-allAll components
optics://components/all
start-hereStarting point for understanding the Optics design system
get-token-referenceReference guide for getting design tokens
component-guideGuide for working with Optics components
theme-customizationWorkflow for customizing themes
migration-guideGuide for migrating to Optics design tokens
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in design
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
A mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation,compaitable with react,svelte 5,vue & React Native
AI image generation and editing with prompt optimization and quality presets. Powered by Nano Banana
MCP Security Weekly
Get CVE alerts and security updates for Optics MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for the Optics Design System, enabling LLMs to understand and work with design tokens, components, and documentation from https://docs.optics.rolemodel.design.
If you're an AI agent, read SYSTEM_OVERVIEW.md FIRST!
Optics uses a sophisticated HSL-based color system that's different from typical design systems. The system overview explains:
--color-primary token (use --op-color-primary-base instead)Key insight: Optics has 500+ color tokens organized as a predictable scale system, not simple name-value pairs.
This MCP server provides 14 tools and resources for working with the Optics design system:
graph TB
subgraph "MCP Client (AI/LLM)"
CLIENT[AI Agent/LLM]
end
subgraph "Optics MCP Server"
SERVER[MCP Server<br/>stdio transport]
subgraph "Resources (13)"
SYSTEM[optics://system-overview]
DOC_INTRO[optics://documentation/introduction]
DOC_START[optics://documentation/getting-started]
DOC_TOKENS[optics://documentation/design-tokens]
DOC_COLOR[optics://documentation/color-system]
DOC_SPACING[optics://documentation/spacing]
DOC_TYPO[optics://documentation/typography]
DOC_COMP[optics://documentation/components]
DOC_A11Y[optics://documentation/accessibility]
TOK_ALL[optics://tokens/all]
TOK_COLOR[optics://tokens/color]
TOK_SPACING[optics://tokens/spacing]
TOK_TYPO[optics://tokens/typography]
COMP_ALL[optics://components/all]
end
subgraph "Core Tools (7)"
T1[get_token]
T2[search_tokens]
T3[get_token_usage_stats]
T4[get_component_info]
T5[list_components]
T6[get_component_tokens]
T7[search_documentation]
end
subgraph "Advanced Tools (7)"
T8[generate_theme]
T9[validate_token_usage]
T10[replace_hard_coded_values]
T11[check_contrast]
T12[suggest_token_migration]
T13[generate_component_scaffold]
T14[generate_sticker_sheet]
end
subgraph "Prompts (5)"
P1[start-here]
P2[get-token-reference]
P3[component-guide]
P4[theme-customization]
P5[migration-guide]
end
subgraph "Data Layer"
TOKENS[83 Design Tokens<br/>HSL colors, spacing,<br/>typography, borders, shadows]
COMPONENTS[24 Components<br/>with token dependencies]
DOCS[Documentation<br/>Guidelines & best practices]
end
end
CLIENT -->|JSON-RPC| SERVER
SERVER --> SYSTEM
SERVER --> DOC_INTRO
SERVER --> DOC_START
SERVER --> DOC_TOKENS
SERVER --> DOC_COLOR
SERVER --> DOC_SPACING
SERVER --> DOC_TYPO
SERVER --> DOC_COMP
SERVER --> DOC_A11Y
SERVER --> TOK_ALL
SERVER --> TOK_COLOR
SERVER --> TOK_SPACING
SERVER --> TOK_TYPO
SERVER --> COMP_ALL
SERVER --> T1
SERVER --> T2
SERVER --> T3
SERVER --> T4
SERVER --> T5
SERVER -->
... [View full README on GitHub](https://github.com/RoleModel/optics-mcp#readme)