Polyxd

Polyxd shows interactive screens right in the conversation.

Ask your AI to split a bill, return an order, fill in a form, compare plans or summarise a week of numbers, and instead of a wall of text you get a real interface: fields to fill in, choices to make, a receipt that adds up, a chart with a plain-words summary, and buttons that do what they say. Your AI writes each screen as a small Polyxd document, a JSON description of what the screen means rather than how it looks.

What you can ask

Add Polyxd's renderer, validator and verifier to the codebase you're working in, following the current docs.
Example path

MCP connector

Server URL: https://mcp.polyxd.com/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: Polyxd turns a small JSON document of meaning into a real screen in a design system. You write the document; this server checks it and shows it to the user. Call once before writing your first document, until it is valid, then . For questions about Polyxd itself (installing a renderer, the verifier, the runtime, Studio, anything in the docs), call and cite the URLs it returns rather than answering from memory. Actions the user takes in a shown screen come back to you as chat messages. A button press only tells you what the user chose: it submits, pays or saves nothing, so never say it did.

Tools

Reads data7

Skills

None in the store listings or on the server

What you can ask

Add Polyxd's renderer, validator and verifier to the codebase you're working in, following the current docs.

Example path

MCP connector

Server URL

https://mcp.polyxd.com/mcp

None

Protocol

MCP 2026-07-28

Instructions

Polyxd turns a small JSON document of meaning into a real screen in a design system. You write the document; this server checks it and shows it to the user. Call once before writing your first document, until it is valid, then . For questions about Polyxd itself (installing a renderer, the verifier, the runtime, Studio, anything in the docs), call and cite the URLs it returns rather than answering from memory. Actions the user takes in a shown screen come back to you as chat messages. A button press only tells you what the user chose: it submits, pays or saves nothing, so never say it did.