Skip to main content
Glama
RoleModel

Optics MCP Server

by RoleModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Optics MCP Server

No user-submitted related servers found.

    Related Servers

    • weave-design-system-mcp

      avcs06
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.
      9 npm
      MIT

    • web-stylebook-mcp

      seungdori
      A
      license
      A
      quality
      B
      maintenance
      Provides deterministic, read-only design knowledge for AI coding agents to help them choose visual directions, plan UI states, and compose design tokens, all without network access.
      6
      12 npm
      4
      MIT

    • UI Design MCP Server

      lnksoul1
      A
      license
      A
      quality
      B
      maintenance
      Provides comprehensive UI design assistance tools for LLMs, generating color palettes, typography, spacing systems, shadows, design tokens, and more via the MCP protocol.
      28
      MIT

    • AI-Canvas MCP Server

      laoluojuhai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, modify, export, and validate design documents with 47 tools covering design, code generation, branding, and print/mockup workflows.
      1 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes (tokens, components, generation, validation). However, some pairs like check_contrast/validate_color_pair and validate_token_usage/replace_hard_coded_values/suggest_token_migration could cause confusion, though their descriptions clarify differences.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern (e.g., get_token, generate_theme, validate_token_usage). No mixing of styles or irregular names.

    Tool Count5/5

    With 15 tools, the server covers a broad range of design system tasks without being excessive. Each tool serves a clear purpose, fitting well within the ideal 3-15 range.

    Completeness4/5

    The surface covers token management (get, search, usage, migration), components (info, list, scaffolding), theme/sticker generation, and validation. Minor gaps exist (no token creation/update, no component deletion) but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources