Skip to main content
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

ClientStatusGuide
Claude Code✅ SupportedConnect Claude Code
Cursor✅ SupportedConnect Cursor
Any remote-MCP client✅ SupportedGeneric setup
Claude connector (claude.ai)🛠️ RoadmapNeeds OAuth
ChatGPT app🛠️ RoadmapNeeds OAuth + search/fetch tools

​
What’s required for the one-click connectors

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.”
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.
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.