Setup guide

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

Claude · Claude ChatGPT · ChatGPT Gemini · Gemini CLI
MCP server URL
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.

OAuth 2.0 + PKCE Read-only by default AES-256-GCM at rest
Choose your 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 Desktop
1
Open Settings
In Claude, open Settings, then Connectors or Custom connectors.
2
Add the server
Choose Add custom connector and enter https://app.ksrolabs.com/mcp.
3
Connect with OAuth
Choose Connect, sign in to KSRO with the verified workspace email, and approve read-only access.
4
Check the tools
Return to Claude, enable the connector for the conversation, and run a harmless read-only question.

Team and Enterprise workspaces may require an organization owner to approve a custom connector.

ChatGPT

Web custom MCP server
1
Open the connector area
Open the tools, apps, or connectors area. Depending on the ChatGPT rollout, the option may be called Add custom MCP server or appear under Plugins.
2
Enter the server URL
Add https://app.ksrolabs.com/mcp exactly. Do not use the KSRO login or setup-guide URL.
3
Complete OAuth
Choose Connect or Install, sign in to KSRO with the verified workspace email, and approve read-only access.
4
Refresh the tools
Start a new conversation or refresh the tool list if the connector does not appear immediately.

If 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 MCP
1
Add the remote server
Use Gemini CLI or add an mcpServers entry with httpUrl set to the KSRO endpoint.
2
Authenticate
Run gemini mcp auth ksro-odoo and complete the browser OAuth flow.
3
Verify the server
Run gemini mcp list, then use /mcp in Gemini CLI to inspect the connection and tools.
4
Start with read access
Ask a harmless question and confirm the result before requesting any approved write policy.

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

The steps

From zero to live data.

Odoo Online path

Odoo user + API key
1
Create your workspace
Register with your work email. This is the account your MCP client will ask you to sign into later.
2
Choose the Odoo user
Use a dedicated user when the customer has one, or use the existing owner/admin user for single-user Odoo accounts. Generate the API key from that same user account.
3
Connect and pass live validation
Open Odoo setup in the workspace and enter the Odoo URL, database, Odoo user login, and API key. KSRO discovers readable models from that user and tests the exact Odoo calls the client will use.
4
Add the connector to your AI client
Paste the MCP server URL into Claude, ChatGPT, Gemini CLI, or another compatible MCP client. Complete OAuth with your workspace email.

Amazon path

Managed Seller Central authorization
1
Create your workspace
The same workspace holds every commerce connection and its validation status.
2
Join the Amazon pilot
KSRO enables approved pilot workspaces while the public SP-API application completes Amazon review.
3
Connect and pass live validation
Choose your marketplace and approve KSRO inside Seller Central. Amazon returns the Seller ID and authorization securely; KSRO then tests Orders, FBA Inventory, Listings, and Finances.
4
Add the connector to your AI client
The same MCP server URL serves Amazon. Nothing about the MCP client configuration changes per platform.

What 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
Start now

Create the workspace first — everything else happens inside it.