Connect Claude, Cursor, Codex, and Automation Clients

All compatible clients use the same Odoo MCP endpoint. Use OAuth for interactive users and a dedicated scoped API key for services or automations.

Connect Claude

1. Open Claude Settings and go to Connectors.
2. Choose Add custom connector.
3. Enter the MCP URL: https://your-odoo-domain.com/mcp
4. Choose Connect and complete the Odoo OAuth login and consent flow.
5. Enable the required tools and test with a read-only request such as odoo_whoami.

Connect Cursor

Create an MCP configuration for the project or user profile. Add a server named niyu-odoo with this URL:

https://your-odoo-domain.com/mcp

For OAuth-capable setups, save the configuration, refresh MCP servers, and complete the browser login when prompted.

For API-key authentication, add this request header in the client configuration:

Authorization: Bearer niyu_mcp_REPLACE_WITH_SECRET

Keep the key outside source control. Use a dedicated Odoo execution user, the minimum required scopes, an expiry date, and an IP allowlist where practical.

Connect Codex, n8n, LangChain, crewAI, scripts, and other clients

Use Streamable HTTP with the same MCP URL. Choose OAuth when the client supports it. Otherwise, send a dedicated scoped API key in the Authorization Bearer header.

Create a separate API key for every client or automation. This makes each connection independently revocable and auditable.

Optional local bridge

For development or localhost workflows, run the included mcp_bridge.py as a local STDIO server. Configure ODOO_URL and ODOO_API_KEY in the local process environment. Keep mutations and deletes disabled until the workflow has been tested safely.