Common contract
Every client below connects to the same workspace endpoint https://mcp.erpipe.com/mcp using its own native OAuth flow. ERPipe keeps the Odoo credential on the workspace connection, so no client receives an Odoo password, dashboard cookie, or static bearer token. Odoo ACLs and record rules stay authoritative, every Odoo-bound call needs an explicit instance key, and writes stay off until the workspace owner enables them.
Client recipes
ChatGPT
Primary client · Published setup path
Developer Mode setup
Settings → Apps & Connectors → CreateMCP URL: https://mcp.erpipe.com/mcp
Authenticate
- Enable Developer Mode and create an app/connector with the workspace MCP URL.
- Sign in to ERPipe in the browser and approve workspace access.
- Enable the ERPipe app in the conversation.
Codex CLI
Recipe ready · Syntax checked with codex-cli 0.145.0; OAuth E2E pending
Terminal
codex mcp add erpipe --url https://mcp.erpipe.com/mcp --oauth-resource https://mcp.erpipe.com/mcpcodex mcp login erpipecodex mcp get erpipe
Authenticate
- Run the login command and complete browser consent.
- Select Grant write only when lifecycle or governed write tools are required.
- Use codex mcp get erpipe to confirm the HTTP endpoint and OAuth state.
Claude Code
Recipe ready · Syntax checked with Claude Code 2.1.235; OAuth E2E pending
Terminal
claude mcp add --transport http --scope user erpipe https://mcp.erpipe.com/mcpclaude mcp login erpipeclaude mcp get erpipe
Authenticate
- Complete the browser OAuth flow opened by claude mcp login.
- Use --scope project instead of user only when the config should live in .mcp.json.
- Check claude mcp get erpipe or /mcp before calling tools.
Gemini CLI
Recipe ready · Syntax checked with Gemini CLI 0.46.0; OAuth E2E pending
Terminal + Gemini prompt
gemini mcp add --transport http --scope user erpipe https://mcp.erpipe.com/mcp# Inside Gemini CLI/mcp auth erpipe/mcp
Authenticate
- Run /mcp auth erpipe to start OAuth discovery and browser consent.
- Use /mcp to confirm the server, tools, prompts, and resources are connected.
- Do not add a static Authorization header; ERPipe supports dynamic client registration.
Antigravity CLI
Protocol-compatible · Official schema checked; agy is not installed on the validation machine
~/.gemini/config/mcp_config.json
{"mcpServers": {"erpipe": {"serverUrl": "https://mcp.erpipe.com/mcp"}}}
Authenticate
- Start agy and open /mcp to reload and inspect the server.
- Complete the OAuth action shown by the MCP manager; ERPipe supports DCR.
- Keep serverUrl: Antigravity CLI does not accept Gemini's legacy url/httpUrl keys.
Grok
OAuth verified · Native OAuth verified 2026-07-21; syntax rechecked with Grok 0.2.106
Terminal + Grok TUI
grok mcp add --transport http --scope user erpipe https://mcp.erpipe.com/mcpgrok mcp doctor erpipe# Inside Grok TUI/mcps → erpipe → i → browser consent → r
Authenticate
- Open /mcps, select erpipe, and press i to authenticate.
- Approve browser consent, then press r to refresh the server.
- Use grok mcp doctor erpipe; tokens remain Grok-managed in its OAuth store.
Validate after OAuth
- Call list_instances and choose an explicit instance key.
- Call health_check with that instance key.
- Run one read-only tool such as search_records before enabling writes.
- For write access, reconnect and select Grant write; the target connection must also allow writes and may require owner approval.
Forbidden patterns
- Do not use dashboard cookies as agent credentials.
- Do not paste static bearer tokens into shared config.
- Do not use the removed /{slug}/mcp hosted route.
- Do not assume a default Odoo instance.
Client recipes last reviewed 2026-08-30.