Home Catalog Nuxt UI

Nuxt UI

Developer tools Listed by MCPBay

Nuxt UI components, props, examples and templates for an assistant that builds interfaces

By: Nuxt

The MCPBay team added this server to the catalog. Its author is not affiliated with MCPBay and did not submit it here. The server runs on the author's side, so MCPBay has no call statistics for it.
Connect

The connection URL lives in your cabinet. Use "Add" above, then open "My MCPs" — the address for your AI client appears there.

About

The official Nuxt UI MCP server gives an assistant structured knowledge of the Nuxt UI component library, so it uses real components and props instead of inventing them.

Tools (12):
- search-components, get-component, get-component-metadata — find a component and read its props, slots, events and usage.
- search-composables — find Nuxt UI composables.
- search-documentation, get-documentation-page — search and read the docs.
- list-examples, get-example — browse and read ready-made usage examples.
- list-templates, get-template — starter templates (dashboard, SaaS, landing, docs and others).
- get-migration-guide — upgrade guides between major versions.
- search-icons — search the icon sets available to Nuxt UI.

Typical use: "Build a settings page with a sidebar, tabs and a form using Nuxt UI" — the assistant checks the real components and examples before writing code.

Who it is for: Vue and Nuxt developers using Nuxt UI.

Notes: free, no account needed. Maintained by the Nuxt team.

Tools (12)

  • Get Component

    Retrieves Nuxt UI component documentation and details. Use the `sections` parameter to fetch only specific parts of the documentation to reduce response size. Use `get-component-metadata` instead when you only need structured props, slots and events.

  • Get Component Metadata

    Retrieves metadata for a Nuxt UI component including props, slots, and events. Props are compact by default, pass `full: true` to get the raw recursive prop schemas (very large). Use this over `get-component` when you need structured props, slots and events rather than prose documentation.

  • Get Documentation Page

    Returns the Markdown content of one documentation page by its URL path, as found in the `path` field of `search-documentation`. Pass `headings` to return only the named h2 sections and reduce response size. The result is the Markdown string only, with no metadata. A path that names a section resolves to its first page. For a component, `get-component` returns the same content with metadata. Fails when no page exists at the path.

  • Get Example

    Retrieves the source code of a UI example. Returns the code as a string only, without metadata. Use `list-examples` to find the exact example name.

  • Get Migration Guide

    Returns the full guide for migrating an application from the previous major version of Nuxt UI to this one, as Markdown with its title, description and URL. Takes no parameters and covers that single upgrade only. The page is large. To read part of it, call `get-documentation-page` with `/docs/getting-started/migration` and a `headings` list.

  • Get Template

    Retrieves a template by its title (case-insensitive): description, framework, features, and links to its live preview and GitHub repository. Does not include setup instructions or source code. Use `list-templates` to find the exact title.

  • List Examples

    Lists the names of all available UI examples. Returns names only, not code: pass a name to `get-example` to read its source.

  • List Templates

    Lists the Nuxt UI templates with their full records and a `total` count. Pass `framework` to keep only templates whose framework matches exactly, ignoring case. An unknown value returns an empty list. Use this to find a template and its exact title. `get-template` returns a single template by title.

  • Search Components

    Search components by name, category, or intent. Matches alternate names from other ecosystems (e.g. "segmented control" finds FieldGroup, "combobox" finds InputMenu, "dialog" finds Modal). Results are ranked by relevance

  • Search Composables

    Finds Nuxt UI composables such as `useToast` or `useOverlay`. `search` is a case-insensitive substring match on the name, title and description, checked against the whole string, so pass one keyword rather than a sentence. With no `search` it lists every composable. Returns name, title, description, path and URL for each match, sorted by name. It does not return usage or signatures. Read a result with `get-documentation-page` using its `path`.

  • Search Documentation

    Search documentation pages by title, description, or section. With no params, lists all pages.

  • Search Icons

    Searches one Iconify collection for icons matching a keyword. One collection is searched per call, `lucide` by default, so repeat the call to try another. Returns each match as a `name` in the `i-{prefix}-{name}` format used by Nuxt UI with a `preview` SVG URL, plus the total match count.