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

# Connect an AI assistant

> Let Claude or another AI assistant read your Reclosed data.

Reclosed has an MCP server, so an AI assistant can read your campaigns, their results and their conversations. MCP (the Model Context Protocol) is the standard way AI assistants connect to other apps. Once it's connected, you can ask things like:

* "How are my Reclosed campaigns doing? Which one has the best reply rate?"
* "Read the conversations in my Solar campaign and sum up what leads are asking about."

The assistant can only read. It can't send messages, change campaigns or delete anything. [Tools and limits](/mcp-tools) lists exactly what it can read.

## What you need

* **An API key.** Create one as [API keys](/api-keys) explains. Make a separate key for each assistant and name it after that assistant, such as "Claude, Sam's laptop", so you can revoke one without affecting the others.
* **An assistant that can send the key with every request**, in a request header. Claude (on some accounts), Claude Code, Cursor and VS Code can. ChatGPT can't: for MCP connections it supports sign-in (OAuth) or no login, but not API keys, and Reclosed doesn't offer sign-in.

Every assistant connects to this address:

```text theme={null}
https://api-production-a5d3.up.railway.app/mcp
```

## Connect it

**Claude**

In claude.ai or the Claude desktop app:

1. Go to **Customize > Connectors** and click **Add custom connector**. On a Team or Enterprise plan, an Owner adds it instead, under **Organization settings > Connectors**: click **Add**, then **Custom**, and choose **Web** if it asks for a type.
2. Name it Reclosed and enter the server address.
3. If it asks about **Authentication**, choose **No sign-in**.
4. Under **Request headers**, choose `authorization` and enter `Bearer rk_live_xxx` as the value, with your key in place of `rk_live_xxx`. Type `Bearer` exactly like that, then a space, then the key. Mark the header **Required**.
5. Click **Add**. To use it in a chat, click **+**, then **Connectors**, and turn Reclosed on.

**Request headers** is a beta that Claude offers to some accounts only. If you don't see it, your Claude account can't send an API key yet, so use Claude Code instead.

On a Team or Enterprise plan, members then click **Connect** next to Reclosed in **Customize > Connectors**. Everyone who uses the connector reads your Reclosed account with that one key.

Claude can't change a connector's key later. To use a new key, remove the connector and add it again.

**Claude Code**

In a terminal, run this, with your key in place of `rk_live_xxx`:

```bash theme={null}
claude mcp add --scope user --transport http reclosed https://api-production-a5d3.up.railway.app/mcp --header "Authorization: Bearer rk_live_xxx"
```

Then run `claude mcp list`. Reclosed should show as **Connected**.

`--scope user` makes Reclosed available in all your projects and saves the key in Claude Code's settings file on your computer (`~/.claude.json`). Don't use `--scope project`: it saves the key in the project's `.mcp.json` file, which is usually committed with the code.

**Cursor**

Open your global Cursor MCP file, `~/.cursor/mcp.json` (on Windows, `C:\Users\<you>\.cursor\mcp.json`), and add Reclosed, with your key in place of `rk_live_xxx`:

```json theme={null}
{
  "mcpServers": {
    "reclosed": {
      "url": "https://api-production-a5d3.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer rk_live_xxx"
      }
    }
  }
}
```

If the file already lists other servers, add the `reclosed` entry inside the existing `mcpServers`. Use this global file rather than a project's `.cursor/mcp.json`, which may be committed with your code.

Developers can keep the key out of the file by putting it in an environment variable and writing the header as `Bearer ${env:RECLOSED_API_KEY}`.

**VS Code**

Run **MCP: Open User Configuration** from the Command Palette and add:

```json theme={null}
{
  "inputs": [
    {
      "type": "promptString",
      "id": "reclosed-api-key",
      "description": "Reclosed API key",
      "password": true
    }
  ],
  "servers": {
    "reclosed": {
      "type": "http",
      "url": "https://api-production-a5d3.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer ${input:reclosed-api-key}"
      }
    }
  }
}
```

VS Code asks for the key the first time it starts the server and stores it securely, so the key never appears in the file.

**Other assistants**

Any assistant that supports remote MCP servers over HTTP (the Streamable HTTP transport) and lets you add a request header can connect. Give it the server address and this header, with your key:

```text theme={null}
Authorization: Bearer rk_live_xxx
```

## Check it works

Ask your assistant to list your Reclosed campaigns. It should use the `campaigns_list` tool, and may ask your permission first.

If it doesn't connect:

* **The key is rejected.** The assistant reports `401`, says the server rejected the key, or asks you to sign in. The key is mistyped or revoked, or the header is missing `Bearer ` before the key. Check the header, or create a new key.
* **Too many requests.** The assistant reports `429`. Wait a minute, then try again.
* **The server can't be reached.** Check the address, including `/mcp` at the end.

## Keep it safe

* Anyone with the key can read your campaigns and conversations, so keep it as safe as a password. If a key might have leaked, revoke it on the API keys page. Anything using it stops working straight away.
* When the assistant reads your data, it's sent to the company that runs the assistant, such as Anthropic, Cursor or GitHub, and handled under that company's terms. That includes your leads' names, phone numbers and messages, so check it fits your privacy obligations before you connect.
* Your leads wrote those messages, and an assistant reading them can be misled by instructions hidden in one. Take care giving the same assistant tools that can send data elsewhere, such as email.

## Search these docs from your assistant

These docs have their own, separate MCP server at `https://docs.reclosed.io/mcp`. An assistant connected to it can search this documentation while it helps you build an integration. It needs no key, and it can't read your Reclosed data.


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