Back to Docs
MCP

Connectors (OAuth)

Connect Claude and ChatGPT to Vaybel with a one-click sign-in — approve access on the consent screen, then manage connected apps from Settings.

Updated 2026-09-07

A connector links an AI assistant to your Vaybel workspace with a one-click sign-in instead of a pasted token. You approve access on a Vaybel consent screen, choose which workspace the assistant can act in, and the assistant stays connected until you revoke it.

Connectors are the right path for Claude (Claude.ai and Claude Desktop) and ChatGPT. Developer clients — Claude Code, Cursor, and Codex — keep using a Personal Access Token; see Quickstart and Authentication & Scopes.

Plan requirement

MCP tools run on Starter or higher. You can connect a Free workspace, but tool calls stay locked until you upgrade.

Connect Claude

Step

Open the connector settings

In Claude, go to Settings → Connectors → Add custom connector.

Step

Point it at the Vaybel MCP server

Set the URL to https://mcp.vaybel.com/.

Step

Sign in and approve

Sign in to Vaybel when prompted. On the consent screen, pick the workspace and the access you want to grant, then choose Allow access. Claude returns to its own window, connected.

Connect ChatGPT

Step

Open developer mode

Enable developer mode, then open Connectors → Create.

Step

Add the server

Set the URL to https://mcp.vaybel.com/ and choose OAuth as the authentication method.

Step

Sign in and approve

Sign in to Vaybel and approve access on the consent screen. ChatGPT completes the connection and can call Vaybel tools.

When an assistant sends you to Vaybel, the consent screen shows who is asking and exactly what you're granting:

  • Workspace — the organization the connection can act in. The assistant can only touch the workspace you choose here. If you belong to more than one, pick the right one before approving.
  • Access requested — the scopes the assistant asked for, grouped into read and write access, each pre-checked. Uncheck anything you'd rather not grant.
  • Stay connected — present when the assistant needs to keep working after you close the tab. It stays granted for the life of the connection.

The screen also names where you'll be sent back to after you decide. Choose Deny to cancel without granting anything.

Manage or revoke a connection

Every connection you approve appears under Dashboard → Settings → API & MCP → Connected apps, with the app name, how many scopes it holds, who connected it, and when it was last used.

Step

Open Connected apps

Go to Dashboard → Settings → API & MCP and find the Connected apps list.

Step

Revoke

Click Revoke next to the app and confirm. Its access ends immediately and it has to be reconnected to work again.

Revoke vs. tokens

Revoking a connected app doesn't touch your Personal Access Tokens, and revoking a token doesn't touch your connectors. They're managed separately on the same settings page.

Developer clients still use tokens

Claude Code, Cursor, and Codex don't use the connector flow — they read a Personal Access Token from local config. Create one under Dashboard → Settings → API & MCP, then follow the per-client setup in the Quickstart.