Skip to main content
Connectors let webAI link third-party accounts and external tool servers so the assistant can use them while you chat. For example, you can search your calendar or email, read Slack or project trackers, or call tools from a custom MCP server.

​
Overview

Connectors are integrations that give the assistant access to tools from services you authorize. Once connected and enabled for a chat, the model can call those tools when your request needs them. In webAI you will see related labels such as:
  • Connectors: the Settings area where you manage connections
  • Connected services: built-in account integrations (Google, Slack, GitLab, Jira)
  • Connected tools: the chat toggle that allows the assistant to use those integrations
  • MCP servers: optional custom tool servers for advanced setups
MCP (Model Context Protocol) is the standard way external tool servers expose capabilities to the assistant. Most people only need the built-in connectors. Power users can add their own MCP servers under the same Connectors settings. Scheduled Tasks use Connectors when a saved prompt needs Gmail, Google Calendar, or other connected services. Connectors set up the services; Scheduled Tasks run the prompt on a timetable and store results in a dedicated conversation.

​
Requirements

Before you use Connectors in chat, confirm the following:
  • At least one service or MCP server is connected under Settings → Integrations → Connectors.
  • A capable model is loaded (about 8B parameters or larger) that supports tool use. Smaller models answer without connected tools.
  • Online is on and Connected tools is enabled for the conversation.
  • You have an internet connection when using Online features that reach external services.

​
Connect a service

1

Open Connectors

Open Settings, then under Integrations open the Connectors tab.
2

Connect a built-in service

Under Connected services, choose a service and follow its connection flow. Use Disconnect later to remove a link.
3

Optional: open from chat

From chat, you can also open Connectors via the Online controls by choosing Connect tools (wording may appear as Connect tools or Connected tools depending on context).
The Connectors tab typically includes:
  • Connected services: Google, Slack, GitLab, Jira
  • MCP servers: add and manage custom tool servers
  • Tool approvals: control confirmation for tools that change data
  • Action history: recent tool attempts on this device

​
Built-in connected services

Status labels you may see: Connected, Not connected, Not configured, Needs attention, Loading. Disconnect removes the link for that service. For token-based services, clearing credentials stops further tool use until you reconnect.

​
Use Connected tools in chat

Connectors do not run on every message by themselves. You turn them on for the conversation, then ask naturally.
1

Turn Online on

In Chat, open the Online controls and turn Online on.
2

Enable Connected tools

Enable Connected tools. Optionally keep Web search on or off. It is independent of Connectors.
3

Ask in plain language

Ask for something that needs a connected service. Examples: “What’s on my calendar tomorrow afternoon?” or “Find recent Slack threads about the launch.”
Status examples you may see:
  • Offline · On Device: local knowledge only; no external requests
  • Online · Connected tools
  • Online · Web search
  • Online · Web search & Connected tools
When Online is on and Connected tools is enabled, relevant requests may be shared with the services you connected. When Offline, the assistant stays on-device and does not call connected services.
When Online is on, web search and connected tools can send data off your device. See the Privacy Policy for how that data is handled.
While tools run, chat may show progress such as Running…, Ran…, or Failed… for a named action. Each answer also shows which tools were selected and run. See Streaming replies and tools.

​
Example prompts

  • “What’s on my calendar tomorrow afternoon?”
  • “Find recent Slack threads about the launch.”
  • “Summarize open GitLab merge requests in this project.”
  • “Search Jira for bugs tagged regression.”

​
Approvals and action history

Some tools read data. Others create or change data (write tools). Write tools can pause with Allow tool action?. Choose Allow or Deny, and optionally Remember this decision for that tool. In Settings → Integrations → Connectors → Tool approvals, you can set each write tool to Ask each time, Always allow, or Always deny. A session-level Require approval for write tools switch may reset when you restart the app; per-tool remembered choices are kept. If you do not respond to an approval prompt in time (on the order of a couple of minutes), the action is treated as cancelled or denied. Action history lists recent tool attempts on this device (success, failure, rejected, cancelled), including whether the action was read or write. Use it to audit what ran.

​
Custom MCP servers

Under Connectors → MCP servers, you can connect external tool servers. Their tools are indexed alongside built-in connector tools and offered to the model when relevant. Credentials for MCP servers are stored in the system keychain, not in the browser or webview.

​
Add a server

1

Open MCP servers

Open Settings → Integrations → Connectors, then in MCP servers choose Add server.
2

Configure the server

Give the server a name and choose a transport:
  • Remote (HTTP): server URL, plus optional auth token or header as needed
  • Local command: a command the desktop app runs locally, with arguments and environment variables as needed
3

Save and enable

Save, then enable the server. You should see status such as Ready (with a tool count), Syncing…, Unavailable, Not syncing, or Disabled.

​
Manage servers

  • Enable / disable a server without deleting it.
  • Remove a server to drop its tools and delete stored secrets for that server.
  • To change transport type (HTTP to local, or the reverse), remove the server and add it again.
  • Optional Improve all with AI can refine tool descriptions when a capable (8B+) model is loaded.

​
MCP limitations

  • MCP servers that require OAuth may show Requires OAuth — not supported yet.
  • Tools that need the network are unavailable when the chat is Offline or Connected tools is off.
  • Remote servers must be reachable from your machine; local command servers must start successfully on this device.

​
Limitations

​
Common questions

More answers are in the FAQ.