daisyUI Blueprint MCP

What: a licensed MCP server that gates daisyUI work behind a chain of specialist personas. Who: any agent writing or revising daisyUI markup in frontend/ or games/*. When: before writing component markup — not after.

Blueprint is not a snippet lookup. You choose the workflowId and pass the same string to every tool in the task; the server keys all accumulated state off it. Two orderings are enforced server-side and rejected with blueprint_error (see Enforced ordering). Treat it as a workflow you enter, not a reference you query.

Everything on this page was observed against daisyui-blueprint@1.5.6. initialize reports serverInfo {"name":"daisyui-blueprint","version":"1.5.6","title":"daisyUI Blueprint"} and capabilities resources, tools, prompts, completions.

Configuration

The server is registered twice, and the two registrations use different syntax for the same deny.

.mcp.json — tracked, project-scoped

{
  "mcpServers": {
    "daisyui-blueprint": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "daisyui-blueprint@latest"],
      "env": {
        "EMAIL": "${DAISYUI_BLUEPRINT_EMAIL}",
        "LICENSE": "${DAISYUI_BLUEPRINT_LICENSE}"
      }
    }
  }
}

The two variables interpolate from the env block in .claude/settings.local.json, which is gitignored globally (~/.config/git/ignore). The license key must never land in .mcp.json — that file is tracked. Without both variables the server exits immediately with 🔑 License validation failed: Env variables missing.

The Figma converter is denied here with the fully-prefixed permission literal:

"permissions": { "deny": ["mcp__daisyui-blueprint__convert_figma_to_daisyui"] }

~/.omp/mcp.json — untracked home config

The same server is registered for omp under mcpServers["daisyui-blueprint"]. Two differences matter:

1. It denies tools through disabledTools, which matches on the bare tool name with no mcp__<server>__ prefix: "disabledTools": ["convert_figma_to_daisyui"]. Using the prefixed literal here silently disables nothing.
2. It carries literal EMAIL and LICENSE values rather than interpolating them.

Standing risk

~/.omp/mcp.json stores the Blueprint credentials in plaintext outside the repository. It is not committed, so the key never reaches version control, but any process that can read the home directory can read the license. Rotating or externalising that credential is a separate security decision and is deliberately not bundled with Blueprint documentation changes. Never paste the license value into a report, diff, log, doc, or commit message.

Both files are plain JSON with no comment support. A syntax error in either one silently disables every MCP server for that client, so validate them after editing.

MCP servers bind at session start, so a session that predates a config change will not see the tools. Restart the client, or speak stdio JSON-RPC to the server directly to verify a change without waiting for a restart.

The persona chain

Argument names below are copied from the live inputSchema; the casing is exact.

Enforced ordering

Observed by calling tools out of order against a fresh server process:

So the enforced graph is: setup_expert → rules_enforcer → {creative_director, page_architect, component_syntax_expert}, with quality_inspector depending only on setup_expert. Nothing forces creative director before page architect.

trend must be the whole enum string

daisyui_creative_director rejects a bare trend label. The enum values embed their own guidance, and the argument must match one verbatim:

"Data-Dense Utilitarian UI - Good for Developer tools, operations software, analytics, trading,
logistics, and internal enterprise systems."

Passing just "Data-Dense Utilitarian UI" returns MCP error -32602: Input validation error: Invalid option: expected one of ….

workflowId scope

One agent, one cohesive task, one design direction. Reuse it across sections of the same page or related pages sharing a design. Mint a new one for a different design direction or an alternative variant. Never reuse another parallel agent’s workflowId — the page architect response states explicitly that “Every parallel agent must use a distinct workflowId”, and setup expert stores projectRoot against it.

State is held per server process. A fresh npx daisyui-blueprint process knows no prior workflowId, so a whole chain must run inside one connection.

Snippet IDs

75 total: 68 components/* (components/button, components/card, components/modal, components/timeline, components/theme-controller, …) plus 7 blocks/* (blocks/bento-grid, blocks/features-section, blocks/hero-section, blocks/logo-marquee, blocks/product-feature, blocks/social-proof-section, blocks/testimonial-wall).

Responses are batched against MAX_COMPONENT_RESPONSE_CHARS and MAX_COMPONENT_SKIPS. When a response reports remaining IDs, re-call with the same workflowId and only the remaining IDs until none remain.

Audit intent

• fix_changes — after this workflow edited UI code. Findings may be fixed only within the changed scope, then the audit reruns.
• report_only — for an explicitly requested read-only audit. Findings are reported and project files must not be edited.

The inspector returns one action to follow: fix and rerun, perform rendered checks and rerun once, report, stop, or finalize. Its report arrives as JSON in the tool result — no MCP resource read required. It does not replace diff, build, test, or browser verification.

Under the hood

Tool surface (tools/list)

Eleven tools: the six daisyui_* personas above plus five converters — convert_figma_to_daisyui, convert_bootstrap_to_daisyui, convert_picture_to_theme, convert_screenshot_to_daisyui, convert_tailwind_to_daisyui.

Prompt surface (prompts/list)

Four prompts, distinct from the tools and named in prose rather than snake_case: Bootstrap to daisyUI, Picture to Theme, Screenshot to daisyUI, Tailwind to daisyUI. There is no Figma prompt — the Figma path is tool-only.

Resources

resources/list is empty. All resources are templated; resources/templates/list returns four URI schemes:

Environment knobs

Other observed defaults: maxPages 5, figmaTimeoutMs 15000.

Error codes

workflow.setup-expert-missing, workflow.rules-enforcer-missing, workflow.page-components-not-retrieved, workflow.page-components-not-used, audit.unclassified-sources, audit.unsupported-target-skipped, and the generic blueprint_error. Ordering violations surface as blueprint_error with retryable: true.

Converters

The four non-Figma converters bypass the chain entirely — they skip every optional tool and the Quality Inspector. The server describes them as a fallback for when MCP prompts are unavailable and the user explicitly asks for that workflow. They are not a shortcut around Law 19: if you are writing Funday markup, run the chain.

convert_figma_to_daisyui is denied repo-wide. Funday has no Figma source of truth, so a Figma-derived design cannot be reconciled against any Funday standard. The deny is expressed twice, with the different literals documented in Configuration: the prefixed mcp__daisyui-blueprint__convert_figma_to_daisyui in .claude/settings.local.json, and the bare convert_figma_to_daisyui in ~/.omp/mcp.json. Neither .cursor/mcp.json nor .vscode/mcp.json exists in this repository.

Showcase runbook

A full read-only chain, all six personas, one workflowId, mutating nothing. This is the exact sequence used to verify this page; it must run inside a single server connection.

Rules that are not optional:

• Re-call step 5 with the same workflowId and only the remaining IDs until none remain.
• Follow the single action step 6 returns. If it returns manual_review, perform the rendered checks it names and rerun once with the same files plus renderedReview: { status: "completed", … }. Never edit code as a result of a report_only audit.
• Never call convert_figma_to_daisyui.

Observed result

All six returned successfully. Step 6 returned status: "issues", action: "report", editPolicy: "read_only", summary {filesAudited: 1, issueCount: 3, warningCount: 1} against frontend/src/lib/components/Feedback.svelte, with three finding codes:

• daisyui.unknown-class × 2 — select-bordered (:47) and textarea-bordered (:58). Both were removed in daisyUI 5; the bordered look is now the default for those controls.
• daisyui.color-treatment × 3 — range-primary (:55), badge-primary (:56), btn-primary (:59) judged too dense for one component.
• accessibility.form-control-name × 2 — the select and textarea have no accessible name; a fieldset legend names the group, not the individual control.

Per report_only these were reported and not fixed.

Conflicts with Funday standards

Blueprint governs how markup gets written. It does not override Funday design policy — when Blueprint output conflicts with the Funday standards pages, the standards win and the Blueprint output is corrected.

Checked against daisyUI Masterclass for the showcase run:

Related

• DaisyKit Cheat Sheet — Midway portable kit quick-start
• daisyUI Masterclass — Funday production patterns
• daisyUI SSOT — vendor snapshot from llms.txt
• MCP configuration — transport and config-file precedence