Polyxd MCP란?
다양한 디자인 시스템 팩을 사용하여 AI 클라이언트가 UI 문서를 작성, 검증 및 인터랙티브 화면으로 렌더링할 수 있도록 합니다. 7개 도구를 제공합니다. 예: polyxd_guide, polyxd_validate, polyxd_verify.
프로젝트 README에서 생성된 요약
Polyxd MCP server 정보
Polyxd는 AI 클라이언트가 인터랙티브한 사용자 인터페이스 문서를 생성, 검증 및 렌더링할 수 있도록 지원합니다. material3와 같은 다양한 디자인 시스템 팩을 사용하여 텍스트 기반 사양을 시각적 화면으로 변환합니다. 이 MCP server는 Claude, ChatGPT, Cursor 또는 VS Code와 같은 AI 어시스턴트를 사용하는 개발자가 자연어를 통해 UI 컴포넌트를 구축하고 테스트할 수 있도록 설계되었습니다.
사용자는 npx를 사용하는 로컬 stdio 설정으로 연결하거나, 계정이나 로그인 없이 URL을 통해 호스팅된 원격 서버에 연결할 수 있습니다. 이 서버는 문서 무결성을 확인하는 polyxd_validate, calm-finance와 같은 디자인 방향에 맞춰 감사하는 polyxd_verify, 그리고 최종 인터페이스를 MCP App으로 렌더링하는 polyxd_show를 포함한 전문 도구를 제공합니다. 호스트가 MCP Apps 확장을 지원하는 경우, UI는 샌드박스 iframe에 나타나며 모델은 버튼 클릭과 같은 사용자 상호작용을 새로운 메시지로 수신할 수 있습니다.
활용 사례
- 1UI 문서 구조 검증생성된 UI 문서의 오류를 확인하고 수정을 위한 구체적인 힌트를 받습니다.
- 2사용 가능한 컴포넌트 탐색생성을 가이드하기 위해 사용 가능한 UI 컴포넌트 목록과 정의를 가져옵니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Polyxd MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Polyxd MCP 설치
$ claude mcp add mcp -- npx -y @polyxd/mcpCursor에 Polyxd MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
}VS Code에 Polyxd MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
}VS Code CLI에 Polyxd MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@polyxd/mcp"]}'Claude Desktop에 Polyxd MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
}Codex에 Polyxd MCP 설치
$ codex mcp add mcp -- npx -y @polyxd/mcpCodex config.toml에 Polyxd MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@polyxd/mcp"]
Gemini CLI에 Polyxd MCP 설치
$ gemini mcp add -s user mcp npx -- -y @polyxd/mcpGemini settings.json에 Polyxd MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
}Polyxd MCP 도구 7
README에서 감지됨polyxd_guidepolyxd_validatepolyxd_verifypolyxd_showpolyxd_packspolyxd_componentspolyxd_docs
| polyxd_guide | — | |
| polyxd_validate | — | |
| polyxd_verify | — | |
| polyxd_show | — | |
| polyxd_packs | — | |
| polyxd_components | — | |
| polyxd_docs | — |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능visualfart/polyxd is public and reachablegithub.com/visualfart/polyxd ↗통과
- 패키지가 이 저장소를 소스로 명시@polyxd/mcp names visualfart/polyxd as sourcenpmjs.com/package/@polyxd/mcp ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @polyxd/mcpnpmjs.com/package/@polyxd/mcp/v/0.4.6#provenance ↗통과
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-10github.com/visualfart/polyxd ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @polyxd/mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음9 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음7 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 132 ms통과
README
GitHub에서 보기@polyxd/mcp
An MCP server for Polyxd. The host's model is the generator: the server gives it the spec as instructions, checks the UI documents it writes, and shows them to the user as an MCP App, drawn by the Polyxd renderer in any design-system pack.
npx -y @polyxd/mcp # stdio
Or connect by URL to the hosted server, which needs no account and no sign-in:
https://mcp.polyxd.com/mcp
Connect by URL
- Claude (claude.ai, and Claude Desktop through your account): Customize > Connectors > Add custom connector, paste the URL, No sign-in.
- Claude Code:
claude mcp add --transport http polyxd https://mcp.polyxd.com/mcp - ChatGPT: turn on developer mode (Settings > Security and login), then add it at chatgpt.com/plugins with the URL and no authentication.
- Cursor:
{ "mcpServers": { "polyxd": { "url": "https://mcp.polyxd.com/mcp" } } }in~/.cursor/mcp.json. - VS Code:
{ "servers": { "polyxd": { "type": "http", "url": "https://mcp.polyxd.com/mcp" } } }in.vscode/mcp.json.
Add it to a host over stdio
Claude Desktop (claude_desktop_config.json) and most other MCP clients:
{
"mcpServers": {
"polyxd": { "command": "npx", "args": ["-y", "@polyxd/mcp"] }
}
}
Claude Code:
claude mcp add polyxd -- npx -y @polyxd/mcp
From a clone of this repository: npm install && npm run build -w @polyxd/mcp, then use node <repo>/packages/mcp/dist/bin.js as the command.
Tools
| Tool | What it does | structuredContent |
|---|---|---|
polyxd_guide |
The spec as instructions: how to use these tools, then the generator prompt the demos use (document shape, rules for generated screens, bindings, actions, every component and its props, the patterns). | { specVersion, guide }, the guide being the same text as the content |
polyxd_validate |
Validates a document. Every issue comes with its JSON Pointer, the component it is in, and a hint saying what to change. | { valid, errors, warnings, issues[{ severity, pointer, component?, message, hint? }] } |
polyxd_verify |
The verifier's document checks (staticAudit from @polyxd/verifier/static, so installing the server installs no Playwright), optionally against a Design Direction (an object, or calm-finance / playful-personal) and a capability registry. A compact report. |
{ errors, warnings, findings[{ severity, check, message, hint? }], direction?, rules } |
polyxd_show |
Validates, then returns the document for display. pack picks the design-system pack (default material3), mode picks light or dark (default: the host's theme). Shows nothing when there are errors. |
{ shown: true, document, pack, packName, mode?, specVersion }, or { shown: false, issues } with isError |
polyxd_packs |
The packs: published design systems and original templates. | { default, packs[{ name, displayName, template, package, description }] } |
polyxd_components |
The components with a one-line summary each, or one component's full definition by name. |
{ components[{ name, category, summary, shell }] }, or { component } with the full definition |
polyxd_docs |
Searches the polyxd.com docs bundled into this version: the sections that best match query, one whole page, or the list of pages. |
{ sections[{ page, title, heading, url, text }] }, { page } or { pages[] } |
Every tool is read-only. data can be passed to polyxd_validate, polyxd_verify and polyxd_show separately from the document; it replaces the document's own data.
Every tool declares an outputSchema (JSON Schema 2020-12, in src/output-schemas.ts, each property described for the model), and every successful result carries structuredContent that conforms to it; the SDK checks each one before it is sent. Error results (isError: true) are not held to the schema: polyxd_show's not-shown result still conforms, the others carry text only.
Resources
ui://polyxd/surface.html(text/html;profile=mcp-app): the MCP App.polyxd://examples/<name>.json: the spec's example documents.polyxd://directions/<name>.json: the spec's example Design Directions.
The MCP App
polyxd_show declares _meta.ui.resourceUri: "ui://polyxd/surface.html", per the MCP Apps extension (SEP-1865, 2026-01-26), and ChatGPT's alias openai/outputTemplate. A host that supports MCP Apps reads that resource and renders it in a sandboxed iframe. The page is self-contained: the @polyxd/web renderer, the renderer's stylesheet and every pack's theme, inlined, with no external origins, so the host's default Content Security Policy is enough.
The resource's _meta says so for each host (appResourceMeta()):
ui.csp:{ connectDomains: [], resourceDomains: [] }. The page loads nothing.ui.prefersBorder: true.- ChatGPT's own keys:
openai/widgetCSP(the same empty lists),openai/widgetPrefersBorder,openai/widgetDescription, andopenai/widgetDomain: "https://mcp.polyxd.com", the origin ChatGPT gives the app's sandbox. - No
ui.domain. Claude wants a hash of the connector URL there and ChatGPT wants an origin, and Claude refuses to render an app whoseui.domainis not its own format. The page needs no stable origin, so it sets none, and ChatGPT readsopenai/widgetDomaininstead.
The page speaks the MCP Apps protocol over postMessage: ui/initialize, then ui/notifications/initialized. It renders the document from the ui/notifications/tool-result notification's structuredContent, in the chosen pack, light or dark from the host's theme unless mode was given. It reports its height with ui/notifications/size-changed.
When the user presses an action, the page sends ui/message with a user message naming the action, the button's label and the action's context (the values bound into it, including what the user typed):
[Polyxd] In the "New task" screen I pressed "Add task" (action task.save).
Context: {"title":"Buy milk","due":"2026-10-01"}
The model receives that as the user's next message and acts on it. Closing the screen (ui.dismiss) arrives the same way. A host without MCP Apps support gets polyxd_show's text summary instead.
The prompt
The generator prompt comes from @polyxd/runtime, which builds it from the spec. src/packs.generated.ts lists the packs, and src/spec-files.generated.ts imports the spec's component definitions and examples as JSON modules, so the server reads no files. npm run sync -w @polyxd/mcp rewrites both, and the tests fail if either is out of date.
Over HTTP
@polyxd/mcp/http serves the same server over MCP's Streamable HTTP transport, as a web-standard (Request) => Promise<Response> handler. It uses nothing from Node, so it runs in a Cloudflare Worker, Deno or Bun.
import { createHttpHandler, rateLimiter } from "@polyxd/mcp/http";
import viewHtml from "@polyxd/mcp/view.html"; // bundled as text
const mcp = createHttpHandler({ viewHtml: () => viewHtml, rateLimit: rateLimiter({ limit: 600, windowMs: 60_000 }) });
export default { fetch: (request: Request) => (new URL(request.url).pathname === "/mcp" ? mcp(request) : new Response(null, { status: 404 })) };
The transport is the SDK's createMcpHandler, stateless: a fresh server per request, no sessions. For 2025-era clients GET and DELETE answer 405, as the spec asks of a server with no standalone stream and no sessions. Clients on the 2026-07-28 protocol, which send the version with every request, work too. Around it:
- Body limit:
maxBodyBytes, default 1 MiB, answered 413. It is checked onContent-Lengthfirst and again as the body is read. - Timeout:
timeoutMs, default 15 seconds, for the whole answer. Late answers get a JSON-RPC error: a 504, or on an SSE stream an error for the request's id. - Rate limit:
rateLimit(request)returns false for 429 withRetry-After.rateLimiter()is a fixed window in memory, keyed onCF-Connecting-IP. It counts per process or per Worker isolate, so it is best effort. - CORS: any origin, since the server holds no credentials and no one's data. Preflights allow the headers they ask for, and responses expose
Mcp-Session-IdandMcp-Protocol-Version. - Logs: one line per request with the method, path, status and duration. Nothing else: not a body, a header, a query string, an address or an error message.
The hosted server
https://mcp.polyxd.com/mcp is apps/mcp, a Cloudflare Worker: /mcp is the handler above, /health answers JSON, and / redirects to the docs. The view is bundled into the Worker as text (about 2.4 MB in all, 385 KB gzipped). Its rate limit is Cloudflare's rate limiting binding, 600 requests a minute per IP address. That binding counts per Cloudflare location, so it guards against floods rather than enforcing an exact quota. Claude and ChatGPT call from their own servers, which is why the limit is generous. Cloudflare's invocation logs, traces and Issues are off in wrangler.jsonc, so the Worker's own lines are all that is kept. With a POSTHOG_KEY secret set, the hosted Worker also counts initializes and tool calls anonymously (apps/mcp/src/analytics.ts): names and counts only, never a document, its data or an address. This package, and npx @polyxd/mcp, send nothing anywhere.
npm run dev -w @polyxd/mcp-remote # wrangler dev on http://127.0.0.1:8787/mcp
node apps/mcp/scripts/smoke.ts http://127.0.0.1:8787/mcp # every tool, in both protocol eras, over real HTTP
npm run deploy -w @polyxd/mcp-remote # builds @polyxd/mcp, then wrangler deploy
Deploying creates the mcp.polyxd.com custom domain on the polyxd.com zone. workers.dev and preview URLs are off.
MCP Registry
server.json describes the hosted server for the MCP Registry as com.polyxd/mcp. A name under com.polyxd needs proof that you control polyxd.com:
openssl genpkey -algorithm Ed25519 -out key.pem
echo "polyxd.com. IN TXT \"v=MCPv1; k=ed25519; p=$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)\""
mcp-publisher login dns --domain polyxd.com --private-key "$(openssl pkey -in key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"
mcp-publisher publish # from packages/mcp
This needs OpenSSL 3 (macOS's LibreSSL has no Ed25519). Keep key.pem private and out of the repository. The TXT record goes on the apex, polyxd.com. HTTP proof works instead: serve the same v=MCPv1; k=ed25519; p=... line at https://polyxd.com/.well-known/mcp-registry-auth and use mcp-publisher login http. It has to be polyxd.com, not mcp.polyxd.com, whose proof would only cover names under com.polyxd.mcp.
The release workflow publishes server.json to the registry on each version tag, once npm has the version, signing in with the private key in the MCP_REGISTRY_KEY Actions secret (the hex string the --private-key command above prints). Without the secret, or when the registry already has the version, the step is skipped with a notice.
server.json lists both the hosted server (remotes) and the npm package (packages), so hosts can offer either. The registry checks the package's mcpName in package.json. Keep both version fields in server.json in step with package.json; a test checks it.
Build and test
npm run build -w @polyxd/mcp # tsc, then scripts/build-view.ts writes dist/view.html
npm test -w @polyxd/mcp
npm test -w @polyxd/mcp-remote # the Worker's routes
The tests connect a client to the server in memory and call every tool on every spec example and on broken documents; start the built bin and speak JSON-RPC to it over stdio; serve it over Streamable HTTP to the SDK client in both protocol eras, and send the raw requests a client library never would (bad JSON, oversize bodies, too many requests, preflights, slow answers); bundle the HTTP entry for a Worker and check it needs nothing from Node; and load the MCP App in headless Chromium with the test playing the host, from the handshake to an action arriving as ui/message. The browser tests skip when Playwright has no Chromium (npx playwright install chromium).
Polyxd MCP 질문
Polyxd MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add mcp -- npx -y @polyxd/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Polyxd MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Polyxd MCP는 어떤 도구를 제공하나요?
7개 도구를 제공합니다. 예: polyxd_guide, polyxd_validate, polyxd_verify, polyxd_show, polyxd_packs.
URL을 통해 Polyxd 서버에 어떻게 연결하나요?
Claude의 커스텀 커넥터에 URL을 붙여넣거나, Claude Code CLI를 사용하거나, Cursor 또는 VS Code의 설정 파일에 추가하여 연결할 수 있습니다.
서버 사용을 위해 계정이나 로그인이 필요한가요?
아니요, 호스팅된 서버는 사용을 위해 계정이나 로그인이 필요하지 않습니다.
UI 문서에 오류가 있으면 어떻게 되나요?
오류가 있는 경우 polyxd_show 도구가 문서를 표시하지 않습니다.