aiti-devtools-nuxt

❝ Every extra step of integration cost creates one more person who never integrates. ❞

Nuxt module: one line in modules = built-in MCP in the dev server (bridge/MCP/launcher same-origin under /aiti/) + launcher auto-injected into the head + automatic agent-tool registration at startup. The user changes no application files.

Installation

npm

npm install -D aiti-devtools-nuxt

yarn

yarn add -D @aiti-ai/aiti-devtools-nuxt

pnpm

pnpm add -D @aiti-ai/aiti-devtools-nuxt

bun

bun add -D @aiti-ai/aiti-devtools-nuxt

Configuration

// nuxt.config.ts — the only place the user touches
export default defineNuxtConfig({
  modules: ['@aiti-ai/aiti-devtools-nuxt'],
  aitiDevtools: { mcp: { register: false } },   // optional, passes through AitiDevtoolsOptions
});

Behavior

• The module internally mounts the aiti-devtools-vite plugin (Nuxt dev runs on Vite underneath) + a Nitro/head injection fallback
• SSR-rendered HTML is injected too (head script)
• dev-only: nuxt build production output gets zero injection
• The aitiDevtools key passes the Vite plugin's options straight through (name/bridgeUrl/aiUrl/mcp…)

Verification

pnpm dev --port 5599
curl -s http://localhost:5599/ | grep -o aiti-launcher   # the launcher script should appear in the HTML

Runnable example: examples/aiti-nuxt-demo (port 5599)