Chat connectors
Connect accounts and compatible remote MCP servers to LLMBase Chat, then choose where they are available.
Updated
Chat connectors let LLMBase Chat work with accounts you connect through OAuth. Each connected account is stored as a separate connector instance, so you can connect more than one Gmail or Google Calendar account and choose which accounts are available in a personal chat or workspace.
Connectors are available to signed-in Chat Pro users. Account credentials are encrypted and are not stored on chat sessions.
Available connectors
| Connector | Status | What it can do |
|---|---|---|
| Gmail | Available | Search and read messages, send email after confirmation, archive messages, and move messages to trash. |
| Google Calendar | Available | List, search, create, update, and delete calendar events. |
| Custom MCP | Available | Connect compatible remote MCP tools through HTTPS, Streamable HTTP, and OAuth. |
GitHub, Notion, Slack, and Linear are not currently visible in the connector picker.
Connect an account
- Open Chat.
- Open the connector modal from the chat controls.
- Choose Gmail or Google Calendar.
- Select Connect.
- Complete Google consent.
- Return to Chat and confirm that the connected account is selected for the current chat or workspace.
If you connect multiple accounts for the same connector, each account appears as its own row. Select the accounts you want the model to use in the current scope.
Add a remote MCP server
- Choose Custom MCP, then Connect.
- Enter a name and the server’s public HTTPS MCP endpoint.
- Complete the server’s OAuth authorization.
- Open Manage tools and keep only the tools you need.
Custom servers must support Streamable HTTP, OAuth, PKCE, and dynamic client registration. URLs cannot contain credentials, query parameters, private-network hosts, or custom ports. LLMBase limits each connection to 32 tools and requires approval before every custom MCP action.
Tool descriptions and results come from the external server. Review the server and its requested permissions before authorizing it. Disabling unused tools also reduces the context and processing needed for each chat.
Personal chat and workspace scope
Connector selection is scoped:
| Scope | Meaning |
|---|---|
| Personal chat | The selected accounts are available only in that chat context. |
| Workspace | The selected accounts are available to workspace chat under workspace policy. |
Credentials belong to the connected account owner. Enabling a connector in one scope does not copy OAuth tokens into that chat or workspace.
Confirming actions
LLMBase asks for confirmation before actions that can send, delete, trash, archive, close, cancel, or otherwise change external data in a meaningful way. Read-only searches and ordinary create/update operations can run directly when the connector is enabled.
For Gmail, delete-like behavior moves messages to trash. LLMBase does not permanently delete Gmail messages.
Reconnect or disconnect
Use the connector modal to rename, reconnect, or disconnect an account. Reconnect is shown when an account needs fresh OAuth consent. Disconnect removes that account instance from future connector use.
Troubleshooting
If a connector is unavailable:
- Confirm you are signed in with a Chat Pro account.
- Confirm the account is selected for the current chat or workspace.
- Reconnect the account if the modal shows a reconnect warning.
- Try a model that supports tools.
If Google denies access, the Google account or workspace admin may have blocked the requested Gmail or Calendar scopes.