Claude for Odoo Online, priced like a managed business system.
Start with safe read-only analysis, then ask KSRO to enable create and update automation when the workspace is paid and the exact Odoo models are approved. The subscription covers the hosted MCP server, OAuth, validation, encrypted credentials, logs, rate limits, and support.
Choose read-only analysis first. Add write automation when the process is ready.
Most customers begin by asking Claude to read and analyze Odoo. When the business process is clear, KSRO can enable create and update tools for paid workspaces with exact model and operation approval.
Read-only Odoo analysis
Included with every validated workspace. Claude can inspect the Odoo models and records the connected Odoo user is already allowed to read.
- Search and read Odoo records from Claude
- Describe models, fields, and relationships before analysis
- Analyze sales, invoices, customers, inventory, purchases, CRM, and products
- No create, update, or delete operations in this mode
Approved create and update automation
Available for paid customers after KSRO reviews the use case. Write tools stay blocked until the admin panel approves the exact Odoo models and operations.
- Prepare record creation or update from Claude
- Require a confirmation token before anything is committed
- Scope access to specific models such as contacts, CRM leads, sales orders, products, or tasks
- Revoke or narrow write access from the admin panel at any time
What the subscription pays for.
The price covers the managed operating layer between Claude and Odoo Online: identity, validation, secure credential handling, rate limits, audit trails, write governance, and support when a customer's Odoo permissions or API key changes.
Hosted MCP endpoint
Customers use one KSRO URL in Claude. KSRO runs the server, transport, OAuth metadata, token flow, and production deployment.
Security by default
Odoo API keys are encrypted at rest, Claude is read-only unless approved, and source Odoo permissions remain the final control.
Live Odoo validation
The workspace checks the URL, database, login, API key, readable models, and sample access before Claude is allowed in.
Logs and usage guardrails
Every MCP request is visible in activity logs, and quotas protect customers and the shared service from runaway sessions.
Controlled write automation
Create and update tools are a paid, admin-approved capability with exact model scoping and confirmation controls.
Setup and policy support
KSRO helps customers resolve validation blockers, API-key rotation, billing activation, and safe write-policy changes.
The real alternative is not a free API key.
A raw Odoo API key does not give a customer OAuth for Claude, token handling, request limits, audit visibility, model discovery, error handling, or a safe path to write automation.
KSRO packages those pieces into a managed SaaS workspace so the customer can focus on business analysis and process automation instead of building and operating the connector themselves.
What customers can use Claude for.
The connector is useful before write access is enabled, and it becomes more powerful once a paid workspace has an approved write policy.
Business analysis from live Odoo data
Ask Claude to summarize sales, compare customer performance, inspect open invoices, review inventory risk, analyze purchase trends, or explain CRM pipeline movement.
Operational answers without exports
Claude can search records, count records, inspect fields, and follow relationships from the connected Odoo user permissions without CSV downloads or manual reports.
Create records after review
For approved models, Claude can prepare new records such as contacts, CRM leads, sales follow-up tasks, or other scoped Odoo records and wait for confirmation before commit.
Update records with guardrails
For approved models, Claude can prepare updates to selected fields while KSRO checks the admin policy, the connected Odoo user permissions, and the confirmation token.
Start small, then choose the term that matches usage.
All paid terms include the same production allowance today: 15,000 MCP tool calls/month, one Odoo Online workspace, read tools, audit logs, support, and eligibility for admin-approved create/update policies.
14-day trial
For validation and light Claude testing before a paid workspace is activated.
- One Odoo Online workspace connection
- Read-only Claude analysis during trial
- Email verification required before setup
- Activity logs visible in the workspace
- Create/update tools require paid KSRO approval
Odoo Automation
For teams that want a short paid pilot with read access and controlled write automation.
- One validated Odoo Online connection
- Read-only analytics, model discovery, and record search
- Eligible for admin-approved create/update tools
- Per-request activity logs
- Email support for setup and policy changes
Odoo Automation
For operators who want enough runway to prove automation value before an annual plan.
- Everything in quarterly access
- Usage resets every calendar month
- Create/update policies can be scoped by model and operation
- OAuth refresh-token window stays at 30 days
- Priority handling for validation blockers
Odoo Automation
For production use once the Odoo connection and Claude workflow are validated.
- Everything in six-month access
- Best effective monthly rate
- Annual workspace continuity
- Admin-controlled create/update enablement
- Monthly usage guardrails to protect service stability
Built for controlled production use.
The paid workspace is not just an API pipe. It includes the guardrails customers need before they let Claude work with business data.
Odoo Online validation
The workspace validates URL, database, login, API key, and readable model access before Claude can connect.
OAuth 2.0 for Claude
Claude connects through KSRO OAuth with PKCE, workspace-bound grants, refresh tokens, and revocation support.
Write access by approval
Read-only is the default. Create and update tools require exact model and operation approval in the admin panel.
Audit and usage controls
Every tool request is auditable, and quota limits protect the shared service from runaway sessions.
Simple for the customer, controlled behind the scenes.
Customers should not need to understand MCP internals. They verify email, connect Odoo Online once, validate the workspace, and use the same MCP URL in Claude.
Create a verified workspace
The customer registers with a real email address and verifies it before connecting business systems.
Connect Odoo Online
They enter the Odoo URL, database name, login, and API key from the same Odoo user. KSRO validates live access.
Add KSRO to Claude
Claude uses the KSRO MCP URL and OAuth flow. The customer signs in with the workspace email and stays connected through refresh tokens.
Expand safely when needed
Read-only analysis works first. Paid write access can be enabled later for exact models and operations.
Usage policy
Enforced automaticallyA counted unit is an authenticated MCP tool invocation from Claude. OAuth sign-in, setup pages, token refresh, validation checks, and health checks are not counted as paid usage.
The annual plan works out to €45.83/month equivalent. If KSRO saves even one manual reporting cycle, one connector build, or one production troubleshooting session, the subscription is usually easier to justify than internal maintenance.
Business Direct
For higher call volume, multiple Odoo companies, heavier automation, or stricter support needs.
- Multiple workspace or company mapping
- Higher MCP call allowance
- Custom create/update policy review
- Operational support package
- Commercial terms matched to usage
Commercial questions answered upfront.
What is included in KSRO Odoo Online MCP pricing?
Paid KSRO Odoo Automation includes one validated Odoo Online workspace, Claude OAuth access, read-only Odoo MCP tools, 15,000 MCP tool calls per calendar month, activity logs, usage limits, encrypted credential handling, and setup support.
Does KSRO support write access from Claude to Odoo?
Yes. KSRO supports create and update workflows through admin-approved write policies. Write access is never enabled by default: KSRO must approve the exact Odoo models and operations, and writes use a prepare-and-confirm flow before data is committed.
Can customers stay read-only?
Yes. Read-only access is the default and is enough for sales, accounting, inventory, purchase, CRM, product, and performance analysis when the connected Odoo user can read those apps.
How are write tools enabled?
Write tools are disabled until KSRO marks the workspace as paid and approves the exact Odoo models and operations. Odoo permissions are still checked by the connected user account, so the source system remains the final authority.
What happens when a cap is reached?
Claude receives a clear usage-limit message. The workspace remains visible, but MCP tool calls pause until KSRO activates paid access or adjusts the allowance.
Can a higher-volume customer get a custom allowance?
Yes. Business Direct is for heavier Claude usage, multiple Odoo companies, stricter support requirements, or a larger approved write policy.
Why not charge much less?
Because KSRO is operating the hosted gateway, OAuth layer, encrypted credential store, validation checks, quota enforcement, logs, billing controls, and support path. Pricing has to cover reliable operation, not only the first connection.
Do customers need to host anything?
No. KSRO hosts the MCP endpoint. Customers keep control of Odoo permissions and API keys, then use one connector URL in Claude.
Validate read-only first. Add paid write automation when it is worth automating.
Start the capped trial, connect Odoo Online, and confirm Claude can read the right business data. After that, choose quarterly, six-month, or annual access and ask KSRO to approve create/update tools for the exact models you need.