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
QAuth is the open-source, self-hostable OAuth 2.1 authorization server for MCP
servers and AI agents (see ADR-007). This
is the entry point to the guides; the canonical, always-current API surface is the
interactive Swagger UI at /docs on any running instance.
🎉 June 2026 — MVP complete and the agent-native authorization layer shipped (agent client type, RFC 8693 on-behalf-of delegation, scope modes, step-up, per-agent audit), alongside the T3 production-hardening track and the T5 environment-aware authorization posture (ADR-008). Start with the agent-authorization guide.
End-to-end: run QAuth, run a mcp-guard-protected MCP resource server, and complete the full discovery → register → authorization_code + PKCE → token handshake. Start here.
How token verifiers behave during the ADR-005 hybrid (Ed25519 + ML-DSA-65) rollout: the mixed OKP+AKP JWKS, the reference-token/introspection delivery default, the draft-revision churn risk, and a migration checklist. No action is required for classical Ed25519-only verifiers.
Hand-written contract for every endpoint: first-party auth (/auth/*), OAuth 2.1 (/oauth/*), discovery, and client management (/api/clients), with request/response shapes, status codes, and the error envelope.
The authoritative, always-current surface is the live OpenAPI / Swagger UI at
/docs on the running instance. Also:
Operator/how-to guide: the environment (development / staging / production) policy dimension on clients/realms, the profile table, fail-safe defaults, and environment-gated developer API keys (T5).