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

# MCP

> Connect an AI tool to B2B Signals over MCP, and control whether it can approve and send messages.

MCP lets an AI tool work in your workspace: find people, run campaigns and draft replies. Your approval rules still apply. Set it up in **Settings** › **API & MCP**.

Connecting a tool sends nothing. Drafts an AI tool makes wait in **Approvals** for a person, unless you turn on [Let AI tools approve and send messages](#let-ai-tools-send).

## Before you start

* **Your plan.** Connecting an AI tool comes with a paid plan (Software or Custom). On Free, the card says "Your plan doesn’t include AI tools." with **See plans**. See [Plans](https://docs.b2bsignals.ai/getting-started/plans.md).
* **Your role.** Only owners and admins can make the link. Others see "Ask an owner or an admin for it."
* **Your AI tool.** It must accept a custom MCP connector by link, or let you set a header.

## Connect with a link

Use this for AI tools where you can only paste a link.

**1. Open the MCP card**

Go to **Settings** › **API & MCP** and press the connect button on the card.

**2. Get your link**

Press **Make a key to get the link**. If the workspace already has a key, press **Make a new key to get the link…**. Copy the link.

**3. Add it to your AI tool**

In your AI tool's settings, add a custom connector. Paste the link, give it any name and save. The B2B Signals tools show up in your chat.

> [!WARNING]
>
> The link carries your API key, and we show the full key once. Anyone who has the link can act as your workspace. Don't share it or paste it into a shared document. **Make a new key to get the link…** stops the old key right away, including every other tool that uses it, so update those too.

## Connect with a header

If your AI tool or code lets you set headers, use this. It keeps the key out of the address, which tools and hosting services may save in logs.

Copy the address from the MCP card. Then send your [API key](https://docs.b2bsignals.ai/developers/api-keys.md) in the `x-api-key` header:

```json theme={null}
{
  "url": "<the address from the MCP card>",
  "headers": { "x-api-key": "b2b_sk_your_key" }
}
```

The exact format depends on your tool.

## What your AI tool can do

Press **See everything it can do** on the card for every tool, with search. There are 124 today:

| Group | Tools |
| - | - |
| Find people and Radar | 16 |
| People and lists | 39 |
| Campaigns | 28 |
| Inbox and replies | 4 |
| Watchlists | 14 |
| Do not contact | 6 |
| Senders and safety | 6 |
| Reports | 4 |
| Workspace, templates and webhooks | 7 |

The tool acts with your workspace's API key, so it has owner-level access to this workspace. It can delete a campaign or a list if you ask it to. Your AI tool may ask you before it acts, but that's up to the tool. See [Permissions](https://docs.b2bsignals.ai/developers/overview.md#permissions).

## Let AI tools send

**Let AI tools approve and send messages** is off by default. While it's off, drafts wait in [Approvals](https://docs.b2bsignals.ai/campaigns/approvals.md) for a person.

![Let AI tools approve and send messages switch turned off, above the API key row with a masked key](https://mintcdn.com/b2-b-signals-llc/u5yYe4FZtFc5vtD_/images/developers/api-key-and-ai-approval.png?fit=max\&auto=format\&n=u5yYe4FZtFc5vtD_\&q=85\&s=c487e16a2426d5c16053b0585848c187)

Settings › API & MCP: the switch at the bottom of the MCP card, off by default, and the API key card under it.

When it's on, your AI tool and any tool that uses your API key can approve drafts and send LinkedIn messages on their own, without a person opening **Approvals**.

* Only owners and admins can change it, and only while signed in. A key can't turn it on.
* Your plan must include MCP.
* It covers your whole workspace, including anything that uses your API key.
* Replies sent this way are limited to 30 per workspace per UTC day, and one every 2 minutes per chat.

> [!WARNING]
>
> With this on, an AI tool's mistake can reach real people, and a sent message can't be taken back. Turn it on only if you want messages to go out with no human review.

Some actions still need a signed-in person, even with this on. See [Permissions](https://docs.b2bsignals.ai/developers/overview.md#permissions).

## Disconnect

To cut off every AI tool, [turn off or replace your API key](https://docs.b2bsignals.ai/developers/api-keys.md). There's one key per workspace, so this also stops your scripts and anything else that uses it.

To remove one tool, delete the connector in that tool. The key keeps working wherever else it's saved.

## Troubleshooting

> [accordion] The AI tool says Not authenticated
>
> The key in the link is wrong, was replaced or was turned off, or your plan doesn't include MCP. Make a new link and update the connector.

> [accordion] The tools don't show up
>
> Check that the whole link was pasted and that you saved the connector. Then start a new chat in your AI tool.

> [accordion] The tool says a signed-in session is required
>
> A person has to do this in B2B Signals. See [Permissions](https://docs.b2bsignals.ai/developers/overview.md#permissions).

> [accordion] Drafts aren't going out
>
> They're waiting in [Approvals](https://docs.b2bsignals.ai/campaigns/approvals.md). That's the default.

## Related

> [card] [API keys](https://docs.b2bsignals.ai/developers/api-keys.md)
>
> Make, replace or turn off your key.

> [card] [Approvals](https://docs.b2bsignals.ai/campaigns/approvals.md)
>
> Review what AI tools draft.


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