Skip to main content

​
What is MCP on Connie?

Model Context Protocol 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:
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

OAuth

Best for IDEs. One grant covers every workspace you belong to, activity attributes to you, and revoke is one click.

Workspace API key

Best for automation. CI jobs, shared bots, anything that runs on behalf of a workspace rather than a person. No browser flow.
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 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.

​
What’s next

Quickstart

Connect Cursor in under five minutes.

All clients

Setup snippets for Cursor, Claude Code, Claude Desktop, and Windsurf.

Multi-workspace

Route requests to specific workspaces from a single grant.

Workspace API key

The non-OAuth path for automation.
Connie’s MCP server speaks the Streamable HTTP transport (MCP spec 2025-03-26). Older stdio-only clients work via the mcp-remote bridge — covered on the client setup page.