MCP Server

What it gives you

The UI Thing MCP server exposes the library in a way that is useful to agents:

• small discovery indexes for components, blocks, prose, docs, examples, and page templates
• exact detail tools for full source code and markdown docs
• install-plan tools for mixed selections
• scaffold-first planning tools for new Nuxt projects

This matters because UI Thing is a copy-paste library. The files are the product, so the MCP server is designed to help agents find the right files, dependencies, and docs before implementation.

Available resources

These resources are intentionally compact indexes:

• resource://uithing/components
• resource://uithing/blocks
• resource://uithing/prose
• resource://uithing/documentation-pages
• resource://uithing/examples
• resource://uithing/page-templates
• resource://uithing/quick-start
• resource://uithing/design-patterns

Use the detail tools when you need full source or full markdown.

Available tools

Discovery

• list-components
• list-blocks
• list-prose
• list-documentation-pages
• list-block-pages
• search-components
• search-documentation-pages
• resolve-library-item

Details

• get-component
• get-block
• get-prose
• get-documentation-page

Planning

• get-project-setup
• get-install-plan
• plan-page
• plan-form
• validate-dependencies
  Compatibility alias for get-install-plan

Available prompts

• setup-project
• build-page
• create-form
• implement-component
• create-documentation
• fix-component-issue
• optimize-accessibility

Prompts now point to the tools above instead of trying to embed the whole workflow in prompt text.

Recommended workflow

For a new Nuxt project:

1. Call get-project-setup
2. Call plan-page or plan-form
3. Call resolve-library-item if the target names are fuzzy
4. Call get-install-plan
5. Call get-component, get-block, get-prose, or get-documentation-page

Codex

Codex does not read .vscode/mcp.json. Add MCP servers with codex mcp add or by editing ~/.codex/config.toml.

Recommended entries

• nuxtMcpToolkit
  Reference docs server for current Nuxt guidance
• uiThingLocal
  Local development server for authoring and testing
• uiThingHosted
  Hosted production endpoint for end-user flows

CLI setup

codex mcp add nuxtMcpToolkit --url https://mcp-toolkit.nuxt.dev/mcp
codex mcp add uiThingLocal --url http://localhost:3000/mcp
codex mcp add uiThingHosted --url https://uithing.com/mcp

Manual config

Codex Config

[mcp_servers.nuxtMcpToolkit]
url = "https://mcp-toolkit.nuxt.dev/mcp"

[mcp_servers.uiThingLocal]
url = "http://localhost:3000/mcp"

[mcp_servers.uiThingHosted]
url = "https://uithing.com/mcp"

VS Code

If you are using VS Code MCP support, add UI Thing alongside the Nuxt MCP Toolkit docs server:

Vscode Mcp

{
  "servers": {
    "Nuxt MCP Toolkit": {
      "type": "http",
      "url": "https://mcp-toolkit.nuxt.dev/mcp"
    },
    "UI Thing": {
      "type": "http",
      "url": "https://uithing.com/mcp"
    }
  },
  "inputs": []
}

For local development, switch the UI Thing URL to http://localhost:3000/mcp.

Cursor

Cursor Mcp

{
  "mcpServers": {
    "ui-thing": {
      "type": "http",
      "url": "https://uithing.com/mcp"
    }
  }
}

Claude Desktop

Claude Desktop Config

{
  "mcpServers": {
    "ui-thing": {
      "command": "npx",
      "args": ["mcp-remote", "https://uithing.com/mcp"]
    }
  }
}

Windsurf

Codeium Windsurf Mcp Config

{
  "mcpServers": {
    "ui-thing": {
      "type": "http",
      "url": "https://uithing.com/mcp"
    }
  }
}

Example requests

"Set up UI Thing in a new Nuxt app"

"Plan a landing page using UI Thing blocks"

"Build an install plan for button, dialog, and Hero 1"

"Resolve the best UI Thing match for a date picker"

"Fetch the full Button component source and docs"

"Search the documentation for sidebar persistence"