nuxt-mcp-dev / vite-plugin-mcp

What it does

This repository ships two packages that add an MCP server to a running development server. You don't start it as a separate process. vite-plugin-mcp is a Vite plugin, and nuxt-mcp-dev is a Nuxt module built on top of it. Once the plugin is added to the project config, the dev server serves an SSE endpoint at /__mcp/sse. That is http://localhost:5173/__mcp/sse for Vite by default and http://localhost:3000/__mcp/sse for Nuxt. An editor assistant connects to that address.

With the Vite plugin on its own, the server has two tools. One returns a summary of the resolved Vite config: root, resolve options, plugin names and environment names. The other returns the module-graph records for a file path: its importers, its imports, HMR timestamp and the transformed output. The Nuxt module adds five tools to those two, for seven in all at v0.3.2 (counted in packages/nuxt-mcp-dev/src/tools/runtime.ts and scaffold.ts). These tools return the Nuxt config, the auto-import items, the registered components and the pages. The fifth, nuxt-scaffold, creates a new file from one of 16 nuxi templates. The Nuxt module also registers a prompt and an mcp:setup hook that other Nuxt modules can use to add tools of their own.

On startup the plugin edits MCP client config files by default (updateConfig: 'auto'). It writes .cursor/mcp.json if a .cursor folder exists in the workspace root, .vscode/mcp.json if a .vscode folder exists, and .mcp.json for Claude Code if that file already exists. It writes ~/.codeium/windsurf/mcp_config.json if Windsurf is installed. The Nuxt module also adds an entry named nuxt-docs, pointing at https://nuxt.com/mcp, to those files unless includeNuxtDocsMcp is set to false (packages/nuxt-mcp-dev/src/module.ts). The README doesn't mention this extra entry. Its makers label both packages experimental.

What it needs

A Vite project (vite-plugin-mcp, added under plugins in vite.config) or a Nuxt project (nuxt-mcp-dev, added under modules in nuxt.config), installed as a dev dependency. The project's dev server must be running, because the endpoint exists only while it runs. The Vite tools read vite.environments, which needs the Environment API from Vite 6. An MCP client that can connect to an SSE URL.

Limits

Its makers call it experimental and say vite-plugin-mcp is not ready for production. The endpoint uses SSE only (/__mcp/sse); no stdio or launch command is provided. It works only while the dev server runs, and nothing reaches a production build. The Vite plugin alone has just 2 tools. The 5 Nuxt tools exist only through nuxt-mcp-dev. get-vite-module-info needs an absolute file path. Its makers point to @nuxtjs/mcp-toolkit for building an MCP server into your own Nuxt app, and to the Nuxt docs server for documentation.

Who it suits

Suits Vite or Nuxt developers who use an editor assistant and want it to check real project state before editing code: resolved config, which auto-imports and components exist, the pages, and how a module is transformed. It is local and needs no sign-in. Most tools only read, but nuxt-scaffold creates files, and the plugin rewrites editor MCP config files unless updateConfig is false. Not a fit for production use, for projects on other build tools, or for Nuxt documentation lookups. For documentation, the Nuxt docs server its README names is the better choice.