# Connect apps

Connect Gmail, Slack, Notion, GitHub and other apps so bots can read and act in them for you.

## Connect from chat

The easiest way is to ask: "connect my Google Calendar". The bot posts a card in the chat; choose
**Authorize** and finish signing in with the app.

## Connect from Integrations

Choose **Connect apps** at the bottom of the sidebar to open **Integrations**. Under **Browse**,
search or pick a **Category**, choose an app, and then **Connect**. **Connected** lists the apps
you've connected.

Once an app is connected, every bot in the [space](/docs/spaces/) can use it in your chats. You don't
set it up per bot. From an app's page you can **Reconnect** it, **Add account** for a second account,
rename an account, or **Uninstall** it.

Connected apps can also start routines and workflows when something happens in them, such as a new
email. See [When something happens in an app](/docs/routines/#when-something-happens-in-an-app).

A connected Google Calendar is also what [**Join my meetings**](/docs/meetings/#join-my-meetings)
follows. With several, rename the accounts here to tell them apart when you choose one.

In a [team space](/docs/teams/#team-spaces), connections are per person. A shared bot uses the apps of
whoever it's working for, so teammates connect their own and never use yours. MCP servers you add
work the same way. The exception is a Drive [knowledge source](/docs/memory/#knowledge-sources), which
answers everyone in the space through the account of the person who added it.

<!-- self-hosted -->

> [!NOTE]
> The app catalog depends on your server. A self-hosted server shows it only when the operator has
> configured an app catalog. See [Self-hosting](/docs/self-host/). Custom sources, below, work on any
> server.

<!-- /self-hosted -->

## Add your own tools

**Add custom** in **Integrations** adds tools that aren't in the catalog:

- **MCP server**: any remote MCP server at an HTTPS address. **Browse MCP servers** searches a public
  directory of them.
- **OpenAPI** and **GraphQL**: point at an API's description and the bot can call it.
- **Treg** and **Executor**: tool gateways that connect with one access token.
- **From GitHub**: install a plugin from its repository. See [Build a plugin](/docs/build-a-plugin/).

Choose an authentication method (**No authentication**, **Bearer token** or **API key header**)
and then **Verify and add**. Credentials are encrypted and never sent to the model.

**Manage MCP servers** lists every server you've added, with **Test connection**, OAuth sign-in, and
which bots can use each one.

## Choose which bots use what

Bots pick the apps they need. To add an MCP server to the bot you're chatting with, open it in
**Integrations** and choose **Use in this bot**.

When a bot wants a server it hasn't used before, it asks first in the chat. Choose **Approve**, or
**Authorize** if the server needs you to sign in.

## Available in

If you have more than one [space](/docs/spaces/), each skill, MCP server and plugin you add has an
**Available in** choice: **All spaces**, including spaces you create later, or only the spaces you
pick. App connections stay in the space you connected them in.

## APIs without an integration

For a service with only an API key or a website login, ask the bot to save it. See
[Reusable credentials](/docs/bot-secrets/).
