Sign in
mcp

Callback

OAuth 2.0 authorization response handler for MCP loopback clients.

Accepts either:

  • A successful authorization response (code + state), which is forwarded back to the validated client redirect_uri with the original (un-wrapped) state.
  • An error response (error[+error_description/error_uri]), per RFC 6749 §4.1.2.1. When state is present and decodes to a trusted redirect_uri, the error params are propagated back to the client so its OAuth library can surface them. Otherwise we render an HTML error page so the user is not left on an opaque 422 / blank screen.
get/callback

Query parameters

codestring nullable
statestring nullable
errorstring nullable
error_descriptionstring nullable
error_uristring nullable

Response

Successful Response

{"stackTrail":"paths:/callback:get:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes