VITE PLUGIN TOOLS

7 tools from the Vite Plugin MCP Server, categorised by risk level.

// ALL 7 VITE PLUGIN TOOLS

READ 6 tools

Read get-nuxt-config Get the Nuxt configuration, including the ssr, appDir, srcDir, rootDir, alias, runtimeConfig, modules, etc. Read get-vite-config Get the Vite config digest, including the root, resolve, plugins, and environment names. Read get-vite-module-info Get graph information of a module, including importers, imported modules, and compiled result. Read list-nuxt-auto-imports-items List auto-imports items, when importing new functions to the code, check available items from this tool. Read list-nuxt-components List registered components in the Nuxt app. When adding importing new components, check available component... Read list-nuxt-pages List registered pages and their metadata in the Nuxt app.

WRITE 1 tools

Write nuxt-scaffold Scaffold a new component/page/layout/middleware etc. in the current Nuxt project.

// RUNNING THIS SERVER

The managed route: connect Vite Plugin through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y vite-plugin-mcp

// FAQ

How many tools does the Vite Plugin MCP server have? +

The Vite Plugin MCP server exposes 7 tools across 2 categories: Read, Write.

How do I enforce policies on Vite Plugin tools? +

Route the Vite Plugin server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Vite Plugin tools fall into? +

Vite Plugin tools are categorised as Read (6), Write (1). Each category has a recommended default policy.

Enforce policy on every Vite Plugin tool call.

Start from Vite Plugin, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Instant setup, no code required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.