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

# MCP Overview

> Connect Connie to MCP-compatible IDEs and tools. Two auth modes, one HTTPS endpoint, every workspace you belong to.

## What is MCP on Connie?

[Model Context Protocol](https://modelcontextprotocol.io) is the open standard that lets an LLM-powered client — Cursor, Claude Code, Claude Desktop, Windsurf, and a growing list of others — reach into a remote service and call its tools directly. Connie exposes its MCP server at:

```
https://mcp.connie.ai/api/mcp
```

Connect once and your IDE's AI assistant gets first-class access to:

* Your **CRM** — search contacts, create deals, log activity
* Your **Inbox** — list conversations, draft replies, send messages
* Your **Flows** — list, trigger, and inspect workflows
* Your **Tools** — every integration you've connected (Slack, GitHub, LinkedIn, …)

No copy-pasting between tabs; no per-IDE plugin to install.

***

## Two auth modes

<CardGroup cols={2}>
  <Card title="OAuth" icon="user-check" href="/mcp/quickstart">
    **Best for IDEs.** One grant covers every workspace you belong to, activity attributes to you, and revoke is one click.
  </Card>

  <Card title="Workspace API key" icon="key" href="/mcp/api-key">
    **Best for automation.** CI jobs, shared bots, anything that runs on behalf of a workspace rather than a person. No browser flow.
  </Card>
</CardGroup>

| | **OAuth** | **Workspace API key** |
| - | - | - |
| **Token shape** | Dynamic `mcp_at_*` access token | Static `sk_*` key from workspace settings |
| **Scope** | The user's identity, across every workspace they're a member of | One specific workspace |
| **Identity in audit logs** | The human who authorized — preserved per call | Anonymous to the workspace |
| **Lifetime** | 1h access + 30d refresh, rotates automatically | Until manually revoked |
| **Multiple workspaces** | One grant covers all the user's workspaces; switch via `?workspaceId=` | One key per workspace |
| **Setup** | One-click browser flow on first use | Paste key into client config |
| **Revoke** | Click **Revoke** in [Connected Apps](https://connie.ai) | Rotate the key in workspace settings |

**The rule, not just a rule of thumb:** OAuth is for software a human is actively driving. For anything else — automation, CI, scheduled jobs, shared bots — use a workspace API key.

This isn't a stylistic preference. OAuth grants are *user-scoped*, so a leaked OAuth token exposes every workspace the human belongs to. A workspace API key is *workspace-scoped*, so a leaked key exposes exactly one workspace's data. Smaller blast radius is always the right default for credentials a machine holds — that's why the two paths exist.

***

## How attribution works

Each MCP client that authorizes you shows up as its own row in your workspace's Connected Apps page. Cursor and Claude Code appear with their own logos and independent revoke buttons, so removing one doesn't kill the other.

For the **consent screen** to show your IDE's name ("Cursor wants to connect to your Connie workspace" rather than the generic `MCP CLI Proxy` placeholder), the install snippet on the [client setup page](/mcp/clients) passes `--static-oauth-client-metadata '{"client_name":"<IDE>"}'` to `mcp-remote` at registration time. Copy-paste the snippet as-is and the name shows correctly from the first authorization.

If you skip the flag (or use a custom MCP host that doesn't set `client_name`), the consent screen renders the placeholder and Connie falls back to a lazy upgrade after the first tool call — see [Troubleshooting](/mcp/troubleshooting#consent-screen-shows-the-mcp-cli-placeholder).

***

## What's next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/mcp/quickstart">
    Connect Cursor in under five minutes.
  </Card>

  <Card title="All clients" icon="grid-2" href="/mcp/clients">
    Setup snippets for Cursor, Claude Code, Claude Desktop, and Windsurf.
  </Card>

  <Card title="Multi-workspace" icon="layer-group" href="/mcp/workspaces">
    Route requests to specific workspaces from a single grant.
  </Card>

  <Card title="Workspace API key" icon="key" href="/mcp/api-key">
    The non-OAuth path for automation.
  </Card>
</CardGroup>

<Note>
  Connie's MCP server speaks the [Streamable HTTP](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http) transport (MCP spec 2025-03-26). Older stdio-only clients work via the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge — covered on the [client setup](/mcp/clients) page.
</Note>


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