Create Builtin MCP Tool Skill

To scaffold a built-in MCP tool server for LibrAgent, this skill generates a standard directory layout including server modules, tool schemas, handlers, and registry integration to reduce boilerplate and ensure design compliance.

The immutable ID rule is an enforced compliance check during MCP tool development that ensures safe, testable implementations by preventing identifier modifications across frontend-backend boundaries within the LibrAgent architecture.

Yes, you can validate MCP tool integration across Rust backend and frontend boundaries. This skill provides templates and guidelines to verify seamless operation across proxy and backend components for reliable tool deployment.

Implementing dual-channel responses and recovery hints for MCP tools requires following the enforced governance checks provided by this skill, ensuring safe handler implementations and consistent tool design across the server architecture.

The best way to ensure MCP tool schema definitions comply with the Tool Design Manifesto is to use scaffolding templates that enforce hallucination firewall checks, immutable IDs, and consistent governance throughout the tool creation lifecycle.

Yes, Rust is required for the backend components of a builtin MCP server architecture. This skill helps verify integration across the Rust backend, proxy, and frontend boundaries to ensure seamless operation and testability.