Integrate Corbado Observe as MCP

The Corbado MCP server lets an AI assistant answer questions about your authentication flows with your project’s Observe data: how the login success rate developed, which login methods your users choose and which known problems are still open. It uses the Model Context Protocol. Access is read-only and covers one Observe project per connection.

https://app.corbado.com/mcp

1. Before you start

An Observe project you are a member of. You sign in with your Management Console account when you connect.
Self-registered applications are allowed. Claude, ChatGPT, Codex, Cursor, VS Code and Gemini CLI register themselves when they connect. A project owner allows this once under Observe → Settings → MCP → OAuth applications with Allow self-registered applications. Without it, these assistants can’t connect.

For Microsoft 365 Copilot and other rollouts to a whole organization, see MCP for enterprise platforms.

2. Let your assistant set it up

Most assistants can add the server themselves. Paste this into your assistant:

Add the Corbado MCP server to this assistant. Follow https://docs.corbado.com/corbado-observe/tools/mcp-server

Instructions for AI assistants: The server URL is https://app.corbado.com/mcp (Streamable HTTP). Authentication is OAuth 2.1 with dynamic client registration and PKCE, discovered from the server; no API key, client ID or secret is needed. Use the setup for the user’s client from section 3, then start the sign-in. The user signs in in the browser, picks one Observe project and allows read-only access. Afterwards call get_project to confirm which project is connected. If your client loads new MCP servers only at startup, tell the user to restart it first.

Most assistants load a new server only when they start. Restart the assistant once it has added the server, then sign in.

3. Add the server

In claude.ai or Claude Desktop:

Open Settings → Customize → Connectors.
Select Add → Add custom connector.
Enter the name Corbado Observe and the URL https://app.corbado.com/mcp, then click Add.
Click Connect next to the new connector and sign in.

In Team and Enterprise plans, an owner adds the connector under Organization settings → Connectors first. Members then click Connect.

claude mcp add --transport http corbado https://app.corbado.com/mcp

Then run /mcp in Claude Code, select corbado and choose Authenticate.

In the ChatGPT desktop app:

Open Customize → Plugins.
Select Add → Add custom MCP server.
Enter the name Corbado Observe and the server URL https://app.corbado.com/mcp. ChatGPT discovers the OAuth settings from the server, so leave them as they are.
Create the server. ChatGPT then opens the sign-in.

On chatgpt.com, custom MCP servers need developer mode under Settings → Security and login → Developer mode. In Business and Enterprise workspaces, an admin first allows Create plugins with MCPs, which is off by default.

codex mcp add corbado --url https://app.corbado.com/mcp
codex mcp login corbado

The Codex CLI, IDE extension and Codex in the ChatGPT desktop app share this configuration (~/.codex/config.toml).In the ChatGPT desktop app, you can also add the server under Customize → Plugins → Add → Add custom MCP server, as described in the ChatGPT tab.

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "corbado": {
      "url": "https://app.corbado.com/mcp"
    }
  }
}

Open Cursor Settings → MCP and click the sign-in button next to corbado.

For GitHub Copilot in VS Code, add the server to .vscode/mcp.json:

{
  "servers": {
    "corbado": {
      "type": "http",
      "url": "https://app.corbado.com/mcp"
    }
  }
}

Start the server from the file or with MCP: List Servers and allow the sign-in.

gemini mcp add --transport http corbado https://app.corbado.com/mcp

Then run /mcp auth corbado in Gemini CLI.

Any MCP client works that supports Streamable HTTP, OAuth with dynamic client registration and PKCE. Add https://app.corbado.com/mcp as a remote server. The client finds the sign-in on its own.

Your assistant opens the Management Console in the browser. Sign in with your usual account.

Pick the project

Choose the Observe project the assistant may read. Only projects that allow self-registered applications are listed.

Allow access

Check the assistant’s name and click Allow access. The browser returns to your assistant.

Check the connection

Ask your assistant: “Which Corbado project am I connected to?” It should name the project you picked.

To read another project, add the server a second time under a different name, for example example-staging, and pick the other project when you sign in.

5. What your assistant can access

Three parties take part in a connection: you, your assistant and Corbado. You sign in at Corbado, never in the assistant, so the assistant never sees your password. Corbado then gives the assistant a token with these limits:

One project. The token reads only the project you picked.
Read-only. The assistant can read KPIs and findings. It can’t change settings, data or team members.
Your permissions. The assistant sees what you may see in the project. If you leave the team, the access ends.
Limited in time. Access ends after 30 days, or after 7 days without use. The assistant then asks you to sign in again.

Every member connects with their own account. All connections are listed under Observe → Settings → MCP → OAuth applications. Each member can revoke their own access there, and owners can revoke anyone’s. Observe data contains values recorded from your users’ browsers, such as user agents and error messages. Treat what the assistant derives from them like any other analysis and review suggested actions before you run them.

6. Tools

Tool	What it does	Example question
`get_project`	Names the connected project with its time zone, flow types and custom tags	”Which Corbado project am I connected to?”
`list_kpis`	Lists the KPIs by topic, for example login overview, login methods, passkeys, friction and recovery	”Which passkey KPIs can you measure?”
`query_kpis`	Measures KPIs over a date range as totals or per day, week or month, optionally split by a dimension such as device or browser	”How did the login success rate develop over the last 4 weeks, per week?”
`list_findings`	Lists findings: the root causes of problems in your authentication flows, with type, owner and status	”Which findings are still open?”
`get_finding`	Reads one finding in full: what happens and why, how to reproduce it, the fix options and the last measured impact	”Explain the newest finding and how to fix it.”

The numbers match the Observe dashboards, including your project’s default saved filter.

7. Troubleshooting

What you see	Cause	What to do
”This application can’t be connected yet”	None of your Observe projects allows self-registered applications	Ask a project owner to turn on Allow self-registered applications, then connect again
”You can’t connect this project” or “You have no Observe project to connect”	Your account is not a member of an Observe project	Ask a project owner to invite you
”This connection request has expired”	The sign-in took longer than 10 minutes	Start the connection again from the assistant
”This connection link does not work”	The assistant’s registration was deleted or its request is invalid	Remove the server in the assistant and add it again
The assistant can’t register or connect	The assistant does not support dynamic client registration	Use an application with a client secret, see MCP for enterprise platforms
The assistant reads the wrong project	You picked another project when signing in	Remove the server, add it again and pick the right project
The assistant asks you to sign in again	The access ended after 30 days or 7 days without use, or it was revoked	Sign in again

Still stuck? Write to support@corbado.com with the assistant you use and the exact message.

MCP for enterprise platforms

Roll out the server to your organization with an OAuth application, for example in Microsoft 365 Copilot.

Observe CLI

Scripted access to Observe data from the terminal, also for coding agents.

Overview

Get started

Custom events

Observe for Agents

Developer tools

Monitoring & alerting

Passkey Intelligence

Data access

Security & compliance

Event model

Journey events

Context & enrichment

Integrate Corbado Observe as MCP

1. Before you start

2. Let your assistant set it up

3. Add the server

5. What your assistant can access

6. Tools

7. Troubleshooting

MCP for enterprise platforms

Observe CLI

1. Before you start

2. Let your assistant set it up

3. Add the server

4. Sign in and allow access

5. What your assistant can access

6. Tools

7. Troubleshooting

MCP for enterprise platforms

Observe CLI