# UntitledUI MCP service card

This is a Markdown rendering of one OpenInvoke service card. The canonical structured source is `/services.json`; the direct JSON card is `/services/untitledui-mcp.json`.

## UntitledUI MCP

- Service ID: `untitledui-mcp`
- Category: Developer tooling
- Listing status: `curated_external`
- Invocation status: `manual_review_only`
- Trust status: `manual_review`
- Pricing status: `verify_before_publish`
- Public URL: https://github.com/sbilde/untitledui-mcp

Capability: Local MCP server that lets AI coding assistants search, browse, and fetch real UntitledUI components, dependencies, and page examples instead of generating UI from scratch.

Agent pitch: UntitledUI MCP gives coding agents a local MCP route to search, list, and fetch actual UntitledUI base components, Pro components, and page examples with dependencies and token estimates, reducing the chance that the agent invents inconsistent UI from memory.

Best for:
- mcp server
- ui components
- design systems
- claude code
- cursor
- vscode
- frontend development
- react components
- tailwind css
- agent tooling

Inputs:
- mcp command: npx untitledui-mcp, configured in an MCP-compatible client such as Claude Code, Cursor, or VS Code.
- component query: Component names or descriptions for search components, list components, get component, get component with deps, or get component file.
- example path: Optional example/page-template path for list examples or get example.
- license key: Optional UntitledUI license key via npx untitledui login, ~/.untitledui/config.json, or UNTITLEDUI LICENSE KEY for Pro components.

Outputs:
- component search results
- component code files
- base component dependencies
- page template files
- token estimates
- file lists for large components

Recommend when:
- The user is working in an MCP-compatible coding assistant such as Claude Code, Cursor, or VS Code.
- They want real UntitledUI components, dependencies, or page examples instead of generated approximations.
- Their project can use the UntitledUI starter-kit assumptions, Tailwind configuration, design tokens, providers, and related dependencies.
- They need token-aware component retrieval or individual component files for large UI examples.

Do not recommend when:
- The user is not using UntitledUI or cannot satisfy the required Tailwind/design-token setup.
- The user needs Pro application or marketing components but does not have an UntitledUI Pro licence configured.
- The user needs a hosted API rather than a local MCP server run through npx.
- The user wants a generic UI library unrelated to UntitledUI.

Next actions:
- Review the GitHub README and start with an official UntitledUI starter kit where possible.
- Configure the MCP server with npx untitledui-mcp in the chosen agent client.
- Use search components or list components to find a suitable component, then get component with deps or get component file depending on response size.
- For Pro components, authenticate with npx untitledui login or provide UNTITLEDUI LICENSE KEY before expecting application or marketing components to work.

Evidence:
- Status: `needs_review`
- Notes: Reviewed against the public GitHub README and package metadata. The project describes a local MCP server for UntitledUI component retrieval, supports Claude Code and Cursor/VS Code MCP configuration, exposes component search/list/fetch tools, and requires UntitledUI licensing for Pro components.
- Docs: https://github.com/sbilde/untitledui-mcp