Polyxd

What the Polyxd MCP server does

The Polyxd MCP server exposes Polyxd's interface-generation workflow to an MCP host's model. Its documented scope includes the Polyxd specification, verification checks, and live screens. UI documents describe semantic components and the data bound to them rather than prescribing pixels, fonts, or colors.

A model or other generator can produce a UI document as spec-valid JSON. Polyxd can then check the document and show the resulting interface through a design-system pack. This is suited to temporary, task-focused screens that an agent or person can use and discard after the task is complete.

How it works

The Polyxd MCP server sits between the host's model and Polyxd's document pipeline. A request is handled by a generator that emits JSON conforming to the Polyxd specification. The document is passed through verification and can be rendered using Polyxd's renderer and a selected pack.

The specification defines semantic components, reusable patterns, an action or capability registry with risk levels, a JSON Schema, and a Design Direction for visual preferences. The renderer maps those semantics to a design system instead of requiring the generator to produce implementation-specific markup or styling.

Verification covers multiple layers. The documented checks include schema, structure, patterns, capabilities, copy, accessibility, contrast, target size, and scripted agent tasks. The renderer also exposes the resulting screen so the host can work with the interface as rendered rather than only inspecting source JSON.

Tools and capabilities

The provided material describes three broad MCP capabilities rather than individual tool names:

• Providing the Polyxd UI specification for document generation.
• Checking documents with Polyxd's verifier.
• Displaying generated documents as live screens through design-system packs.

Polyxd supports renderers based on React and Web Components. The Web Components package documents Vue and Svelte adapters. Available design-system packs include Material 3, IBM Carbon, Ant Design, Fluent 2, shadcn/ui, Bootstrap 5, Mantine, Radix Themes, Shopify Polaris, GitHub Primer, Adobe Spectrum 2, GOV.UK Frontend, and Chakra UI. Custom packs can be built from an application's tokens with the Polyxd tooling.

The broader Polyxd packages also define semantic events such as actions, checkpoints, completion, abandonment, input errors, status changes, and undo. Those events use keys and codes rather than the text entered by a person, but the excerpt does not state that the MCP server itself exposes event collection.

Limitations and notes

The Polyxd MCP server does not include a model. The host must supply a model or another generator capable of producing JSON that follows the Polyxd specification. It also does not replace the application's data source: UI documents are bound to data provided by the application.

The supplied material does not name individual MCP tool identifiers, transport modes, installation commands, required environment variables, or specific client integrations. Those details should be confirmed in the package documentation before configuring a host.

Polyxd's verifier is intended to check documents before display, including accessibility and whether an agent can operate the interface. A verification result is therefore part of the document workflow, not evidence that the server supplies a particular backend, model provider, or application database.