Vite Plugin MCP Server: Setup for Claude, Cursor and Other Apps
Lets Claude, Cursor and other assistants inspect your Vite dev setup and module graph while your app runs.
vite-plugin-mcp is a Vite plugin, not a program you run on its own. You add it to your vite config, start the dev server, and your assistant can then read the config and the module graph from the running app. The README calls it experimental. It exposes two read-only tools and, by default, edits your MCP config files for you.
Good for
- Vite developers who want an assistant to understand their config and imports
- People debugging why a module is bundled or imported
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports hosted MCP servers.
Only through the mcp-remote bridge (our adaptation, not in the plugin README); custom connectors cannot reach localhost. GitHub
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
The server listens on localhost on your computer, which ChatGPT's hosted connectors cannot reach. GitHub
Install vite-plugin MCP
Claude Code
- 1
Copy this prompt.
Add the vite-plugin MCP server to Claude Code. Open vite.config.ts (create it if it does not exist) and merge in this entry, keeping any servers already there: // vite.config.ts import { defineConfig } from 'vite' import { ViteMcp } from 'vite-plugin-mcp' export default defineConfig({ plugins: [ViteMcp()], }) Then tell me how to load it and whether I need to sign in. - 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires A Vite project, Install with: npm i -D vite-plugin-mcp.
Read-only mode: Both tools only read. The plugin edits MCP config files unless you set updateConfig to false.
Add the plugin first and start your Vite dev server; the server only runs while the dev server runs. With the default updateConfig: 'auto' the plugin writes the server into the config of Cursor, VS Code, Windsurf and Claude Code when it finds their project folders, so the second method is only needed for other cases. The port is your dev server's port (5173 by default). This server runs on your computer at localhost, so hosted apps like ChatGPT cannot reach it.
From the project README. Source.
Tools
Shows your Vite project's root, plugins and environments
Returns a digest of the running Vite config: the project root, resolve settings, plugin names and environment names.
Try: “Which plugins is my Vite app using?”
Read ·
get-vite-configShows what a module imports, who imports it, and its compiled output
Looks up one file in the dev server's module graph and returns the files that import it, the files it imports, and the compiled code. The file must be a module Vite has already loaded.
Try: “What imports src/main.ts, and what does it import?”
Read ·
get-vite-module-info
Read from the source code
Permissions
low risk · 4 things to watch
Low risk
The assistant can read your Vite config and compiled module code from the dev server, and the plugin writes MCP config files unless you turn that off. Keep the dev server on localhost.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only modeHow to turn it on
Watch out for
The plugin edits your MCP config files
By default it writes the server address into .cursor/mcp.json, .vscode/mcp.json, .mcp.json for Claude Code, or your Windsurf config when those exist. Set updateConfig to false to stop that. github.com
Compiled source code is exposed to your assistant
The module tool returns the compiled output of project files, so anything in them can reach the model. github.com
The endpoint has no sign-in
It runs on your Vite dev server at localhost by default. Anything that can reach that port can use it, so avoid exposing the dev server on a network. github.com
The author calls it experimental
The README says it is not ready for production, and it only runs while the dev server runs. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Turning on read-only | Both tools only read from the running Vite dev server. Nothing is written by the tools. |
|---|---|
| Sign-in and keys | No account or key. Runs inside your own dev server. |
Questions
Is vite-plugin-mcp official?
No. It is a community plugin by Anthony Fu in the nuxt-mcp-dev repository, not made by the Vite team.
How do I install it?
Add the plugin to your vite config, as in the install box, and start the dev server. The server only exists while Vite runs.
What is the server URL?
http://localhost:5173/__mcp/sse by default, using your dev server port. It uses the older SSE connection type.
Does it change my config files?
Yes by default. It adds the server to Cursor, VS Code, Windsurf and Claude Code config files it finds in the project. Set updateConfig to false to turn that off.
Can it change my code?
No. Both tools only read the Vite config and the module graph.
Does it work with Nuxt?
The plugin lives in the nuxt-mcp-dev repository next to a Nuxt module, but this page covers only the Vite plugin.
Is it ready for production?
No. The README marks it experimental and not ready for production.
Does it work in ChatGPT or Claude Desktop connectors?
No. The server runs on your own computer at localhost, which hosted apps cannot reach.
Information
updated Nov 2, 2026
- Publisher
- Community
- Transport
- SSE
- Auth
- None
- Version
- 0.3.2
- License
- MIT
- Last commit
- Mar 1, 2026
- Open issues
- 9
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 3Hide
- github.com · github.com
- github.com · github.com
- github.com · github.com