Any OpenID Connect library

Standard OIDC with discovery. Point any certified client library at the issuer.

Register the app first: ask your agent, or create a web app in the dashboard with redirect URI http://localhost:3000/auth/callback.

  1. Settings for your library

    text
    Issuer / discovery:  https://yourself.mees.sh/.well-known/openid-configuration
    Client ID:           app_…
    Client secret:       ysec_… (shown once when the app was created; rotate it if lost)  (web apps only)
    Redirect URI:        http://localhost:3000/auth/callback
    Scopes:              openid profile email   (add offline_access for refresh tokens)
    Response type:       code, with PKCE (S256)
    Token auth:          client_secret_basic or client_secret_post (web), none (spa/native)
  2. What you get back

    • ID token: ES256 JWT, 1 hour. Claims: iss, sub, aud (= client ID), exp, iat, auth_time, nonce, plus name (profile) and email, email_verified: false (email).
    • Access token: ES256 JWT with typ: at+jwt, aud = client ID, 1 hour. Use it for /userinfo or your own API.
    • Refresh token: with offline_access. Rotated on every use; reusing an old one revokes the whole sign-in.
    • Sign out everywhere: send the browser to https://yourself.mees.sh/logout?client_id=app_…&post_logout_redirect_uri=… (the URI must be registered as a post-logout redirect URI).
  3. Rules the server enforces

    • Only the account that owns the app can sign in. Anyone else sees an error and no code is issued.
    • Redirect URIs must match exactly. http://localhost and http://127.0.0.1 match on any port.
    • PKCE is required for spa and native apps, and recommended for web apps.
    • Authorization codes last 60 seconds and work once. Responses include iss (RFC 9207).
  4. Check it works

    Start the app and open it. You're sent to yourself, sign in with your passkey, and land back in the app signed in. The list_activity MCP tool (or the dashboard) shows an app.signed_in event.