FileScopeMCP
Ask what a file does and get an answer without the model reading the source — plus who calls the function you are about to change.Read full description
admicaLABSCO SUMMARY
The dev server already knows how the app is wired; this lets the model ask it.
It is small on purpose — a module or a plugin, not a separate process — and it is experimental, so treat it as a development-time convenience rather than something to depend on.
What it is
A pair of packages that add MCP support to a local development server: nuxt-mcp-dev as a Nuxt module and vite-plugin-mcp as a Vite plugin. The MCP server lives inside the dev server you already run.
What you get
An MCP endpoint attached to your local Vite or Nuxt development server, so a model asking about your app is answered by the running app rather than by reading files on disk.
Requirements
A local Vite or Nuxt development server. Add nuxt-mcp-dev as a Nuxt module or vite-plugin-mcp as a Vite plugin. Both are marked experimental by the author and should be used with caution. Two adjacent projects are pointed at for different needs: @nuxtjs/mcp-toolkit for building an MCP server out of your own Nuxt application, and the Nuxt documentation MCP server for documentation questions. MIT licensed.
Setup effort
One command — npx -y nuxt-mcp-dev
USE CASES
01
Helping a model understand your local app
The MCP endpoint runs inside the dev server, so questions about the app are answered from its live state rather than inferred from the source tree.
02
Adding it to a Nuxt project
Install the Nuxt module; there is no separate server to start or port to manage.
03
Adding it to a plain Vite project
The Vite plugin covers the same ground for apps that are not Nuxt.
BEFORE YOU INSTALL
What to know first
Requires
npx on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"nuxt-mcp-dev": {
"command": "npx",
"args": [
"-y",
"nuxt-mcp-dev"
]
}
}
}npx
TERMINAL
npx -y nuxt-mcp-dev
