Bluma MCP Server
Hosted Model Context Protocol server on the Bluma API host. Discovered via RFC 9728 OAuth Protected Resource Metadata rather than from the documentation, which never mentions it. Requires an OAuth 2.1 bearer token issued by clerk.getbluma.com; dynamic client registration and PKCE S256 are supported, so a compliant MCP client can bootstrap itself. An anonymous tools/list returns 401 with a spec-correct WWW-Authenticate resource_metadata challenge, so the live tool surface is not publicly readable.