تخطي للذهاب إلى المحتوى
Sadeem MCP — Claude AI Connector

Sadeem MCP — Claude AI Connector

Connect Claude AI to your Odoo via Model Context Protocol

Sadeem Cloud 0 تحميلات OPL-1
السعر
75.00 SR
Includes 12 months of updates
Try Live Demo
الإصدارات المتوافقة
0
التحميلات
1.260809001
Version
Last updated 19/11/2026

Sadeem MCP — Claude AI Connector

Connect Claude AI to your Odoo instance via the Model Context Protocol (MCP).
Ask Claude questions in plain language and get real Odoo data back — no code required.
Everyone signs in with their own Odoo account, so a connector shared across a whole team still gives each person their own permissions.

Community Enterprise Odoo.sh



Watch It in Action

See how Claude AI connects to Odoo live — from setup to running real queries in minutes.

Features

Natural Language Queries

Ask Claude in plain language: "Show me overdue invoices" or "Who are my top customers?" and get real data back instantly.

Search Any Model

Use the search_records tool to query any installed Odoo model with custom domain filters — not limited to built-in tools.

Dynamic Tool Discovery

Tools are enabled automatically based on which modules are installed. Accounting tools appear only if accounting is installed, CRM tools only if CRM is installed, etc.

Per-User Sign-In (OAuth 2.1)

No password in the URL. Each person is sent to your Odoo login — SSO, two-factor and password policy all still apply — and approves the connection themselves. The token that comes back names them, so every request runs under their own access rights and their own name appears in the audit trail.

Safe to Share with a Team

On a Claude Team or Enterprise plan an owner adds the connector once and every member connects individually. Nobody inherits anybody else's Odoo permissions, and a colleague with no Odoo account simply cannot use it.

Read-Only or Full Access

Two permissions, chosen on the approval screen: Read for searching and reporting, Write for creating and confirming. Grant read-only and the write tools are not merely refused — Claude never sees them.

You Decide Who Can Connect

A dedicated MCP: Can Connect group gates the whole feature. Tick a user to let them connect an assistant; untick them and every token they already hold stops working on the very next request.

A Private Endpoint per Database

Your connector URL ends in a random segment unique to this database, so scanners find nothing and strangers cannot probe the endpoint. Leaked the URL? One click issues a new one and disconnects every session.

Every Connection Visible

Administrators see who connected, from which application, with which permissions and when it was last used — and can disconnect any one of them. Users manage their own connections from the Settings page.

Create Records

Use create_record to create invoices, sales orders, leads, and more — directly from Claude. Records are always created as draft for review before confirmation.

Duplicate Records

Use copy_record to duplicate any existing record — invoices, orders, leads — using Odoo's native copy. Faster and more accurate than recreating from scratch.

Bulk Import Records

Use create_records_bulk to import up to 200 records in a single request — ideal for spreadsheet data pasted into Claude. Returns per-record success/failure for full visibility.

Execute Business Actions

Use execute_action to confirm invoices, close opportunities, validate deliveries, and more — in bulk. Every action leaves an internal note in the record's chatter, signed with the name of the person whose connection ran it.

Direct Record URLs

Every tool result includes a direct URL to open the record in Odoo. URLs are built using Odoo's own window actions for accurate deep-linking.

How to Connect Claude AI

Step 1 — Install & Enable

  • Install the Sadeem MCP module from Apps.
  • Go to Settings → Claude AI Connector.
  • Toggle Enable MCP Endpoint to ON.
  • Your connector URL appears, ending in a random segment unique to this database.

Step 2 — Choose Who Can Connect

  • Go to Settings → Users & Companies → Users.
  • Tick MCP: Can Connect for each person allowed to use an AI assistant.
  • Everyone else is refused at the approval screen, even with the URL in hand.

Step 3 — Add the Connector in Claude.ai

  • Open claude.ai → Settings → Connectors.
  • Click Add custom connector and paste the URL from Odoo.
  • Leave the OAuth Client ID and Secret fields empty — Claude registers itself automatically.
  • On a Team or Enterprise plan, an owner does this once for the whole organization.

Step 4 — Sign In and Approve

  • Click Connect. Claude sends you to your own Odoo login page.
  • Sign in as yourself — SSO and two-factor work exactly as they normally do.
  • Choose what to allow: Read only, or Read and Write.
  • Each colleague repeats this step for their own account.

Step 5 — Use in Chat

  • Start a new chat in Claude.ai.
  • Click the + button and enable your Odoo connector.
  • Ask anything: "Show me unpaid invoices", "Who are my top 5 customers?", "List open CRM opportunities".

Requirements

  • HTTPS. Claude will not run a sign-in flow over plain HTTP.
  • Behind a reverse proxy, run Odoo with --proxy-mode so it advertises https:// addresses.
  • A Claude Pro, Team or Enterprise plan, which is what custom connectors require.

Available Tools

The Permission column is what the person approving the connection controls. Grant Read only and the write tools are never offered to Claude at all.

Tool Permission Requires Module Description
search_recordsReadAlwaysSearch any Odoo model with a custom domain filter. Results include a direct URL to each record.
get_model_fieldsReadAlwaysList available fields for any model — use before searching or creating records
copy_recordWriteAlwaysDuplicate any existing Odoo record using Odoo's native copy mechanism. Always created as draft. Supports field overrides (e.g. change date on the copy).
create_recordWriteAlwaysCreate a new record in any model (invoice, order, lead, etc.). Always created as draft. Logs an internal note on creation.
create_records_bulkWriteAlwaysCreate up to 200 records of the same model in a single request. Ideal for importing spreadsheet data. Per-record error isolation with continue_on_error option. Always draft.
execute_actionWriteAlwaysExecute business actions on records: confirm, cancel, validate, mark won/lost, write, write_translation (field translations per language), and more. Supports bulk operations. Logs an internal note after each action.
get_record_urlReadAlwaysGet the direct Odoo URL for any record by model and ID
get_translatable_termsReadAlwaysList the translatable text terms of a record for one language — sentences only, no markup. Marks each term translated, untranslated or stale, with an only_untranslated filter.
set_translationsWriteAlwaysWrite translations term by term through Odoo's own update_field_translations. Partial sets are expected, the source language is never touched, and unknown terms are rejected instead of silently dropped.
get_translation_statusReadAlwaysTranslation coverage per record for one language — total, translated, untranslated and stale term counts, so you can ask which pages are not fully translated yet.
upload_imageWriteAlwaysUpload an image through Odoo's own processing pipeline and get back the exact /web/image URL the website editor produces, ready to paste into HTML. Rejects non-images and oversized uploads.
replace_image_in_fieldWriteAlwaysSwap one image inside an HTML or XML field with proper lxml parsing — the rest of the document, and the editor classes, stay untouched.
list_attachmentsReadAlwaysList existing image attachments with their public URLs so an image can be reused instead of uploaded twice.
get_overdue_invoicesReadAccountingCustomer invoices past their due date
get_upcoming_dueReadAccountingInvoices due in the next N days
get_unpaid_billsReadAccountingVendor bills that are unpaid
get_open_ordersReadSalesConfirmed sales orders not yet fully invoiced
get_top_customersReadSalesTop customers ranked by total sales
get_pending_purchasesReadPurchasePurchase orders waiting for approval or delivery
get_upcoming_vendor_billsReadPurchaseVendor bills due soon
get_open_leadsReadCRMOpen CRM leads and opportunities
get_hot_opportunitiesReadCRMOpportunities with high probability
get_low_stockReadInventoryProducts below their reorder point
get_stock_valueReadInventoryStock valuation by product category

Frequently Asked Questions

Is my Odoo data safe?

Claude never gets a password. It signs in through OAuth 2.1 against your own Odoo login page, and the access token it receives is tied to one Odoo user — so every request is subject to that user's access rights and record rules, exactly as if they had clicked it themselves. Write operations (create_record, execute_action) only succeed where that user could already do the same thing by hand, records are always saved as draft first, and delete is not supported at all. Tokens are stored only as a SHA-256 digest, so even a database dump contains nothing that can be replayed.

Do I need a Claude Pro subscription?

Yes. Custom connectors (MCP) require a Claude Pro or Team plan on claude.ai.

Our whole team shares one connector. Does everybody end up with the same Odoo access?

No — and this is the reason the connector uses OAuth rather than a shared key. On a Claude Team or Enterprise plan an owner adds the connector once and it becomes available across the organization, but the URL carries no credential. Each member still signs in to Odoo as themselves and approves their own connection, so a salesperson sees what a salesperson sees and an accountant sees what an accountant sees. Somebody with no Odoo account, or who is not in the MCP: Can Connect group, simply cannot use it.

Can I give an assistant read-only access?

Yes. The approval screen offers two permissions and you can untick Write. A read-only connection is not simply refused when it tries to change something — the write tools are never advertised to Claude in the first place, so it does not try.

How do I cut off access to somebody who has left?

Untick MCP: Can Connect on their user, or archive it. Their existing tokens stop working on the very next request — the permission is re-checked every time, not only when the connection is first made. You can also disconnect a single connection from Settings → Technical → Claude AI Connector → Connections, and if the connector URL itself has been shared somewhere it should not have been, Generate a new URL moves the endpoint and disconnects everyone at once.

I am upgrading from an older version that used API keys

API key authentication has been removed, and the connector URL has changed. Existing connectors stop working when you upgrade, so plan a few minutes for it: enable the endpoint, add the people who need access to the MCP: Can Connect group, then delete the old custom connector in Claude and add the new URL. Old Odoo API keys are left untouched — revoke them by hand if they existed only for this connector.

Does my Odoo need to be reachable from the internet?

Yes, over HTTPS — Claude runs in Anthropic's cloud and has to reach your server, and it will not run a sign-in flow over plain HTTP. Behind a reverse proxy, start Odoo with --proxy-mode so it advertises https:// addresses. Your connector URL ends in a random segment unique to your database, so the endpoint is not something a scanner can stumble upon: anything else on that path answers with a plain 404.

Can Claude create or modify Odoo records?

Yes — if you granted the Write permission when you approved the connection. create_record creates new records in draft state for your review. execute_action runs business actions (confirm, cancel, validate, etc.) on existing records. Both leave an internal note in the record's chatter, signed with your name, so every AI-initiated change is traceable — and because it is a note rather than a message, nobody following the record gets notified for it. Delete operations are not supported.

What if a tool is not showing for a module I have installed?

Tools are detected by the Odoo technical module name (e.g. account, sale, crm, stock, purchase). Make sure the standard Odoo module is installed, not just a custom extension.


Change Log

Version 1.260809001 - 2026-08-09

Breaking change. API key authentication is removed and the connector URL has changed, so existing connectors must be re-added after upgrading. See the upgrade note in the F.A.Q above.

  • New: per-user OAuth 2.1 sign-in replaces the API key in the URL. Each person signs in to Odoo themselves and approves their own connection, so a connector shared across a Claude organization no longer means a shared Odoo identity — each member gets their own permissions, their own record rules and their own name in the audit trail
  • New: Read and Write permissions, chosen on the approval screen. A read-only connection is never even offered the write tools
  • New: MCP: Can Connect security group decides who may authorize an assistant. Removing someone from it stops the tokens they already hold on the next request
  • New: the connector URL ends in a random segment unique to each database, keeping the endpoint away from scanners. One click issues a new URL and disconnects every session — a kill switch if it ever leaks
  • New: Settings → Technical → Claude AI Connector lists every connection and registered client for administrators; users review and disconnect their own from the Settings page
  • Security: tokens are stored only as a SHA-256 digest, refresh tokens rotate on every use, and a replayed refresh token revokes the whole session. Sign-in uses mandatory PKCE with no client secret anywhere
  • Fix: chatter entries are now internal notes rather than messages. They used to notify every follower of a record for what is only a line saying how it was touched
  • Fix: the Enable MCP Endpoint toggle is now enforced. The setting existed but the endpoint answered whether or not it was switched on
  • Requires HTTPS. Behind a reverse proxy, run Odoo with --proxy-mode
Version 1.260802001 - 2026-08-02
  • New: get_translatable_terms, set_translations and get_translation_status — translate term by term through Odoo's own translation API. Only the sentences travel, never the markup, and the source language is never touched
  • New: upload_image, replace_image_in_field and list_attachments — upload images through Odoo's own processing pipeline and get back the exact URL the website editor produces
  • Deprecated: the write_translation action of execute_action still works unchanged, but set_translations should be used instead
Version 1.260714001 - 2026-07-14
  • New: write_translation action in execute_action — write field translations for any active language (e.g. Arabic content on blog posts) without touching the source language
Version 1.260506001 - 2026-05-06
  • New: create_records_bulk — create up to 200 records in a single request for bulk imports; per-record error isolation with continue_on_error option
Version 1.260504001 - 2026-05-04
  • New: copy_record — duplicate any Odoo record using Odoo's native copy mechanism (draft, with optional field overrides)
Version 1.260329002 - 2026-03-29
  • New: create_record — create any Odoo record as draft from Claude
  • New: execute_action — run business actions (confirm, cancel, validate, etc.) in bulk
  • New: get_record_url — get a direct Odoo URL for any record
  • All tool results now include a direct url field per record
  • Chatter notes posted automatically after create and execute actions
  • URLs built using Odoo's ir.actions.act_window for accurate deep-linking
Version 1.260329001 - 2026-03-29
  • Initial release
  • 13 dynamic tools across Accounting, Sales, Purchase, CRM, Inventory
  • Universal search_records and get_model_fields tools
  • Native Settings page with API key generation

About


Sadeem is an Egyptian registered company established in 2020 under the name Digital X and then the name was changed to Sadeem in 2023.

Website


https://sadeem.cloud

Whatsapp


https://wa.me/201143535115

Recent changes
2026-11-19  fix(sadeem_mcp): label client_id fields 'Client ID'
2026-11-19  fix(sadeem_mcp): report wizards and errors from execute_action
2026-11-19  fix: tool handler and OAuth bugs found while porting to 16.0
2026-08-18  fix: bind the request environment to the token user
2026-08-09  fix: drop expand/string from the search view group on 19.0
2026-08-09  fix: declare mcp_can_connect in the settings view
2026-08-09  port: adapt the OAuth work to Odoo 19.0
2026-08-09  docs: update the store listing for OAuth authentication
2026-08-09  fix: log chatter entries as internal notes instead of messages
2026-08-09  fix: rename _register, which collides with a reserved ORM attribute
2026-08-09  feat!: replace API-key auth with per-user OAuth 2.1
2026-08-03  fix: make translation counts deterministic and never silently low
2026-08-03  fix: stop a missing ledger table from aborting the transaction
2026-08-03  feat: add term-level translation and image tools to sadeem_mcp
2026-07-14  feat: add write_translation action to execute_action in sadeem_mcp
Technical Name
sadeem_mcp
Category
Technical
Module Version
1.260809001
Lines of Code
7255
Website
https://sadeem.cloud
Dependencies
base web mail base_setup

Log in to review modules you purchased.

No reviews yet.

License: OPL-1

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.