> ## Documentation Index
> Fetch the complete documentation index at: https://developers.webai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Link Google, Slack, GitLab, Jira, and custom MCP servers so the assistant can use them in Chat.

export const ConnectorsFaq = () => <AccordionGroup>
    <Accordion title="Why don't I see the Connectors tab?">
      Open <strong>Settings → Integrations → Connectors</strong>.
    </Accordion>
    <Accordion title="Why are Connected tools greyed out or unavailable?">
      Common causes: <strong>Online</strong> is off, you are offline or have no network, the loaded model is below about 8B or does not support tool calling, or no services or MCP servers are connected yet.
    </Accordion>
    <Accordion title="I connected a tool but the model says it doesn't have access">
      Connected tools need a capable model (about <strong>8B parameters or larger</strong>) that supports tool calling. Smaller models answer from local knowledge and may say they cannot reach your calendar, email, or other connected services even when a connector is set up. Load a larger model in <strong>Settings → Model</strong>, then confirm <strong>Online</strong> and <strong>Connected tools</strong> are on and ask again. See <a href="/settings/model">Model</a> for more questions about choosing and loading a capable model.
    </Accordion>
    <Accordion title="I connected Google or Slack but the assistant still doesn't use them">
      Check that <strong>Online</strong> and <strong>Connected tools</strong> are on, that a capable model is loaded, and that your prompt clearly needs that service. Try asking for a specific mailbox, calendar, or workspace action.
    </Accordion>
    <Accordion title="What's the difference between Web search and Connected tools?">
      <strong>Web search</strong> looks up current public information on the web. <strong>Connected tools</strong> send relevant requests to <strong>your</strong> connected accounts and MCP servers. You can use either or both under <strong>Online</strong>.
    </Accordion>
    <Accordion title="Are my credentials safe?">
      Connection tokens and MCP secrets are stored <strong>locally on your device</strong> (including the system keychain for MCP credentials), not in the webview. You can disconnect a service or remove an MCP server to revoke access from webAI.
    </Accordion>
    <Accordion title="Why am I asked to allow a tool action?">
      Write tools that create or change data pause for confirmation. You can allow once, deny, or remember a preference per tool under <strong>Tool approvals</strong> in <strong>Settings → Integrations → Connectors</strong>.
    </Accordion>
    <Accordion title="An approval prompt disappeared or the tool didn't run">
      If you wait too long, the pending action times out and is treated as cancelled or denied. Check <strong>Action history</strong>, then try again.
    </Accordion>
    <Accordion title="What does &quot;Requires OAuth — not supported yet&quot; mean on an MCP server?">
      That custom MCP server expects an OAuth login flow that the desktop app does not support yet. Use a server that works with a URL token or header, or a local command setup instead, or wait for OAuth support.
    </Accordion>
    <Accordion title="Can I add my own tools?">
      Yes. Power users can add <strong>MCP servers</strong> (Remote HTTP or Local command) under <strong>Connectors</strong>. Those tools appear to the model alongside built-in connector tools when <strong>Connected tools</strong> is on.
    </Accordion>
    <Accordion title="Do Google and Slack let the assistant send email or post messages?">
      Built-in Google and Slack connectors are described as <strong>read-only</strong> (search and read). Prefer write-capable custom MCP tools or other services when you intentionally allow write approvals.
    </Accordion>
    <Accordion title="Why did a scheduled task say I need to connect Google or enable tools?">
      Scheduled work that depends on specific connectors will not start until those integrations are connected and the desktop tool stack is ready. See <a href="/using-webai/scheduled-tasks">Scheduled Tasks</a> for setup, templates, and troubleshooting.
    </Accordion>
  </AccordionGroup>;

**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](/using-webai/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

<Steps>
  <Step title="Open Connectors">
    Open **Settings**, then under **Integrations** open the **Connectors** tab.
  </Step>

  <Step title="Connect a built-in service">
    Under **Connected services**, choose a service and follow its connection flow. Use **Disconnect** later to remove a link.
  </Step>

  <Step title="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).
  </Step>
</Steps>

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

| Service    | What it enables (typical)                                          | How you connect                                                   |
| ---------- | ------------------------------------------------------------------ | ----------------------------------------------------------------- |
| **Google** | Calendar, Drive, Gmail, and Meet access described as **read-only** | Sign in with **Connect** (browser/OAuth flow)                     |
| **Slack**  | Workspace messages and search described as **read-only**           | Sign in with **Connect** (OAuth)                                  |
| **GitLab** | Search and read issues, merge requests, and project activity       | Provide project path and a personal access token with read access |
| **Jira**   | Search projects, issues, and activity                              | Provide site URL, account email, and API token                    |

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.

<Steps>
  <Step title="Turn Online on">
    In [Chat](/using-webai/chat), open the **Online** controls and turn **Online** on.
  </Step>

  <Step title="Enable Connected tools">
    Enable **Connected tools**. Optionally keep **Web search** on or off. It is independent of Connectors.
  </Step>

  <Step title="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."
  </Step>
</Steps>

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.

<Note>
  When **Online** is on, web search and connected tools can send data off your device. See the [Privacy Policy](https://www.webai.com/privacy) for how that data is handled.
</Note>

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](/using-webai/chat#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

<Steps>
  <Step title="Open MCP servers">
    Open **Settings → Integrations → Connectors**, then in **MCP servers** choose **Add server**.
  </Step>

  <Step title="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
  </Step>

  <Step title="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**.
  </Step>
</Steps>

### 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

| Restriction                  | What you should know                                                                                                                                                      |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Capable model**            | Connected tools need roughly an **8B+** model with tool calling. Smaller models will not use connectors.                                                                  |
| **Online + Connected tools** | External connector tools run when **Online** is on and **Connected tools** is enabled for the chat.                                                                       |
| **Network**                  | Online mode needs internet connectivity for web search and most connected services.                                                                                       |
| **Read-only built-ins**      | Google and Slack integrations are described as **read-only** (search and read).                                                                                           |
| **Secrets on device**        | Tokens and MCP credentials stay on your device (system keychain and local storage), under your control.                                                                   |
| **Write confirmation**       | Tools that modify data can require explicit approval.                                                                                                                     |
| **Approval timeout**         | Ignoring an approval prompt for too long cancels the action.                                                                                                              |
| **Web search vs Connectors** | **Web search** is separate under **Online**; it does not require a Connectors setup.                                                                                      |
| **Personas / isolation**     | Some chat modes (for example connected-persona turns) may suppress MCP or connected tools so those sessions stay isolated.                                                |
| **Scheduled tasks**          | Tasks that depend on Google or other tools may fail readiness until the matching connector and tool stack is set up. See [Scheduled Tasks](/using-webai/scheduled-tasks). |

## Common questions

<ConnectorsFaq />

<Note>
  More answers are in the [FAQ](/support/faq#connectors).
</Note>