> ## 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 Quickstart

> Connect Claude Desktop to Connie and call your first tool in five minutes.

This walks through the OAuth path with **Claude Desktop** as the example — it speaks MCP over HTTP natively, so this is the shortest possible config. Cursor, Claude Code, and Windsurf follow the same shape via the `mcp-remote` bridge — see [Client setup](/mcp/clients) for their snippets. For automation that should run as a workspace rather than a person, skip to the [Workspace API key](/mcp/api-key) path.

You'll need:

* A Connie account ([sign up at connie.ai](https://connie.ai) if you don't have one)
* A recent Claude Desktop build (any version with native HTTP MCP — most builds from 2026 onward)

***

## 1. Open Claude Desktop's MCP config

The file lives at:

* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
* **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`

If it doesn't exist yet, create it as an empty JSON object: `{}`.

## 2. Add Connie

Paste this into the `mcpServers` block. If you already have other servers configured, add the `"connie"` entry alongside them.

```json theme={null}
{
  "mcpServers": {
    "connie": {
      "url": "https://mcp.connie.ai/api/mcp"
    }
  }
}
```

Save the file. That's the entire config — no command, no bridge, no Node.js required. Claude Desktop's native HTTP client sends its own `client_name` during registration, so the consent screen will show **"Claude Desktop wants to connect"** automatically (no extra metadata flag needed — that's only required for `mcp-remote`-bridge clients on the [Client setup](/mcp/clients) page).

## 3. Fully restart Claude Desktop

Quit and reopen the app. Close every window and let Claude Desktop shut down completely before reopening — a tray-icon close on Windows doesn't count.

## 4. Authorize in the browser

The first time Claude reaches for a Connie tool, your default browser opens to the Connie consent screen.

<Steps>
  <Step title="Sign in to Connie">
    If you're not already signed in, you'll be prompted. An existing browser session works — no second auth.
  </Step>

  <Step title="Pick a default workspace">
    The dropdown lists every workspace you're a member of. Whichever you pick becomes the default for tool calls that don't specify a workspace — you can still address any other workspace per request later. See [Multi-workspace](/mcp/workspaces).
  </Step>

  <Step title="Click Allow">
    Claude receives the access token and closes the browser tab automatically. No copy-paste.
  </Step>
</Steps>

## 5. Test it

Back in Claude, ask something that requires a Connie tool. Try:

* *"List my recent Connie conversations."*
* *"Search Connie tools for `flow`."*
* *"What workspaces do I have access to?"*

Claude calls the corresponding tool and responds with real data from your workspace.

<Note>
  The first call may take an extra second while the MCP session boots and `tools/list` fetches the full surface. Subsequent calls are immediate.
</Note>

***

## Verify the connection

Open [connie.ai](https://connie.ai) and head to **Settings → Connected apps**. You should see a row labeled **Claude Desktop** with its logo, the timestamp of when you authorized, and a **Revoke** button.

Native Claude Desktop registers as `"Claude Desktop"` directly, so the row should show the canonical name from the first authorization. If you're on an older Claude Desktop build without the native HTTP-MCP transport, it falls back to the `mcp-remote` bridge and the row may show `MCP CLI Proxy` or `MCP CLI Client`. In that case: make any tool call to trigger the lazy attribution upgrade, then refresh. If it still shows the placeholder after a successful tool call, see [Troubleshooting](/mcp/troubleshooting#consent-screen-shows-the-mcp-cli-placeholder).

***

## What's next

<CardGroup cols={2}>
  <Card title="Add more clients" icon="grid-2" href="/mcp/clients">
    Setup snippets for Cursor, Claude Code, and Windsurf — they all coexist on the same machine.
  </Card>

  <Card title="Switch workspaces" icon="layer-group" href="/mcp/workspaces">
    Pin a request to a specific workspace, or set a per-tool override.
  </Card>

  <Card title="Workspace API key" icon="key" href="/mcp/api-key">
    For CI jobs and shared automations — one key, no browser flow.
  </Card>

  <Card title="Troubleshooting" icon="life-ring" href="/mcp/troubleshooting">
    OAuth failures, missing tools, attribution placeholder.
  </Card>
</CardGroup>


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