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

# Official connectors (Claude & ChatGPT)

> Status and roadmap for the one-click Claude connector and the ChatGPT app.

The smoothest experiences — adding ECN as a **Claude connector** (Settings →
Connectors on claude.ai / Claude Desktop) or as a **ChatGPT app** — require OAuth.
ECN's MCP server authenticates with static, org-scoped API keys today, so these
one-click flows are on the roadmap rather than available now.

## What works today

| Client                       | Status      | Guide                                                    |
| ---------------------------- | ----------- | -------------------------------------------------------- |
| Claude Code                  | ✅ Supported | [Connect Claude Code](/mcp/connect-claude-code)          |
| Cursor                       | ✅ Supported | [Connect Cursor](/mcp/connect-cursor)                    |
| Any remote-MCP client        | ✅ Supported | [Generic setup](/mcp/overview#generic--remote-mcp-setup) |
| Claude connector (claude.ai) | 🛠️ Roadmap | Needs OAuth                                              |
| ChatGPT app                  | 🛠️ Roadmap | Needs OAuth + `search`/`fetch` tools                     |

## What's required for the one-click connectors

<AccordionGroup>
  <Accordion title="Claude connector — OAuth 2.1 + Dynamic Client Registration">
    Claude's custom connectors expect the remote MCP server to support OAuth 2.1,
    including Dynamic Client Registration, so users authorize with their ECN account
    instead of pasting a key. This mirrors how Attio's MCP works — "log in with your
    account, no API keys required."
  </Accordion>

  <Accordion title="ChatGPT app — OAuth + search/fetch tools">
    ChatGPT apps additionally expect the server to expose conventionally named
    `search` and `fetch` tools so the model can retrieve and cite records. ECN's tool
    catalog would expose those aliases over the OAuth-authenticated endpoint.
  </Accordion>
</AccordionGroup>

<Note>
  Tracked under the **MCP & Agent Surface** workstream (Linear `TER-157`–`TER-160`).
  When OAuth ships, this page will document the one-click flow for each client.
</Note>