Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/nuxt-modules/mcp-toolkit/manage-mcpnpx skills add nuxt-modules/mcp-toolkit --skill manage-mcpgit clone --depth 1 https://github.com/nuxt-modules/mcp-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nuxt-modules/mcp-toolkit/manage-mcp)<a href="https://agentmods.dev/skills/nuxt-modules/mcp-toolkit/manage-mcp"><img src="https://agentmods.dev/badge/skills/nuxt-modules/mcp-toolkit/manage-mcp.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00050 | $0.08834 |
| Opus 5 | $0.00025 | $0.04417 |
| Sonnet 5 | $0.00010 | $0.01767 |
| Haiku 4.5 | $0.00005 | $0.00883 |
Grade B, and why
manage-mcp scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- **curl smoke test**: `curl -X POST … -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Hit the endpoint: `curl http://localhost:3000/mcp` (responds to MCP JSON-RPC) How it starts
The opening of the file, as written. The whole thing — 1,000 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage MCP
Complete skill for managing Model Context Protocol (MCP) servers in Nuxt with @nuxtjs/mcp-toolkit. Setup, create tools/resources/prompts, organize with multi-handler folder convention, build interactive UI widgets (MCP Apps), wire up sessions and observability, review, and troubleshoot.
When to Use
- Setup: "Setup an MCP server in my Nuxt app", "Add MCP to Nuxt"
- Create: "Add a tool that calculates BMI", "Expose a README as a resource", "Create a code-review prompt"
- Organize: "Split my MCP into admin + public endpoints", "Filter tools per user"
- Customize: "Add authentication to my MCP", "Log every tool call to Axiom", "Stream progress to the client"
- Build apps: "Add an interactive Vue widget callable from ChatGPT/Cursor"
- Persist state: "Remember the user across tool calls in one session"
- Review: "Review my MCP implementation", "Check for best practices"
- Troubleshoot: "My tool isn't discovered", "Auto-imports don't work", "OAuth flow keeps triggering"
- Test: "Eval which tools the model picks for these prompts"
Setup MCP Server
Installation
::code-group
pnpm add @nuxtjs/mcp-toolkit zod
npm install @nuxtjs/mcp-toolkit zod
yarn add @nuxtjs/mcp-toolkit zod
bun add @nuxtjs/mcp-toolkit zod
::
Or in one go via the Nuxt CLI:
npx nuxt add mcp
Add to nuxt.config.ts:
export default defineNuxtConfig({
modules: ['@nuxtjs/mcp-toolkit'],
mcp: {
name: 'My MCP Server',
description: 'Read and update todos for the current user.',
},
nitro: {
experimental: { asyncContext: true }, // required for useEvent / useMcpServer / useMcpLogger
},
})
Directory Structure
server/mcp/
├── tools/ # Actions the AI can perform
│ └── admin/ # Subdirectory → group: 'admin'
├── resources/ # Data the AI can read
├── prompts/ # Reusable message templates
└── handlers/ # Optional: named handlers mounted at /mcp/<name>
└── admin/
├── index.ts # defineMcpHandler({ middleware: requireAdmin })
├── tools/ # auto-attached to /mcp/admin
└── resources/
app/mcp/ # Optional: MCP Apps (interactive Vue widgets)
└── palette.vue # → app `palette`, callable from ChatGPT / Cursor
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 1,000 lines · 50 tokens per session scan B d2cad7e7d0cd
manage-mcp is a skill published in the GitHub repository nuxt-modules/mcp-toolkit (170 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 8,834 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
manage-bx24-template-mcp
Skill "manage-bx24-template-mcp" from bitrix24/templates-mcp, covering bx24-template-mcp — agent skill, project context, ground rules, code review — persona walk and feedback mechanism.
run-manual-qa
Organize and run a manual QA pass against the bitrix24/templates-mcp MCP server — first through the MCP Inspector, then through an AI agent connector. Use when the user asks to "run manual QA", "test PR.
team-dev
Implement a feature then iterate with architect, frontend lead, devil's advocate, and code reviewer reviews (×3 rounds).
verify-rule
Use when verifying a CSS noop rule against real Chromium behavior, checking rule correctness and e2e/unit test consistency. Triggers on "verify rule", "check rule", "re-verify", or reviewing rule accuracy after changes.
speckit-checklist
Generate a custom checklist for the current feature based on user requirements.