Connect Claude, Codex or ChatGPT to Verbial

Connect your assistant directly to Verbial and choose what it can access. Use your own account for each workspace. You do not need to run a server on your computer or share an administrator's credentials.

1. Set permissions and copy your workspace URL

1. Sign in to the workspace you want to connect.
2. Open Settings → My API Tokens → MCP permissions.
3. Save the categories you want to allow. Financial data, communications, configuration and writes are off by default.
4. Open Settings → Developer → AI assistants (MCP) and copy the exact MCP URL shown there. Use that URL in the instructions below. Connect different workspaces separately.

These choices restrict all your personal tokens and OAuth connections in this workspace. They never grant access beyond your current role and record permissions. With financial access off, entire tools that mix amounts with other data can be unavailable, including detailed records, reports and message content.

Privacy mode only blurs your screen. Use MCP permissions to restrict assistant access. A permission change cannot erase data already returned to a conversation.

2. Choose your client

Claude Desktop, Cowork or claude.ai

1. Open Customize → Connectors → + → Add custom connector.
2. Name it Verbial and paste the workspace URL.
3. Leave advanced OAuth client ID and secret fields empty. Add the connector, select Connect, then sign in to Verbial and review access.
4. Enable Verbial from the conversation's connector menu.

In a managed Claude workspace, an owner may need to add the connector first. Each teammate then signs in individually. Remote connectors belong to your Claude account; a local Desktop configuration is a different connection.

Codex app or CLI

In MCP settings, add a remote HTTP server with your workspace URL and sign in using OAuth. With the CLI, replace YOUR_WORKSPACE_MCP_URL below with the URL you copied:

codex mcp add verbial --url YOUR_WORKSPACE_MCP_URL
codex mcp login verbial

The add command may start sign-in automatically. Use login if authentication has not completed. Start a new task so the tools load. If Codex runs on a remote machine, configure and authenticate that host separately.

ChatGPT on the web

ChatGPT needs its own connection, separate from Codex.

1. If your account allows it, enable Developer mode in Settings → Security and login.
2. Open Plugins, select +, and create a developer-mode app for your MCP server.
3. Enter the workspace URL and choose OAuth with dynamic client registration (DCR). Leave client ID and secret empty. Do not select No Authentication.
4. Sign in to Verbial and review access.
5. Select the app in the conversation's Developer mode menu.

If these controls are missing, check availability with your ChatGPT workspace owner. No paid upgrade is required by these instructions; availability depends on the client's plan and administrator settings.

Claude Code

You may already see your Claude web connector in /mcp when signed in with the same Claude subscription. Otherwise add it directly:

claude mcp add --transport http --scope user verbial YOUR_WORKSPACE_MCP_URL

Run /mcp and authenticate the server. This direct CLI configuration is separate from the web connector.

3. Verify before reading business data

Ask:

Use Verbial to call verbial_whoami and confirm my account. Do not read other records or make changes.

Confirm it identifies your own account. With financial access off, invoice and financial report tools should be unavailable, including attempts to call old tool names. Missing tools can also reflect your role, enabled modules or workspace plan. After a permissions change, refresh the client's tool list or start a new conversation.

Replace an old local connection

Verify the remote connection first. Then disable or remove the old local Omni or Verbial entry so your assistant does not choose the wrong server. If its old personal token is no longer needed, revoke it in My API Tokens. Removing configuration alone does not revoke credentials.

For a client that cannot use OAuth, create a personal token and put it only in that client's secure bearer-credential field. Never paste a token into chat, a support ticket or a shared configuration file. Lost token secrets cannot be recovered; revoke and replace them.

Disconnect and troubleshoot

• Stop access: disconnect the OAuth connection or revoke its personal token in My API Tokens. Disable MCP to stop all your MCP credentials in that workspace.
• Registration failed: recopy the exact workspace URL and use OAuth/DCR without a manually entered secret. Ask support if registration still fails; do not disable authentication.
• Sign-in expired: reconnect using your own Verbial account.
• Wrong identity: disconnect before reading records and sign in as the correct user. Do not share another user's token.
• Old Omni labels: refresh the connection’s tool catalog or reconnect after the updated server is available. New labels use Verbial and explain the action; historical names remain compatible without extra access.
• Tools missing: check saved MCP permissions, your normal access and workspace features. The connector exposes a selected tool set, not every Verbial page.

Client labels change over time. These instructions were checked against the official Claude connector guide, Claude Code guide, Codex MCP guide, and ChatGPT developer-mode guide on September 17, 2026.