Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nuxt Docs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Official Nuxt framework documentation search and module lookup.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nuxt-docs-mcp https://nuxt.com/mcp
# 2 — ask your agent for something these tools do
# get-blog-post, list-blog-posts, get-changelog and 7 more
Nuxt Docs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http nuxt-docs-mcp https://nuxt.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | The path to the blog post (e.g., /blog/v4) |
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
No parameter schema on file.
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" - ge
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Filter by repository (e.g., "nuxt/ui", "nuxt/nuxt"). If omitted, returns releases from all repos. |
| limit | number | no | Number of releases to return (default: 5, max: 20) |
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_deplo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | The path to the deploy provider (e.g., /deploy/vercel) |
| sections | array | no | Specific h2 section titles to return. If omitted, returns full content. |
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 f
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | The path to the documentation page (e.g., /docs/4.x/getting-started/introduction) |
| sections | array | no | Specific h2 section titles to return (e.g., ["Usage", "API"]). If omitted, returns full documentation. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Nuxt major version |
| sections | array | no | Specific h2 section titles to return. If omitted, returns full guide. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Documentation version to fetch |
| search | string | no | Filter pages by keyword (matches title, path, and description). Strongly recommended to avoid large results. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The unique module identifier, exactly as shown in list_modules (e.g., "@nuxt/ui", "@nuxtjs/i18n", "nuxt-icon") |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Search term to filter modules by name, description, or npm package name |
| category | string | no | Filter by exact category name (e.g., "Security", "UI", "Database", "CMS", "SEO"). Auth modules use category "Security", not "auth". Prefer search for keyword discovery. |
| sort | string | no | Sort modules by downloads, stars, published date, or created date |
| order | string | no | Sort order (ascending or descending) |
| includeStats | boolean | no | Include full per-module stats. Defaults to true when sort is publishedAt or createdAt. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nuxt Docs or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Nuxt Docs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.