Skip to Content

AI Tool Calls via MCP

by
Odoo

$ 149.00

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 4788
Technical Name mcp_outbound_at
LicenseOPL-1
Websitehttps://www.arure.tech
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 4788
Technical Name mcp_outbound_at
LicenseOPL-1
Websitehttps://www.arure.tech
For Odoo 19 · AI tool calling · MCP client · 9,400+ services

AI Tool Calls via MCP

AI tool calling for Odoo. Your automation rules, scheduled actions, and server actions reach Slack, Notion, GitHub, Google Drive, Postgres, and 9,400+ external services through the open Model Context Protocol (MCP). No Zapier middleware. No SaaS holding your credentials. Audit-logged, rate-limited, self-hosted.

The first MCP client for Odoo. 23 modules expose Odoo as an MCP server — this one is the inverse, letting Odoo invoke tools on external MCP servers.

$149
Per database
9,400+
MCP servers reachable
90 days
Refund window
15/15
Tests passing
support@arure.tech WhatsApp +1 858 463 4405

What you get

Four guarantees, every install. Set up once, runs every day.

Call from any automation rule
Call MCP Tool plugs straight into the standard automation-rule UI — no Python, no scheduler glue, no external runner.
9,400+ services in the MCP registry
Slack, Notion, GitHub, Drive, internal services, and the rest of the public MCP registry. JSON-RPC 2.0 and Streamable-HTTP supported.
Per-call audit log with full request and response
Per-invocation row with request, response, latency, source record — production-grade observability from day one.
Self-hosted, no Zapier middleware
No Zapier middleware. No external service holding your credentials. Your Odoo, your egress, your secrets.

Who this is for

Operations engineers
You run automations on Odoo and want to extend their reach without standing up another integration platform.
Internal-tools teams
You expose internal services as MCP servers and want Odoo to be one of the consumers.
Founders & SaaS builders
You want Odoo to talk to whatever you ship next without a connector backlog.

See it running

Real screenshots from a fresh Odoo 19 instance, organised the way you'll meet the module — setup first, then daily use, then the audit trail. Click any image to view full size.

Set it up

Register an MCP server (Slack workspace shown)
Register an MCP server (Slack workspace shown)
Server registry: every MCP server in one place
Server registry: every MCP server in one place

Use it daily

Discovered tools: what each server exposes
Discovered tools: what each server exposes
Live activity log: every call across every server
Live activity log: every call across every server
Drill into a single call: request, response, latency
Drill into a single call: request, response, latency

Trust it

Failed call: full error message and retry context
Failed call: full error message and retry context

Common scenarios

Three patterns Odoo automations now reach external services for.

Customer created -> Slack notification
Odoo automation rule fires on res.partner creation. Calls the Slack MCP server's send-message tool with the customer name, account manager, and link back to Odoo. No webhook configuration on Slack's side.
Stock movement -> external warehouse system
Internal MCP server exposes your warehouse-system actions. Odoo's stock.picking on-confirm trigger calls the right tool with picking ref, SKUs, quantities. Failed calls surface in the audit log with full request and response.
Internal automation reaching company tools
Notion, GitHub, Drive, Postgres, internal services — anything with an MCP server is callable from any Odoo automation. One declarative configuration covers the whole MCP registry, today and as it grows.

Frequently asked

Yes. The Model Context Protocol is an open spec (originally introduced by Anthropic, now used widely). This module implements the client side — meaning your Odoo can call any MCP-compliant server.

Webhooks are point-to-point and require code on each end. MCP is a structured protocol with a registry — one client implementation reaches every server in the ecosystem. This module IS that one client.

No. Add an MCP server through the standard Odoo configuration UI (URL, optional auth header), then drop a Call MCP Tool action onto any automation rule. No Python required.

Server credentials are stored encrypted on the connector instance. Outbound calls add the auth header automatically. Secrets never appear in the audit log payloads.

No — this module is the OUTBOUND direction (Odoo as MCP client). Inbound MCP is on our roadmap as a separate module.

The audit-log entry captures the error, the automation rule's standard error path runs, and the request can be retried automatically by the connector's queue. Full exception detail is available for debugging.

Yes. The module hooks into Odoo's standard automation framework and stable public APIs. Bug fixes and security patches are committed for 12 months after Odoo 21 ships.

Yes. Each MCP server can be scoped to one or more companies. Audit logs are filtered by the active company.

Because shipping a new category onto the App Store is expensive, and we entitle every buyer to a 90-day no-questions-asked refund and 1-business-day support response. The price reflects ongoing maintenance, not the 5 minutes it takes to install.

No. Per Odoo's policy, third-party paid apps cannot be installed on Odoo Online. This module runs on Odoo.sh and on-premise (self-hosted Community or Enterprise) deployments.

Evaluate before you commit. Buy when you're confident.

You have up to 90 days to claim a full refund. Reach us through any channel below — we reply within 1 business day.

Email
support@arure.tech
Setup questions, refund requests, anything else.
WhatsApp
+1 858 463 4405
Quick questions, same-business-day reply.
Live chat
Chat with us
Quick technical questions, no waiting on email.

What's New

Release notes for every published version. The full CHANGELOG.md is included inside the module package.

v19.0.1.0.0 2026-05-08 Latest

Initial Odoo 19 release — outbound MCP client

What's in the box
  • Register any MCP server through the standard Odoo configuration UI.
  • Call MCP Tool action drops onto any automation rule, scheduled action, or server action — no Python required.
  • Per-invocation audit log capturing request, response, latency, and source record.
  • JSON-RPC 2.0 and Streamable-HTTP transports supported out of the box.
Quality & safety
  • 15 unit tests passing on a fresh Odoo 19.
  • Encrypted credential storage, secrets scrubbed from audit-log payloads.
  • Built on connector_common_at — the same audit/queue/retry foundation as our flagship connectors.

License

Odoo Proprietary License (OPL-1). Per-database license. Source code included; not redistributable.

Trademarks

Odoo is a registered trademark of Odoo S.A. This module is an independent extension developed by Arure Technologies and is not affiliated with, endorsed by, or sponsored by Odoo S.A.

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.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.