# Setup

> Connecting Claude, ChatGPT and Cursor to one MCP endpoint, and fixing what goes wrong when sign-in fails or the tools do not show up.

- [Connect company apps to Claude and ChatGPT](https://elaichi.ai/blog/connect-company-apps-to-claude-and-chatgpt/) — To connect company apps to Claude and ChatGPT, connect each account once in Elaichi, share it, and add one URL to both. No MCP server to run.
- [Connect Elaichi to Claude Code](https://elaichi.ai/blog/connect-elaichi-to-claude-code/) — To connect Elaichi to Claude Code, run one claude mcp add command and sign in with OAuth. The entry holds no secret, so a project .mcp.json is safe to commit.
- [Connect Elaichi to Codex](https://elaichi.ai/blog/connect-elaichi-to-codex/) — To connect Elaichi to Codex, add one URL as a streamable HTTP server and run codex mcp login. No token, no header, and each engineer signs in as themselves.
- [Connect Elaichi to VS Code and Windsurf](https://elaichi.ai/blog/connect-elaichi-to-vs-code-and-windsurf/) — To connect Elaichi to VS Code and Windsurf, add one URL to each editor's MCP config and sign in with OAuth. No personal API keys on any laptop.
- [Connect Elaichi to Claude](https://elaichi.ai/blog/connect-elaichi-to-claude/) — To connect Elaichi to Claude, add one URL as a custom connector and sign in with OAuth. On Team and Enterprise, an Owner adds it once for everyone.
- [Fix OAuth errors when adding an MCP connector](https://elaichi.ai/blog/mcp-oauth-errors/) — Most OAuth errors when adding an MCP connector come from the URL, the account or a missing checkbox. What each Elaichi error means, and who fixes it.
- [MCP tools not showing up? Start here](https://elaichi.ai/blog/mcp-tools-not-showing/) — MCP tools not showing in Claude, ChatGPT or Cursor? With Elaichi, connected tools are never listed by design. Check these five things, in order.
- [Connect Elaichi to ChatGPT](https://elaichi.ai/blog/connect-elaichi-to-chatgpt/) — To connect Elaichi to ChatGPT, a workspace admin adds one MCP endpoint as a custom app and each person signs in with OAuth. No API key, no per-user URL.
- [Connect Elaichi to Cursor for a whole team](https://elaichi.ai/blog/cursor-mcp-one-endpoint-vs-per-developer/) — To connect Elaichi to Cursor, add one URL to mcp.json or share it as a Team MCP server, and each developer signs in with OAuth. No API key.