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

# MCP Overview

> Connect Claude, ChatGPT, and other AI clients to Sapt through one MCP connector.

The Model Context Protocol (MCP) is an open standard for connecting AI agents to external tools and data sources.

For most users, Sapt uses one connector URL:

```
https://mcp.sapt.ai/mcp
```

Add that URL to Claude or ChatGPT, sign in with your Sapt account, and the available tools show up for the Projects you can access.

## Claude setup

1. Open [Claude connectors](https://claude.ai/customize/connectors?modal=add-custom-connector).
2. Click **Add custom connector**.
3. Name it `Sapt`.
4. Paste the Sapt MCP URL:

```
https://mcp.sapt.ai/mcp
```

5. Click **Connect** and authorize with your Sapt account.
6. Optional but recommended: set tools to **Always allow**.

## ChatGPT setup

1. Open [ChatGPT connector settings](https://chatgpt.com/#settings/Connectors/Advanced).
2. Go to **Settings → Apps → Advanced settings**.
3. Turn on **Developer mode**.
4. Click **Create app**.
5. Name it `Sapt`.
6. Paste the Sapt MCP URL:

```
https://mcp.sapt.ai/mcp
```

7. Set authentication to **OAuth**.
8. Check the disclaimer and click **Create**.

## Authentication

Claude and ChatGPT use OAuth. When the client asks you to connect, sign in with your Sapt account. The connector uses your account permissions to decide which Projects and tools are available.

API keys are for direct REST API usage and server-side integrations, not the normal Claude or ChatGPT connector flow.

## Tools

The connector exposes Sapt capabilities across Project context, memory, content, search, social, ads, email, reviews, leads, and support. Tool availability depends on your account, Project access, and connected integrations.

For developers who need narrower catalogs, the pages below describe the underlying capability groups.

| Connector                            | Tools | Purpose                                                                             |
| ------------------------------------ | ----- | ----------------------------------------------------------------------------------- |
| **Sapt Google Business Profile MCP** | 11    | Google Business Profile management server.                                          |
| **Sapt Cold Email Sequencing MCP**   | 22    | DEPRECATED LEGACY ENGINE: This server drives the old cold-outreach engine.          |
| **Sapt Meta MCP**                    | 71    | Social media command center for Facebook, Instagram, and Threads via the Meta APIs. |
| **Sapt**                             | 55    | You are connected to Sapt, the user's shared AI operating layer for one workspace.  |

## MCP or REST?

Both let software work with the same Project. Pick by how you're building.

| Need                                                         | Best fit                                    |
| ------------------------------------------------------------ | ------------------------------------------- |
| Let Claude, ChatGPT, Cursor, or another agent use Sapt tools | **MCP**                                     |
| Build an internal app, script, or custom integration         | **[REST API](/docs/mintlify/api/overview)** |
| Start without writing code                                   | **Dashboard**                               |

## Safety basics

Technical access should be scoped and intentional.

* Keep API keys on the right Project.
* Enable tools only where they're needed.
* Use review steps for public or customer-facing actions.
* Keep secrets in environment variables or secure app settings.

When in doubt, start with read-only or draft-producing access before allowing direct changes.