add-mcp-tools

To add MCP tools with Better Auth, you define zod schemas, scaffold handlers via defineTool, apply access control, and update the tool registry. This enforces consistent patterns and auditability for new tool domains like webhooks or secrets.

The defineTool scaffolding structures MCP tool handlers by enforcing consistent input and output schemas via zod. It standardizes the tool definition process to ensure predictable execution and seamless integration with the broader tool registry.

The best way to organize MCP tool files is using a scalable blueprint with separate files for schemas, create, list, update, delete operations, and an index barrel. This maintains consistency across new domains like apiKeys and webhooks.

Yes, zod schemas are required to define MCP tools because they enforce strict input and output validation. This schema-first approach ensures data integrity and consistency when integrating new tool domains into the registry.

Yes, Better Auth RBAC can be used for MCP tool access control. It integrates directly into the tool definition process to manage permissions, ensuring only authorized users can execute specific tool handlers within the mesh.

You should not use the MCP tools blueprint for simple, one-off scripts that do not require registry updates, strict schemas, or Better Auth integration. It is designed for expanding tool domains needing structured access control and auditability.