Handlers

Default & custom Structure & options Examples & routing Sharing & practices Multi-handler organization

Create custom MCP endpoints with their own tools, resources, and prompts.

What are Handlers?

Handlers allow you to create multiple MCP endpoints in a single Nuxt application. Each handler has its own route, name, version, and can include its own set of tools, resources, and prompts.

Create a custom MCP handler and endpoint

This is useful when you want to:

Separate different MCP functionalities into different endpoints
Create versioned MCP APIs
Organize tools/resources by domain or feature

Guides

Multi-handler organization

Folder convention to attribute tools, resources, and prompts to MCP routes — plus the getMcp* escape hatch.

Default & custom handlers

Override /mcp via server/mcp/index.ts, or expose new endpoints with defineMcpHandler.

Structure & options

Every defineMcpHandler field — name, route, middleware, tools, experimental_codeMode.

Sharing & practices

Cross-handler tool sharing, file layout, and use cases.

Edit this pageorReport an issue

Patterns & advanced

Real-world examples, organization, type safety, best practices, and conditional registration.

Default & custom handlers

Override the default `/mcp` handler and add custom defineMcpHandler endpoints.