What problem does it solve? Developers working on the REDAXO ai_platform addon need accurate knowledge of its MCP server routing, tool registration, scope system, and the fully implemented OAuth 2.1 layer (PKCE, refresh rotation, DCR) to add routes, register tools, or debug remote clients like Claude Desktop without rediscovering known pitfalls. ## Core Features & Use Cases - MCP Architecture Reference: Documents live routes (/mcp, /oauth/*, discovery endpoints), config keys, class topology (Router, Server, Authenticator, Context, Tool), and tool registration with scope-based visibility. - OAuth 2.1 Internals: Covers authorization code + PKCE (S256-only), refresh token rotation with replay protection, Dynamic Client Registration, and the YCom group-to-scope mapping tables. - Remote Client Debugging Playbook: Eleven hard-won lessons for connecting Claude Desktop via ngrok, including baseUrl derivation, arg_separator pitfalls, DCR client_secret_post support, and the ngrok inspector workflow. - Use Case: When a protected tool does not appear in Claude Desktop's tool list, consult the skill to learn about the chicken-and-egg 401 problem and enable mcp_require_auth so OAuth login is triggered. ## Quick Start Ask the assistant to explain how to register a new scope-protected MCP tool in the ai_platform addon and why it might not appear for anonymous callers.