Which Odoo versions are supported?

This server uses the JSON-RPC protocol, which is compatible with Odoo 14, 15, 16, 17, and 18. Both Odoo Community and Enterprise editions are supported.

Does it work with Odoo.com (SaaS)?

Yes! Works with both Odoo.com hosted instances and self-hosted Odoo servers. Just provide your instance URL and API key.

How do I generate an API Key?

Go to Settings → Users → select your user → API Keys tab → New API Key. Give it a descriptive name and copy the generated key.

Odoo Inventory MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Odoo Inventory
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to Odoo Inventory through the Vinkius — pass the Edge URL in the `mcps` parameter and every Odoo Inventory tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Odoo Inventory Specialist",
    goal="Help users interact with Odoo Inventory effectively",
    backstory=(
        "You are an expert at leveraging Odoo Inventory tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Odoo Inventory "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Odoo Inventory MCP Server

Connect Odoo ERP to any AI agent — manage your entire business without switching tabs.

When paired with CrewAI, Odoo Inventory becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Odoo Inventory tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

CRM — Search and create leads, track opportunities through your pipeline
Contacts — Find individual contacts and companies, create new partners
Sales — List and manage sales orders with full order details
Notes — Add comments and notes to any record in your Odoo instance

The Odoo Inventory MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Odoo Inventory to CrewAI via MCP

Follow these steps to integrate the Odoo Inventory MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 9 tools from Odoo Inventory

Why Use CrewAI with the Odoo Inventory MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Odoo Inventory through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Odoo Inventory + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Odoo Inventory MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Odoo Inventory for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Odoo Inventory, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Odoo Inventory tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Odoo Inventory against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Odoo Inventory MCP Tools for CrewAI (9)

These 9 tools become available when you connect Odoo Inventory to CrewAI via MCP:

odoo_get_transfer

picking record with all fields including move line IDs. Use after listing transfers to drill into a specific receipt, delivery, or internal transfer for full details. Get complete details of a specific stock transfer including its individual stock move lines

odoo_list_adjustments

quant records where inventory_quantity_set is true — these are quants with a proposed adjustment that has not yet been applied. Use when the user asks about pending stock corrections, cycle count discrepancies, or inventory adjustments awaiting approval. List pending inventory adjustments that need to be validated or reviewed by a warehouse manager

odoo_list_locations

location records with usage="internal" — the physical locations where stock is stored. Returns location name, full hierarchical path (e.g., WH/Stock/Zone A), and parent warehouse. Use when the user needs to find specific storage locations, plan inventory placement, or understand the warehouse structure. List internal stock locations (bins, zones, shelves) within Odoo warehouses

odoo_list_stock_moves

move records ordered by date descending. Each move represents a single product movement from one location to another. Returns product name, quantity, state, origin/destination locations, and source document. Use when the user needs a granular audit trail of what moved where and when. List recent individual stock movements showing product, quantity, source, destination, and processing state

odoo_list_transfers

picking records — each represents a batch of stock moves like incoming shipments, outgoing deliveries, or internal transfers. Returns transfer reference, partner, operation type, state (draft/waiting/confirmed/assigned/done), source document (e.g., SO or PO number), scheduled date, and source/destination locations. Filter by state to see only pending, ready, or completed transfers. List stock transfers (receipts, deliveries, internal moves) in Odoo with their current processing status

odoo_list_warehouses

warehouse records. Each warehouse has a name, short code (e.g., WH, WH2), and linked partner/address. Warehouses are the top-level organizational unit in Odoo Inventory. Use when the user asks about warehouse locations, needs warehouse codes for transfers, or wants an overview of the logistics network. List all configured warehouses in Odoo with their short codes and addresses

odoo_product_stock

quant records for the given product ID, showing quantity and reserved quantity at each internal location. Use when the user needs to know WHERE stock is located, not just the total — e.g., "how much of Product X is in Warehouse A vs Warehouse B?" Get detailed stock levels for a specific product broken down by warehouse location

odoo_search_inventory_products

product records (variants) by name. Returns product name, internal reference (SKU), quantity on hand (qty_available), forecasted quantity (virtual_available), incoming qty, outgoing qty, category, and product type. Use when the user wants to check stock levels, find products with low inventory, or verify availability before fulfillment. Search products in Odoo Inventory with real-time stock quantities, including available, incoming, and outgoing

odoo_search_lots

lot records by name/number. Returns lot name, associated product, and total quantity in that lot. Use for traceability — when the user needs to find which products belong to a specific batch, or trace a serial number back to its origin. Search for lot numbers or serial numbers in Odoo to trace product batches

Example Prompts for Odoo Inventory in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Odoo Inventory immediately.

"Search for leads from the website"

"Show recent sales orders"

Troubleshooting Odoo Inventory MCP Server with CrewAI

Common issues when connecting Odoo Inventory to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Odoo Inventory + CrewAI FAQ

Common questions about integrating Odoo Inventory MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.