Nuxt MCP
The nuxt-mcp gives AI coding assistants direct insight into your Nuxt or Vite application’s internal structure.
It provides two packages: nuxt-mcp, a Nuxt module, and vite-plugin-mcp, a Vite plugin. Both spin up a local MCP (Model Context Protocol) server that exposes your project’s configuration, module graph, and other runtime details to compatible AI tools like Cursor, Windsurf, or Claude Code.
This allows the AI to move beyond simple file reading and understand the actual context of your framework-specific setup.
Features
- 🧠 AI Context for Frameworks: Provides your Nuxt or Vite app’s internal state and configuration directly to AI coding assistants via the MCP protocol.
- ⚡ Zero-Config Setup: For supported editors, the plugin can automatically configure your
nuxt.config.tsorvite.config.tsfile on installation. - 🔌 Extensible Architecture: Offers a
mcp:setuphook for other Nuxt modules to register their own custom tools and expose additional data to the AI.
How To Use It
For Nuxt Projects:
Install the package:
npm install nuxt-mcpAdd to your nuxt.config.ts:
export default defineNuxtConfig({
modules: ['nuxt-mcp']
})The MCP server becomes available at http://localhost:3000/__mcp/sse. Compatible AI editors will automatically detect and configure themselves to use this endpoint.
For Vite Projects:
Install the package:
npm install vite-plugin-mcpAdd to your vite.config.ts:
import { defineConfig } from 'vite'
import { ViteMcp } from 'vite-plugin-mcp'
export default defineConfig({
plugins: [ViteMcp()]
})The MCP endpoint runs at http://localhost:5173/__mcp/sse.
Extending with Custom Tools:
Other Nuxt modules can contribute additional MCP tools using the mcp:setup hook:
nuxt.hook('mcp:setup', ({ mcp }) => {
mcp.tool('get-nuxt-root', 'Get the Nuxt root path', {}, async () => {
return {
content: [{
type: 'text',
text: nuxt.options.rootDir,
}],
}
})
})The Vite plugin accepts configuration options for customizing the auto-configuration behavior through updateConfig and updateConfigServerName parameters.
Latest MCP Servers
Memo
Colab
Excalidraw
Featured MCP Servers
Excalidraw
Claude Context Mode
Context+
FAQs
Q: What exactly is the Model Context Protocol (MCP)?
A: MCP is an open standard, like a common language, that lets AI applications (clients) and external data sources or tools (servers) talk to each other. It helps AI models get the context (data, instructions, tools) they need from outside systems to give more accurate and relevant responses. Think of it as a universal adapter for AI connections.
Q: How is MCP different from OpenAI's function calling or plugins?
A: While OpenAI's tools allow models to use specific external functions, MCP is a broader, open standard. It covers not just tool use, but also providing structured data (Resources) and instruction templates (Prompts) as context. Being an open standard means it's not tied to one company's models or platform. OpenAI has even started adopting MCP in its Agents SDK.
Q: Can I use MCP with frameworks like LangChain?
A: Yes, MCP is designed to complement frameworks like LangChain or LlamaIndex. Instead of relying solely on custom connectors within these frameworks, you can use MCP as a standardized bridge to connect to various tools and data sources. There's potential for interoperability, like converting MCP tools into LangChain tools.
Q: Why was MCP created? What problem does it solve?
A: It was created because large language models often lack real-time information and connecting them to external data/tools required custom, complex integrations for each pair. MCP solves this by providing a standard way to connect, reducing development time, complexity, and cost, and enabling better interoperability between different AI models and tools.
Q: Is MCP secure? What are the main risks?
A: Security is a major consideration. While MCP includes principles like user consent and control, risks exist. These include potential server compromises leading to token theft, indirect prompt injection attacks, excessive permissions, context data leakage, session hijacking, and vulnerabilities in server implementations. Implementing robust security measures like OAuth 2.1, TLS, strict permissions, and monitoring is crucial.
Q: Who is behind MCP?
A: MCP was initially developed and open-sourced by Anthropic. However, it's an open standard with active contributions from the community, including companies like Microsoft and VMware Tanzu who maintain official SDKs.
