# Connect your agent

Tandem's MCP server is at:

```
https://api.tandemcrm.app/mcp
```

It uses **streamable HTTP** transport (the current MCP standard for remote servers). There are two ways for an agent to authenticate:

- **OAuth (recommended for AI apps).** The app registers itself with Tandem automatically (dynamic client registration), opens a browser, and you sign in, choose a workspace and approve its permissions. Nothing to copy except the address. You can disconnect it at any time under **Agents**.
- **API key (for scripts, servers and agents you run yourself).** A workspace owner or admin creates a key under **Agents**, choosing its permissions. The agent sends it as `Authorization: Bearer crm_sk_…`. Keys are shown once and can be revoked at any time.

Both reach the same tools. An agent only sees the tools its permissions allow.

## Guides by app

- [Claude](/docs/connect/claude): Claude.ai and Claude Desktop connect with just the address. You sign in and choose a workspace once.
- [Claude Code](/docs/connect/claude-code): Claude Code adds Tandem as a remote HTTP server. The first time you use it, it opens a browser for you to sign in.
- [ChatGPT](/docs/connect/chatgpt): ChatGPT connects to Tandem as a custom connector, with Tandem's views shown inline in the chat.
- [Codex](/docs/connect/codex): Codex adds Tandem as a remote MCP server and signs in through your browser.
- [Cursor](/docs/connect/cursor): Cursor connects to Tandem's remote server and signs in through your browser.
- [VS Code](/docs/connect/vs-code): GitHub Copilot's agent mode in VS Code connects to Tandem as an HTTP server and signs in through your browser.
- [Gemini CLI](/docs/connect/gemini-cli): Gemini CLI connects over streamable HTTP and discovers Tandem's sign-in on its own.
- [Hermes](/docs/connect/hermes): Hermes Agent connects over OAuth. The first time it runs, it opens a browser for you to sign in.
- [Muse](/docs/connect/muse): Muse builds its own connector for Tandem from the address and an API key.
- [Delegated](/docs/connect/delegated): Delegated's agents call Tandem through Custom APIs, using Tandem's REST API: the same actions agents use over MCP.
- [Any MCP client](/docs/connect/other): Anything that speaks MCP over streamable HTTP. Clients that can sign in use OAuth; scripts and agents you run yourself use an API key.

## Checking the connection

Ask your agent: "Which Tandem workspace are you connected to, and what can you do there?" It will call `describe_schema`, which returns the workspace's record types, fields, deal stages and activity types.

If the agent can't connect:

- Make sure the address ends in `/mcp`.
- If sign-in loops, sign out of Tandem in the browser and connect again; you choose the workspace after signing in.
- If the agent says a tool is missing, its permissions may not include it. Reconnect and approve more, or create a key with more scopes.
- A workspace whose trial or subscription has ended is read-only: reads work, writes return `payment_required`.