Skip to main content
Glama
N-Link-Lab

design-tokens-mcp

by N-Link-Lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to design-tokens-mcp

No user-submitted related servers found.

    Related Servers

    • ds-canon

      jtrainer357
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server that exposes a design system's tokens, components, conventions, and deprecations as queryable tools, enabling agents to look up canonical values, assess change impact, and detect hardcoded value drift.
      8
      1 npm
      MIT

    • eds-mcp-server

      Edwson
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to access design system tokens and component contracts through MCP, reducing token usage and ensuring consistency.
      29
      MIT

    • ds-pilot

      lyse-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.
      5 npm
      9
      MIT

    • Sekura Design MCP

      mictsi
      A
      license
      A
      quality
      A
      maintenance
      Serves the complete Sekura Design System—tokens, components, layouts, UX patterns, accessibility contract, and paste-ready code—to MCP-capable tools, enabling agents to build accessible, dark-mode-first interfaces with verified values.
      19
      MIT

    • ai-ready-ds-auditor

      TJaraC
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI IDEs to query Figma design tokens, component specs, and audit issues via MCP tools, without cloud subscriptions.
      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

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing, getting, setting, exporting, and drift-checking. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent 'tokens_verb' pattern with snake_case, making the set predictable.

    Tool Count5/5

    5 tools is well-scoped for a design token server; each tool covers a core operation without redundancy.

    Completeness4/5

    The set covers CRUD except deletion, and includes export and drift detection. A delete token tool is missing, but the surface is otherwise complete for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources