Skip to main content
Each app acts as its own OAuth 2.0 provider, allowing external applications to authenticate users and consume the app’s API.
  • Authorization code flow with PKCE support
  • Pluggable identity providers (Synthetiq, Google, GitHub, any OIDC provider)
  • OAuth client management via the built-in admin UI
  • Token refresh and revocation
Users register OAuth clients on the API & MCP Access page (/settings/oauth-apps), reached from the user menu — this is where you create the client ID and secret an MCP client such as Claude Desktop uses to connect. Admins can manage every OAuth client for the app at /admin/oauth-clients. After creating an OAuth application, the user receives a client ID and client secret. These credentials are used to configure the OAuth flow in whatever third-party tool or service is consuming the app’s HTTP API or MCP server. For a step-by-step walkthrough of connecting a client such as Claude Desktop, see Connect to a Deployed App Over MCP. For more detail on creating and managing OAuth connections in a deployed app, see OAuth connections.