Overview

MCP Configs is where you connect external tools and services that your bots can use.

In simple terms, an MCP connection links your bot to a tool such as:

  • Gmail
  • Notion
  • Google Calendar
  • Google Sheets
  • Slack
  • GitHub
  • Google Drive
  • Google Docs
  • HubSpot
  • Airtable
  • Supabase
  • Outlook
  • Perplexity AI
  • And many other available tools

Each connection can have its own name and a specific set of tools or actions that the bot is allowed to use.

Why use MCP Configs?

MCP connections allow your bot to do more than simply generate answers.

For example, a bot connected to Gmail could work with emails, while a bot connected to Google Calendar could work with calendar-related actions.

The important idea is:

MCP Configs connect your bot to external tools and control which actions from those tools are available.


Understanding the MCP Configs Screen

The screen has three main areas:

Area Purpose
CONNECTED TOOLS Shows tools that have already been connected
Integrations library Shows tools that can be connected
Right-side panel Lets you name a connection and select the tools/actions it can use

This separation makes it easier to distinguish between tools you already use and tools that are available to add.


Connected Tools

CONNECTED TOOLS contains the MCP connections that have already been configured.

Each connection shows:

  • Connection name
  • Connection status
  • A pause/play control
  • A short connection identifier

Example

You might have:

Connection Status
Support Gmail Connected
Company Notion Connected
Sales Calendar Disconnected

The connection name is chosen by you, so you can make it meaningful to your team.


Connection Names

A connection name helps you identify a specific connection.

This becomes especially useful when you have multiple connections to the same type of service.

For example, instead of having:

  • Gmail
  • Gmail

you could name them:

  • Support Inbox
  • Sales Inbox

Similarly, two Notion connections could be named:

  • Product Notion
  • Internal Notion

Best practice

Use names that describe the purpose of the connection rather than simply repeating the service name.

Good examples:

  • Customer Support Gmail
  • Sales Calendar
  • Product Documentation
  • Marketing Slack

Connected and Disconnected Status

Every connection has a status:

  • Connected
  • Disconnected

Connected

A connected tool is available as an active MCP connection.

Disconnected

A disconnected tool is paused and is not currently active.

Disconnected connections remain in the system, so you can reconnect them later without necessarily creating a new configuration.


Pause and Resume a Connection

You can temporarily disconnect a tool without deleting its configuration.

Pause a connection

Pausing changes the connection from:

Connected → Disconnected

Resume a connection

Turning it back on changes:

Disconnected → Connected

The status change is saved immediately.

You do not need to use Save Changes for this operation.

When to pause a connection

Pausing can be useful when:

  • A tool is temporarily not needed
  • You want to prevent a bot from using a particular integration for a while
  • You want to keep the configuration but temporarily disable the connection
  • You are testing a different setup

Example

You have two Notion connections:

  • Product Notion
  • Internal Notion

If Internal Notion should temporarily not be available, disconnect it while keeping Product Notion connected.