Craft CMS 5.12.0: Added an authenticated HTTP MCP server Craft CMS 5.12.0 added an authenticated HTTP MCP server that MCP clients can connect to after a user signs in and authorizes them via OAuth, with clients acting as that user within their permissions and a granted access level of read only, read and write, or full access for admins. The release also adds a public HTTP MCP server exposing only capabilities and content approved from Settings → MCP, discoverable via /.well-known/ai-catalog.json and a Server Card at /server-card per SEP-2127, plus an OAuth authorization server with PKCE and refresh token rotation and a My Account → Tokens screen for managing personal access tokens and authorized MCP clients. Dynamic OAuth client registration is limited to 10 clients per IP address per hour by default via the new registrationRateLimit and registrationRateLimitDuration settings. You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert Added an authenticated HTTP MCP server, which MCP clients can connect to after a user signs in and authorizes them via OAuth. Clients act as that user, within their permissions and the access level they grant read only, read and write, or full access for admins . 20145, 20189 The authenticated MCP server’s endpoints default to /{cpTrigger}/mcp and /{cpTrigger}/mcp/auth, or /mcp and /mcp/auth when public registration is enabled. Endpoints within the control panel can only be used by users with control panel access. 20189 Added a public HTTP MCP server, which exposes only the capabilities and content approved from Settings → MCP, without signing in. Its endpoint defaults to /mcp. 20145, 20189 The HTTP MCP servers are discoverable via /.well-known/ai-catalog.json and a Server Card at