All servers / Developer / Nuxt Projects MCP server
Nuxt Projects MCP server
MCP server for Nuxt projects — exposes routes, components, config, and more to AI agents
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.8.0. Package: mcp-server-nuxt · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.7 seconds including download)
- Tools offered: 33
- Last published: 2026-11-16
- Weekly downloads (npm): 1,747
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_project_overviewno parametersGet a high-level overview of the Nuxt project: root, name, Nuxt version, config file, directory layout, layer list, and counts of routes, components, composables, server routes, middleware, plugins and modules.
get_type_infono parametersRead generated Nuxt type information (imports.d.ts, types/*, nuxt.schema.json). Auto-generates types into a cache when `.nuxt` is missing — no nuxi prepare required.
list_routes1 of 1 parameter describedList all page routes with their resolved URL paths, source files, params, middleware, layouts and children. Use this to understand the page/routing surface of the project.
get_route1 of 1 parameter describedGet detailed information about a single page route by its resolved URL path (e.g. /users/:id).
explain_route2 of 2 parameters describedExplain how Nuxt resolves a concrete URL (e.g. /users/42): matched page, dynamic params, nested parents, layout, middleware order, data-fetching calls, and mapped /api server handlers. Static analysis only — no DevServer or nuxi prepare.
add_route4 of 4 parameters describedScaffold a new page route under the project pages directory (honoring srcDir) following Nuxt conventions. Supports static, dynamic (:id -> [id]), optional ([[id]]), optional catch-all ([[...slug]]), and catch-all ([...slug]) segments.
list_components4 of 4 parameters describedList Vue components using .nuxt/components.d.ts when it exists, otherwise the components config (dirs, prefix, pathPrefix, extensions, aliases). Includes props, emits, and slots.
inspect_component1 of 1 parameter describedGet one component by the auto-imported name Nuxt would generate (prefix, path segments, and components.d.ts). Returns props, slots, and emits.
generate_component5 of 5 parameters describedGenerate a new Vue SFC under the project components directory (honoring srcDir) with typed defineProps/defineEmits and slots.
list_composables1 of 1 parameter describedList all composables, both auto-imported and explicit. Returns name, file path, parameters, and return type. Use this to discover reusable logic before writing new code.
get_auto_imports1 of 1 parameter describedRead the auto-imports registry (imports.d.ts): every auto-imported symbol with its source path and type signature. Auto-generates types into a cache when `.nuxt` is missing.
generate_composable3 of 3 parameters describedGenerate a new composable under the project composables directory (honoring srcDir) with a typed export. Names are normalized to useXxx.
list_server_routes1 of 1 parameter describedList all Nitro server API routes, middleware, and plugins. Returns route path, handler file, HTTP method, and middleware chain. Use this to understand the server/API surface of the project.
scaffold_nitro_api4 of 4 parameters describedGenerate a new Nitro server API handler under the project server/api directory (honoring serverDir) with H3 defineEventHandler and optional Zod body validation.
list_modules1 of 1 parameter describedList Nuxt modules discovered from nuxt.config and package.json, with version, status (active/inactive) and source. Use this to understand which Nuxt features are available.
add_nuxt_module3 of 3 parameters describedAdd a Nuxt module to the modules array in nuxt.config, optionally with options. Returns a diff; dry-run by default.
inspect_route_meta1 of 1 parameter describedInspect a single route: returns route params, middleware, layout, page meta plus the component props, emits and slots. Accepts a route path (e.g. /users/:id) or a page file path.
read_config1 of 1 parameter describedRead the resolved Nuxt config, or a single key by dot-notation (e.g. runtimeConfig.public.apiBase). Omit the key to return the whole config.
update_config3 of 3 parameters describedUpdate a nuxt.config value by dot-notation key. Returns a diff of the change. Dry-run by default; real writes require the server to be started with write authorization.
search_code5 of 5 parameters describedSearch project source files for a substring or regex. Returns matching files with line/column numbers and surrounding context lines.
get_nuxt_docs1 of 1 parameter describedGet targeted offline Nuxt documentation guidance for a feature area (routing, nitro, modules, layers, composables, config, components).
inspect_layersno parametersResolve and return the full Nuxt extends hierarchy (layers). Returns layers ordered by override priority (project first), with each layer's config file, raw extends, and sub-layers.
check_type_errorsno parametersRun a TypeScript type check against Nuxt-generated tsconfig (auto-generated into a cache when `.nuxt` is missing) or the project tsconfig.json. Returns structured diagnostics with file, line, column, code and severity.
analyze_bundle_depsno parametersAnalyze package.json dependencies: classify Nuxt modules vs runtime/dev dependencies and surface warnings for misplaced or missing modules.
analyze_project2 of 2 parameters describedAnalyze overall project health: overview counts, dependency warnings, component sample with pagination, and hints (e.g. type auto-generation when .nuxt is missing).
explain_render_mode2 of 2 parameters describedExplain how Nitro resolves the render mode for a concrete URL from nuxt.config routeRules / nitro.routeRules (ssr, spa, prerender, isr, swr, static) plus cache, redirect, cors, headers and proxy. Static analysis only — no DevServer or nuxi prepare.
find_api_callers2 of 2 parameters describedFind every page/component/composable/layout/plugin/middleware/util that calls a server API route via useFetch, useLazyFetch, $fetch, or useAsyncData($fetch). Accepts a handler file path (server/api/users/[id].get.ts) or a concrete URL (/api/users/42). Static analysis only — no DevServer or nuxi prepare.
find_usages2 of 2 parameters describedFind every file that uses a component or composable (explicit imports, Nuxt auto-imports, Lazy prefix, kebab-case templates). Omit target to list unused components and composables. Static analysis only — no DevServer or nuxi prepare.
check_ssr_safety2 of 2 parameters describedStatically flag SSR hazards: browser-only globals at setup top level / module scope, non-deterministic values (Date.now / Math.random / crypto.randomUUID) rendered in templates or computed, and shared ref/reactive state in composables. Static analysis only — no DevServer or nuxi prepare.
explain_middleware2 of 2 parameters describedExplain a Nuxt middleware (global / named / inline): its type, global run order, the routes it applies to, and whether it calls navigateTo or abortNavigation. Omit name to list all middleware and flag pages referencing missing middleware. Static analysis only — no DevServer or nuxi prepare.
check_runtime_config1 of 1 parameter describedParse runtimeConfig from nuxt.config, list flattened keys with types and env vars, scan useRuntimeConfig() accesses, and report undefined/unused keys plus private keys read in client code. Never prints values. Static analysis only — no DevServer or nuxi prepare.
explain_data_fetching2 of 2 parameters describedList useFetch / useLazyFetch / useAsyncData / useLazyAsyncData / $fetch calls with URL or key, method and detected options, and flag duplicate keys, $fetch in onMounted, bare await $fetch at setup top level, server: false without lazy, and lazy results rendered without pending/status. Accepts a page/component file or a URL resolved like explain_route. Static analysis only — no DevServer or nuxi prepare.
check_nuxt4_migration1 of 1 parameter describedCheck a Nuxt project against the official Nuxt 4 upgrade guide: current package.json version, app/ directory or future.compatibilityVersion 4, legacy root directories, singleton data-fetching conflicts, data/error/pending/shallow-reactivity changes, and removed APIs/options (route.meta, Unhead v2, window.__NUXT__, generate, experimental, pages:extend meta). Static analysis only — no DevServer or nuxi prepare.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.