Connect Grokbot to Verbial
Connect Grokbot with your own account, choose what it can read, and verify the connection before it touches business data.
Connect Grokbot 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. The same URL works for Grokbot.
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 Grokbot
- Go to grok.com/connectors and select New Connector → Custom.
- Name it Verbial and paste the workspace URL.
- Choose OAuth. Leave any client ID and secret fields empty, and do not select an option that skips authentication.
- Sign in to Verbial and review the access it asks for.
- Enable Verbial in the conversation where you want to use it.
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 connection in Grokbot, 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 connect with OAuth, 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.
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.
Common questions
Do I need an API token?
No. Grokbot signs in with OAuth using your own Verbial account. A personal token is only a fallback for clients that cannot use OAuth.
Can Grokbot 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.
Does my whole team share one connection?
No. Each person connects with their own identity and sees only what they can already see in Verbial.
Can Grokbot change data?
Writes are off by default. A write needs your normal permission, the relevant MCP categories and write access. Leave writes off unless you need them.