Product flow
How your commerce data reaches Claude.
KSRO hosts the MCP server, the OAuth layer, and the platform gateways. Your team keeps control of the connected Odoo user, API key, and access rights at the source.
The connection in one line
Claude · MCP clientClaude → KSRO OAuth → validated tenant credential → your platform's read APIs. No step of that chain shares your credentials with the client.
MCP server URL
https://app.ksrolabs.com/mcp
OAuth 2.0 + PKCE
Read-only by default
AES-256-GCM at rest
The flow
Four stages, one URL for Claude.
1
You register a workspace
The workspace is your tenant surface: it holds your Odoo connection, its validation status, and the exact next action.
2
You connect an Odoo user
Use the existing owner/admin user or a dedicated least-privilege user, generate an API key for that same user, and paste those details into KSRO. The API key is encrypted before storage.
3
Claude connects to one hosted endpoint
Claude uses https://app.ksrolabs.com/mcp as its connector URL. During authorization, Claude opens a KSRO sign-in page. You log in with your workspace account, and KSRO binds the token to the validated Odoo connection.
4
Claude reads live data, read-only
Every tool call goes through your validated credential and Odoo user permissions. Nothing writes back to Odoo.
What KSRO hosts
- The MCP endpoint and its OAuth authorization server
- Encrypted Odoo credential storage (AES-256-GCM)
- Live validation against Odoo authentication, metadata, and sample-read calls
- Tenant-level Odoo permissions and connector audit records
What stays yours
- Your Odoo database and user permissions
- The API key, revocable from the Odoo user account
- Your Odoo password — KSRO never asks for it
Where it can be revoked
- Delete the API key on the connected Odoo user
- Revoke the app authorization in Seller Central
- Block the workspace user from the KSRO operations console
Ready
Start with the setup guide.
It covers the Odoo Online user/API-key path and the connector URL Claude needs.