2,500+ MCP servers ready to use
Vinkius

Odoo Manufacturing MCP Server for CrewAI 7 tools — connect in under 2 minutes

Built by Vinkius GDPR 7 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Odoo Manufacturing Specialist",
    goal="Help users interact with Odoo Manufacturing effectively",
    backstory=(
        "You are an expert at leveraging Odoo Manufacturing 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 Manufacturing "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 7 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Odoo Manufacturing
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 Manufacturing MCP Server

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

When paired with CrewAI, Odoo Manufacturing becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Odoo Manufacturing 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 Manufacturing MCP Server exposes 7 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 Manufacturing to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py — CrewAI auto-discovers 7 tools from Odoo Manufacturing

Why Use CrewAI with the Odoo Manufacturing MCP Server

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

01

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

02

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

03

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

04

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 Manufacturing + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Odoo Manufacturing MCP Tools for CrewAI (7)

These 7 tools become available when you connect Odoo Manufacturing to CrewAI via MCP:

01

odoo_create_manufacturing_order

production record in "draft" state. Requires a product.product ID and desired quantity. Odoo will auto-select the default BOM if bomId is not specified. Once confirmed, the system will check component availability and create work orders if the BOM has routing operations. Use when the user wants to schedule new production, replenish stock via manufacturing, or create a custom production run. Create a new manufacturing order to produce a specific product quantity, optionally with a specific Bill of Materials

02

odoo_get_bom_components

bom.line records for the given BOM ID, showing each raw material/component needed, its required quantity, and unit of measure. Use when the user needs to know what materials are needed to manufacture a product, wants to verify component quantities, or is planning material procurement. Get the component list (raw materials and quantities) of a specific Bill of Materials

03

odoo_get_manufacturing_order

production record with all key fields for drill-down analysis. Use after listing MOs to inspect a specific production order — e.g., to check how much has been produced vs planned, which BOM is being used, or the planned start date. Get the complete details of a specific manufacturing order including product, BOM, quantities, and progress

04

odoo_list_boms

bom records — the recipes/formulas that define how products are manufactured. Returns BOM name, finished product, quantity produced per BOM, BOM type (normal manufacturing vs kit), and reference code. Use when the user asks about product recipes, manufacturing formulas, component lists, or needs to find a BOM ID for creating manufacturing orders. List all Bills of Materials (BOMs) in Odoo showing the finished product, quantity, type, and reference code

05

odoo_list_manufacturing_orders

production records showing all manufacturing orders across the shop floor. Returns MO reference number, product being manufactured, planned quantity, quantity already produced, production state (draft/confirmed/progress/done/cancel), linked Bill of Materials, and planned start date. Filter by state to focus on orders in progress, waiting for materials, or completed. Use when the user asks about production activity, shop floor status, manufacturing backlog, or wants to check which products are being produced. List manufacturing orders (production orders) in Odoo with product, planned quantity, BOM, and production status

06

odoo_list_work_centers

workcenter records — the physical or logical production resources where operations are performed. Returns work center name, code, capacity, time efficiency percentage, and active status. Use when the user asks about available production resources, machine capacity, or needs work center codes for planning. List all work centers (machines, stations, production lines) configured in Odoo Manufacturing

07

odoo_list_work_orders

workorder records — the individual operations within manufacturing orders. Each work order represents a step in the production routing (e.g., cutting, assembly, painting). Returns work order name, product, assigned work center, state (pending/ready/progress/done), expected duration, and linked production order. Use when the user asks about shop floor activity, operator assignments, or production bottlenecks. List active work orders on the shop floor showing product, assigned work center, state, and estimated duration

Example Prompts for Odoo Manufacturing in CrewAI

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

01

"Search for leads from the website"

02

"Show recent sales orders"

Troubleshooting Odoo Manufacturing MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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 Manufacturing + CrewAI FAQ

Common questions about integrating Odoo Manufacturing MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Odoo Manufacturing to CrewAI

Get your token, paste the configuration, and start using 7 tools in under 2 minutes. No API key management needed.