Nuxt
Search Nuxt documentation, modules, deploy providers, and changelogs. No key required.
What Nuxt exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the nuxt__ namespace. Your agent never loads them all — it searches, and gets the few that match.
nuxt__get-blog-post1 argument · 1 required
Get Blog Post
Retrieves the full content of a specific Nuxt blog post. WHEN TO USE: Use this tool when you know the EXACT path to a blog post. Common scenarios: - User asks for a specific post: "Get the blog post about Nuxt 4" → /blog/v4 - You found a relevant post from list_blog_posts and want the full content - The current page context is a /blog/... path WHEN NOT TO USE: If you don't know the exact path and need to search/discover, use list_blog_posts first. Never call this tool twice for the same path — one call returns the full post. EXAMPLES: "/blog/v4", "/blog/nuxt3", "/blog/nuxt-on-the-edge"
Required
pathnuxt__get-changelog2 arguments
Get Changelog
Retrieves the latest releases from Nuxt core and official modules (changelog). WHEN TO USE: Use this tool when users ask about: - "What's new in Nuxt?" - latest releases and changes - "What changed in Nuxt UI v3?" - specific module updates - "Show me recent bug fixes" - browse recent changelogs - "What version of nuxt/content was just released?" - check latest versions - "Changelog for Nuxt" - general changelog queries Covers repositories: nuxt/nuxt, nuxt/ui, nuxt/content, nuxt/image, nuxt/fonts, nuxt/devtools, nuxt/scripts, nuxt/eslint, nuxt/icon, nuxt/hints, nuxt/test-utils, nuxt-content/nuxt-studio. OUTPUT: Returns releases with title, repo, tag, date, and raw markdown body. Optionally filter by repository name.
nuxt__get-deploy-provider2 arguments · 1 required
Get Deploy Provider
Retrieves detailed deployment instructions and setup guide for a specific hosting provider. WHEN TO USE: Use this tool when you know EXACTLY which provider the user wants. Common scenarios: - User asks for a specific provider: "How do I deploy to Vercel?" → /deploy/vercel - User mentions a known platform: "Cloudflare deployment" → /deploy/cloudflare - You found a relevant provider from list_deploy_providers and want full details WHEN NOT TO USE: If the user is asking about options or comparing providers, use list_deploy_providers first. EXAMPLES: "/deploy/vercel", "/deploy/cloudflare", "/deploy/netlify", "/deploy/aws", "/deploy/node-server"
Required
pathnuxt__get-documentation-page2 arguments · 1 required
Get Documentation Page
Retrieves the full content and details of a specific Nuxt documentation page. WHEN TO USE: Use this tool when you know the EXACT path to a documentation page. Common use cases: - User asks for a specific page: "Show me the introduction page" → /docs/4.x/getting-started/introduction - User asks about a known topic with a dedicated page - You found a relevant path from list_documentation_pages and want the full content WHEN NOT TO USE: If you don't know the exact path and need to search/explore, use list_documentation_pages first. COMMON PAGES (Nuxt 4.x): Getting Started: - "/docs/4.x/getting-started/introduction" - main intro - "/docs/4.x/getting-started/installation" - setup - "/docs/4.x/getting-started/upgrade" - migration from v3 Core Concepts: - "/docs/4.x/guide/concepts/rendering" - SSR/CSR/SSG modes - "/docs/4.x/guide/concepts/auto-imports" - auto-imports - "/docs/4.x/guide/concepts/server-engine" - server features Directory Structure: - "/docs/4.x/guide/directory-structure/composables" - composables - "/docs/4.x/guide/directory-structure/components" - components - "/docs/4.x/guide/directory-structure/pages" - routing Common Issues: - "/docs/4.x/guide/going-further/debugging" - debugging - "/docs/4.x/guide/going-further/error-handling" - errors
Required
pathnuxt__get-getting-started-guide2 arguments
Get Getting Started Guide
Retrieves the official "Getting Started" introduction page for a given Nuxt major version. WHEN TO USE: When the user wants a high-level overview / setup guide for Nuxt without specifying a precise documentation page. WHEN NOT TO USE: For a specific page outside the introduction, prefer get_documentation_page.
nuxt__get-module1 argument · 1 required
Get Module
Retrieves complete details about a specific Nuxt module including README, compatibility, maintainers, and stats. WHEN TO USE: Use this tool when you know the EXACT module identifier. Common scenarios: - User asks for a specific module: "Get details about @nuxt/ui" - User mentions a known module: "Show me nuxt-icon module" - You found a relevant module from list_modules and want full details - You need to check Nuxt 4 compatibility for a specific module WHEN NOT TO USE: If you don't know the exact module identifier and need to search/discover modules, use list_modules first. PARAMETER: slug (required) - The unique module identifier EXAMPLES: - slug: "@nuxt/ui" - slug: "@nuxtjs/i18n" - slug: "nuxt-icon" - slug: "@nuxt/image" - slug: "nuxt-auth"
Required
slugnuxt__list-blog-postsno arguments
List Blog Posts
Lists all Nuxt blog posts with metadata including titles, dates, categories, tags, and descriptions. WHEN TO USE: Use this tool when you need to DISCOVER or SEARCH for blog posts. Common scenarios: - "What are the latest announcements?" - browse recent posts - "Has there been any post about X feature?" - search by topic - "Show me performance improvements" - find relevant posts by topic - "What's new in Nuxt?" - explore recent updates WHEN NOT TO USE: If you already know the exact blog post path (e.g., "/blog/v4"), use get_blog_post directly. OUTPUT: Returns list of posts with title, description, date, path. Use get_blog_post to retrieve full content of specific posts.
nuxt__list-deploy-providersno arguments
List Deploy Providers
Lists all deployment providers and hosting platforms for Nuxt applications with their features and capabilities. WHEN TO USE: Use this tool when you need to DISCOVER or COMPARE deployment options. Common scenarios: - "What deployment platforms are available?" - browse all options - "I need edge functions support" - compare features across providers - "Show me platforms with free tiers" - search for specific features - "What are my deployment options?" - general exploration WHEN NOT TO USE: If you know the exact provider (e.g., "Vercel", "Cloudflare"), you can use get_deploy_provider directly with the path. OUTPUT: Returns list of providers with titles, descriptions, and paths. Use get_deploy_provider for detailed deployment instructions.
nuxt__list-documentation-pages2 arguments
List Documentation Pages
Lists Nuxt documentation pages, optionally filtered by search term. WHEN TO USE: When you need to find documentation about a topic but don't know the exact page path. WHEN NOT TO USE: If you already know the page path, use get_documentation_page directly. TIPS: Always pass a search term to narrow results — avoids dumping the entire catalog.
nuxt__list-modules5 arguments
List Modules
Lists all available Nuxt modules with optional filtering and sorting capabilities. WHEN TO USE: Use this tool when you need to DISCOVER or SEARCH for modules. Common scenarios: - "I need an authentication module" - search by category or keyword - "What UI libraries are available?" - filter by category - "Show me popular image optimization modules" - filter + sort by downloads - "Find a module for X feature" - general exploration PARAMETERS: - search: Filter by name, description, or npm package name - category: Filter by exact category name (e.g., "Security", "UI", "Database", "CMS", "SEO") — use search for keyword discovery, not category - sort: Order by downloads, stars, publishedAt, or createdAt - order: asc or desc - includeStats: Include full per-module stats (downloads, stars, publishedAt, createdAt, etc.). Defaults to true when sort is publishedAt or createdAt. WHEN NOT TO USE: If you already know the exact module slug (e.g., "@nuxt/ui"), use get_module directly. OUTPUT: Returns list of modules with name, description, category, and either downloads/stars or full stats. Use get_module for complete details including README and compatibility.
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Nuxt is already on
It needs no credential, so it is on for every account from the first call.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.devOthers in the same category.
They share the endpoint, so having more than one on costs you nothing in context — the search decides which is relevant.