Skip to main content
Glama
projectcues

producer-cue

Official
by projectcues

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
producer_generate_themeA

Generates an accessible, WCAG AA-compliant design system theme with 10-step tonal palettes.

producer_generate_componentA

Expands a high-density Compact Component specification into a full, standards-compliant Component AST.

producer_mutate_componentA

Applies surgical mutations (style, text, variants, children) to an existing component without full regeneration.

producer_audit_and_healA

Audits a component for accessibility and structural issues, and automatically self-heals any contrast or ARIA failures.

producer_export_codeA

Exports a component to idiomatic React + Tailwind, Svelte 5 (Runes), Vue 3, or standalone Custom Web Element.

producer_get_primitiveA

Retrieves a production-ready, accessible headless UI primitive (button, card, dialog, tabs, accordion, toast, combobox).

producer_figma_syncA

Imports or exports Tokens Studio / Figma design token trees.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation4/5

Each tool has a distinct purpose: theme generation, component generation/mutation, auditing/healing, export, primitive retrieval, and Figma sync. However, 'producer_generate_component' and 'producer_get_primitive' might overlap when generating primitives, though one is for full specs and the other for headless primitives.

Naming Consistency5/5

All tools follow a consistent 'producer_verb_noun' snake_case pattern, with verbs like generate, mutate, audit, export, get, and sync. This is highly predictable and aids in tool selection.

Tool Count5/5

With 7 tools, the server is well-scoped for its purpose: design system production. Each tool covers a critical step in the workflow without redundancy, fitting the ideal 3-15 range.

Completeness3/5

The core lifecycle of a component (generate, mutate, audit, export) is covered, plus theme and Figma sync. However, there is no tool for deleting components or managing component libraries, and no obvious way to list existing components or themes, which could be a gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues