Connect your commerce data to the AI client you already use.
No custom module is required for Odoo Online, and no Seller Central password is required for Amazon. The same OAuth-protected MCP URL works with Claude, ChatGPT, Gemini CLI, and other compatible clients.
What to paste into your AI client
https://app.ksrolabs.com/mcp
Your client opens a KSRO sign-in page the first time you connect. Sign in with your verified workspace email. Never paste an Odoo password or API key into the client.
One endpoint. Three clear connection paths.
Finish Odoo validation first, then follow only the instructions for the client you use. OAuth is handled in the browser; customers do not create or copy a bearer token.
Claude
Web or Claude DesktopTeam and Enterprise workspaces may require an organization owner to approve a custom connector.
ChatGPT
Web custom MCP serverIf the custom MCP option is missing, check the ChatGPT plan and workspace-admin policy. Changing the Odoo API key will not enable a missing ChatGPT feature.
Gemini CLI
Remote HTTP MCPGemini web and mobile may not expose arbitrary custom MCP servers in every account. Gemini CLI is the documented path when that option is unavailable.
Gemini CLI configuration, if you prefer a file
Add this to your user-level ~/.gemini/settings.json. Do not place an Odoo API key or KSRO token in this file.
{"mcpServers":{"ksro-odoo":{"httpUrl":"https://app.ksrolabs.com/mcp"}}}
After saving, run gemini mcp auth ksro-odoo. If your Gemini CLI version uses different flags, run gemini --help; the remote endpoint and browser OAuth flow are unchanged.
From zero to live data.
Odoo Online path
Odoo user + API keyAmazon path
Managed Seller Central authorizationWhat each platform needs
For Odoo, a dedicated user is recommended for least privilege but not required. Single-user accounts can start with the owner/admin user.
- Odoo Online URL, for example https://northstar-retail.odoo.com
- Odoo database name from Settings -> About
- Odoo user email and API key from that same user
- An active Amazon Seller Central account and your primary marketplace
- Approval of the KSRO application in Seller Central; no Amazon API credentials are pasted into KSRO
Source permissions still apply. If the connected Odoo user or app cannot read a record, the MCP client cannot read it either.
If validation fails
The workspace names the exact failing check rather than a generic error.
- You see which stage failed: authentication, metadata, or sample reads
- Each failure carries the remediation step for that specific blocker
- Permission gaps are fixed at the source, in Odoo or Seller Central
- After changing settings, run validation again from the workspace
- MCP client authorization stays blocked until the connection passes