Nuxt Devtools v4.1.0: disabling Vite MCP and component inspector via vue-tracerBrief · digest for November 3
Brief≈ 1 min

Nuxt Devtools v4.1.0: disabling Vite MCP and component inspector via vue-tracer

For developers in the Vue ecosystem, the Nuxt Devtools panel has long been an indispensable tool. In Nuxt Devtools v4.1.0, Anthony Fu added control over the Model Context Protocol (MCP) and fixed networking bugs in local debugging.

The headline addition is the devtools.mcp option. You can now explicitly disable the built-in Vite DevTools MCP endpoint if your project doesn't use AI agents or you want to close an unnecessary socket:

// nuxt.config.ts
export default defineNuxtConfig({
  devtools: {
    enabled: true,
    mcp: false // Disable the Vite DevTools MCP endpoint
  }
})

The dock toolbar now integrates the vue-tracer inspector, letting you highlight a component in the browser and jump straight to its file in your IDE with a single click. The release also fixes WebSocket behavior during local HTTPS development and resolves connection drops on the local network when launching with the --public flag.

You can install the update with the standard command:

pnpm update @nuxt/devtools
Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 3