14 tools from the Optics MCP Server, categorised by risk level.
View the Optics policy →check_contrast Check WCAG contrast ratio between two color tokens get_component_info Get detailed information about a component including its design token dependencies get_component_tokens Get all design tokens used by a specific component get_token Get detailed information about a specific design token by name get_token_usage_stats Get statistics about design token usage across the system list_components List all available components in the design system search_documentation Search through Optics documentation 2/5 search_tokens Search for design tokens by category or name pattern suggest_token_migration Suggest design tokens for a hard-coded value validate_token_usage Validate code for hard-coded values that should use design tokens 2/5 generate_component_scaffold Generate a React component scaffold with proper token usage 2/5 generate_sticker_sheet Generate a visual style guide with color swatches and component examples 2/5 generate_theme Generate a custom Optics theme with CSS variable overrides. Includes installation instructions for @rolemodel/optics via npm or CDN (jsDelivr/unpkg... 2/5 replace_hard_coded_values Replace hard-coded values with design tokens 3/5 The Optics MCP server exposes 14 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Optics server.
Optics tools are categorised as Read (10), Write (4). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept