Skip to main content
End-to-end authorization_code + PKCE flow for MCP clients.

1. Dynamic Client Registration

Response:

2. Authorize (end-user redirect)

The user lands on the Glide step-up sheet, authenticates via Privy (Face-ID + email OTP as needed), and authorizes the requested scope+resource binding. Glide redirects back with ?code=...&state=....

3. Token exchange

Response:

4. Call MCP tools

5. Refresh

Refreshing issues a new access token; the old grant’s jti is superseded. Clients MUST track only the latest jti for revocation.

Revocation

Tokens are revoked by the user at app.glide.co/dashboard/agents/:id or by the agent itself via agent.grant.issue (which supersedes the prior grant) / killSwitch.all (global revoke). Grant-wrapper fresh-reads the revoked_at column on every tool call — revocation is MCP-inert within 3s P99.