- A project owner adds an OAuth application in the Management Console and gets a client ID and a client secret.
- An admin of your platform configures the Corbado MCP server for your organization with these values.
- Each person signs in with their own Corbado account and allows read-only access, as described in MCP for AI assistants. The OAuth application only lets the platform start that sign-in. It gives no access by itself.
1. Add an OAuth application
A project owner adds the application under Observe → Settings → MCP → OAuth applications:1
Add the application
Click Add application and enter a name your team recognizes, for example
Microsoft 365 Copilot.2
Enter the redirect URI
Enter the redirect URI of your platform. Its documentation names it, or the platform shows it when you configure the server. If it appears only later, add it afterwards with Edit.
3
Copy client ID and secret
Corbado shows the client secret once. Store it in your platform right away. If it gets lost, create a new one with Regenerate secret.
2. Values for your platform
The Endpoints button on the same page lists these values:
Platforms that read the server metadata find most of these values in
https://app.corbado.com/.well-known/oauth-authorization-server.
3. Example: Microsoft 365 Copilot
In Microsoft 365 Copilot, the Corbado MCP server becomes a custom federated connector. Copilot then reads Observe data live in Copilot Chat, Researcher and Copilot in Word, Excel, PowerPoint and Outlook. Nothing is copied into Microsoft 365. You need:- Admin role: Global Administrator or AI Administrator in the Microsoft 365 admin center
- Developer portal: access to the Teams Developer Portal
- Licenses: a Microsoft 365 Copilot license for every person who uses the connector
1
Add the OAuth application in Corbado
Add an OAuth application as described in section 1 with this redirect URI:
2
Register the OAuth client in the Teams Developer Portal
In the Teams Developer Portal, open Tools → OAuth Client Registration and select + New OAuth connection. Enter:
Turn on Proof Key for Code Exchange (PKCE), which Corbado requires. Select Save and copy the OAuth client registration ID.
3
Create the connector in the Microsoft 365 admin center
In the Microsoft 365 admin center, open Copilot → Connectors and the Gallery tab. Under Created by your org, select Add on the Create a new connector tile. On the Custom connector page, select Add under Connect to MCP server and enter:
Select Save.
4
Roll it out
The connector appears under Copilot → Connectors → Your connections. Use Staged rollout to start with a test group, then Deploy to all users. Custom connectors also depend on Allow agents and plugins built by your organization under Agents → Settings → Agent and plugin access. Changes can take up to 10 minutes.
5
Connect as a user
In Microsoft 365 Copilot Chat, open … → Settings → Sources, select Connect next to Corbado Observe and sign in with your Corbado account. Then ask: “Which Corbado project am I connected to?”
4. Control and revoke access
All applications and everyone who connected through them are listed under Observe → Settings → MCP → OAuth applications. Owners can revoke one person’s access, revoke all access of an application or delete the application. Access is read-only, follows each person’s project permissions and ends after 30 days, or after 7 days without use. To allow only the applications your owners added, turn off Allow self-registered applications on the same page. Assistants that register themselves then can’t connect to this project.MCP for AI assistants
Setup for Claude, ChatGPT, Codex, Cursor, VS Code and Gemini CLI, with tools and troubleshooting.
Management Console access
Who can sign in and what each role may do.