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

# Integrations

> Connect your newsletter tool and the other services your AI teammates work with

An integration gives your AI teammates tools — a way to search the web, read your support inbox, publish a page, or
generate an image. BoostGPT speaks the **Model Context Protocol (MCP)**, so a connection is a set of tools your
AI teammates can call, described well enough for them to know when to reach for one.

> [!NOTE]
>
> Starting a newsletter? Connect your [newsletter tool](/docs/newsletter/tools.md) first: it's how signups
> reach your list and how Mira drafts each issue.

## Three ways to connect

> [card] [Managed connectors](/docs/integrations/connectors/overview.md)
>
> BoostGPT builds and maintains these. Enter one credential; when a vendor changes an endpoint, that is ours
> to fix.

> [card] [Remote MCP servers](/docs/integrations/remote-mcp.md)
>
> The vendor runs the server. You sign in and approve access — there is no key to paste and no app to register.

> [card] [Bring your own](/docs/integrations/custom/overview.md)
>
> An OpenAPI specification, a Postman collection, or the address of any MCP server.

## Grouped by what they are for

Both catalogues are grouped by the loop BoostGPT works in, rather than alphabetically:

| | |
| - | - |
| **Build** | Make images, video and voice for the site — and know what shipped |
| **Talk** | Reach the audience |
| **Learn** | Research what people search for, and what customers keep asking |
| **Improve** | Work on the site itself |

The featured entries in each group are the ones that change what the Site says or what the Widget answers.
Everything else is one click away under **Show more**.

## Connecting one

**1. Connect it once, for the workspace**

**Connectors** in the dashboard. A credential you enter is checked against the vendor before anything is
saved, and a server that signs in is saved only once the sign-in succeeds — so a connection that exists is
one that works.

**2. Give it to the AI teammates that need it**

Each AI teammate has their own **Connectors** tab. A connection is shared, so adding it to a second AI teammate asks for
no credential; switching a tool off for one AI teammate does not touch another.

**3. Decide what needs asking first**

Every connection carries an approval setting — every time, never, or per tool. An AI teammate can always ask more
often than you set, never less.

> [!NOTE]
>
> Two connectors need no setup at all: **Serper** for web search and **Pexels** for photography are funded by
> BoostGPT and attached to a new AI teammate automatically. Your own key always takes precedence over ours.

## What an AI teammate does with them

Tools are not a menu your AI teammate reads top to bottom. It picks by the description, which is why every entry in
these catalogues says what it is *for* rather than what its API does — and why a tool you switch off disappears
from your AI teammate's view entirely rather than being refused at call time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.