Connect ChatGPT to Verbial
Connect ChatGPT with your own account, choose what it can read, and verify the connection before it touches business data.
Connect ChatGPT to Verbial with your own account and choose what it can reach. Nothing runs on your computer, and you never share an administrator's credentials.
1. Set permissions and copy your workspace URL
- Sign in to the workspace you want to connect.
- Open Settings → My API Tokens → MCP permissions.
- Save the categories you want to allow. Financial data, communications, configuration and writes are off by default.
- Open Settings → Developer → AI assistants (MCP) and copy the exact MCP URL shown there.
These choices apply to every personal token and OAuth connection you hold in this workspace. They never grant access beyond your current role and record permissions. A permission change cannot erase what a conversation has already been told.
2. Add the connection in ChatGPT
- If your account allows it, enable Developer mode in Settings → Security and login.
- Open Plugins, select +, and create a developer-mode app for your MCP server.
- Enter the workspace URL and choose OAuth with dynamic client registration (DCR). Leave client ID and secret empty. Do not select No Authentication.
- Sign in to Verbial and review the access it asks for.
- Select the app in the conversation's Developer mode menu.
Connect each workspace separately. Every teammate connects with their own identity.
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 names your own account. With financial access off, invoice and financial report tools should be unavailable. Missing tools can also reflect your role, your enabled modules or your workspace plan. After changing permissions, refresh the tool list or start a new conversation.
Disconnect and troubleshoot
- Stop access: remove the app in ChatGPT, then disconnect the OAuth connection in My API Tokens. Disabling MCP stops all your MCP credentials in that workspace at once.
- Registration failed: recopy the exact workspace URL and use OAuth with DCR, without a manually entered secret. Do not disable authentication.
- Sign-in expired: reconnect with your own Verbial account.
- Wrong identity: disconnect before reading records, then sign in as the correct user.
- Tools missing: check your saved MCP permissions, your normal access and your workspace features. The connection exposes a selected tool set, not every Verbial page.
Codex and Claude connect differently. See Connect Claude, Codex or ChatGPT for those clients.
Common questions
Is this the same connection as Codex?
No. ChatGPT on the web and the Codex app each need their own connection, even on the same OpenAI account. Setting up one does not set up the other.
Do I need an API token?
No. ChatGPT signs in with OAuth using your own Verbial account. A personal token is only a fallback for clients that cannot use OAuth.
Can ChatGPT see money?
Only if you allow it. Financial access is off by default under Settings → My API Tokens → MCP permissions, and reports that mix amounts with other data are withheld too.
Why are the developer-mode controls missing?
Availability depends on your ChatGPT plan and your workspace administrator's settings. Ask your ChatGPT workspace owner.