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

# MCP Integration

> Connect Clearcue to AI assistants like Claude, ChatGPT, Perplexity, and Cursor via the Model Context Protocol.

The Clearcue MCP server lets you access your buying signals, leads, and pipeline data directly from your favorite AI assistant using the Model Context Protocol (MCP).

Ask questions in natural language, filter people, set up signals, and export lists — all without leaving your AI tool.

## Available tools

Once connected, your AI assistant can use these tools.

### Your account

| Tool                        | What it does                              |
| --------------------------- | ----------------------------------------- |
| **get\_my\_context**        | Confirms who you are signed in as         |
| **list\_my\_organizations** | Lists the organizations you can work with |
| **create\_organization**    | Creates a new organization                |

### Finding and organizing records

| Tool                            | What it does                                                             |
| ------------------------------- | ------------------------------------------------------------------------ |
| **get\_filter\_schema**         | Shows which filters you can use (country, seniority, industry, and more) |
| **search\_companies\_by\_name** | Finds a company by name                                                  |
| **fetch\_industries**           | Lists the industries you can filter by                                   |
| **get\_lists**                  | Shows your saved lists                                                   |
| **manage\_tags**                | Adds or removes tags on people and companies                             |

### Signals

| Tool                               | What it does                                                 |
| ---------------------------------- | ------------------------------------------------------------ |
| **list\_signal\_configs**          | Shows the signals you have set up                            |
| **list\_signal\_templates**        | Shows the signal templates you can start from                |
| **create\_template\_signal**       | Sets up a signal from a template                             |
| **create\_custom\_search\_signal** | Sets up a signal that watches posts matching your own search |
| **deactivate\_signal\_config**     | Turns a signal off                                           |

### Exports

| Tool                         | What it does                                                    |
| ---------------------------- | --------------------------------------------------------------- |
| **people\_export**           | Exports up to 10,000 people, filtered however you like          |
| **companies\_export**        | Exports up to 10,000 companies, filtered however you like       |
| **export\_person\_signals**  | Exports one person's signals, with the content behind each one  |
| **export\_company\_signals** | Exports one company's signals, with the content behind each one |
| **companies\_import**        | Adds companies to your account in bulk                          |

## How exports work

Exports return a CSV file rather than dumping rows into the conversation. Your
assistant picks the file up and works from it, so keep asking for what you want:
summarize it, pull out the accounts worth calling, or turn it into a shortlist.

Files stay available for 24 hours.

Reach for the two signal exports when you want the detail behind one account or
one person. Each row is a single signal with the post, job listing, or research
finding that triggered it, who it came from, and which of your signals matched.
That depth is why they run one record at a time.

<Note>
  If your assistant says it cannot reach the file, the block is in its own
  network settings, not in Clearcue. See [letting Claude open your
  exports](/mcp/claude#let-claude-open-your-exports).
</Note>

## How authentication works

Clearcue supports two authentication methods for MCP:

### OAuth 2.0 (recommended)

When you add the Clearcue connector in your AI assistant, it opens a browser window where you sign in with your Clearcue account. Once authorized, the AI assistant can securely access your organization's data. This is the easiest option for tools that support OAuth, like Claude Desktop, claude.ai, and ChatGPT.

### API key

For MCP clients that don't support OAuth — such as custom agents, automation platforms (n8n, Make), or CLI tools — you can generate a static API key instead.

1. Go to **Settings > Integrations > Clearcue MCP** in your Clearcue dashboard
2. Click **Generate Key** and give it a name
3. Copy the token (it starts with `clc_` and is only shown once)
4. Pass it as a `Bearer` token in your MCP client's authorization header

You can revoke or delete API keys at any time from the same settings page.

All requests — whether via OAuth or API key — are scoped to your organization. You can only access data you have permission to see.

## Server URL

Use this URL when configuring any MCP client:

```
https://api.tools.clearcue.ai/mcp
```

## Setup guides

<CardGroup cols={2}>
  <Card title="Claude" icon="comments" href="/mcp/claude">
    Connect Clearcue to Claude Desktop or claude.ai.
  </Card>

  <Card title="ChatGPT" icon="message" href="/mcp/chatgpt">
    Connect Clearcue to ChatGPT via connectors.
  </Card>
</CardGroup>

## Example prompts

Once connected, try asking your AI assistant:

* "Export people from Germany with a C-Suite seniority level"
* "Which companies have the most interactions this month?"
* "Create a signal tracking engagers of linkedin.com/company/clearcue"
* "Export all people who showed buying intent in the last 7 days"
* "What signals do I have configured?"
* "Export every signal for Acme Corp so I can see what they have been posting about"
* "Pull the signals for this person before my call: linkedin.com/in/their-profile"