Server facts
nuxt-mcp-dev / vite-plugin-mcp
Project
- Author
- antfu
- Repository
- github.com/antfu/nuxt-mcp
- License
- MIT
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 911
- Last commit
- Data as of
Tags
- Local Development
- Nodejs
- Nuxt
- Vite
Overview
The nuxt-mcp repository contains two packages intended to help models understand an application running locally. The Nuxt integration is called nuxt-mcp-dev and is presented as a module that adds MCP capabilities to a Nuxt development server. The companion vite-plugin-mcp package serves the corresponding role for a Vite application. This division makes the repository relevant to developers looking for framework-level MCP integration during local development, rather than a standalone catalog of documentation tools. The supplied project metadata identifies a Node runtime and an MIT license.
The README is brief and labels the project experimental, with an explicit caution about use. It does not enumerate exposed tools, show a runnable installation or startup command, or explain authentication and configuration. As a result, the provided material establishes the packages' purpose but does not establish specific inspection operations, environment variables, or deployment behavior. It also distinguishes this experiment from two other resources: the Nuxt MCP toolkit for building an application's MCP server, and Nuxt's documentation MCP offering. Those references are alternatives for different goals, not features claimed for these packages. Choose this repository for its stated local-app integration focus, while recognizing that the supplied README alone is insufficient for a complete setup.
Install & configure
Requirements
- A Nuxt or Vite application, depending on the package
No install command stated in the README — see repo.
Not stated in the README: a runnable installation or launch command. The input metadata lists stdio, but the README does not explain transport setup. Package names are nuxt-mcp-dev and vite-plugin-mcp.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
No individual tool names were confirmed in the source material. Check the repository for its current tool list.
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Explore MCP support within a local Nuxt development server.
- Evaluate a Vite plugin for exposing application context to models.
- Compare local-app MCP integration with Nuxt documentation access.
Strengths
- Provides separate integration packages for Nuxt and Vite.
- Targets context from locally running applications.
- MIT license is explicitly identified.
Limitations
- Marked experimental with a caution to users.
- No runnable setup command is supplied.
- Specific tools and configuration are not described.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
