Odoo Purchase MCP Server for CrewAI 7 tools — connect in under 2 minutes
Connect your CrewAI agents to Odoo Purchase through Vinkius, pass the Edge URL in the `mcps` parameter and every Odoo Purchase tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Odoo Purchase Specialist",
goal="Help users interact with Odoo Purchase effectively",
backstory=(
"You are an expert at leveraging Odoo Purchase 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 Purchase "
"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)
* 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 Purchase MCP Server
Connect Odoo ERP to any AI agent — manage your entire business without switching tabs.
When paired with CrewAI, Odoo Purchase becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Odoo Purchase tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through 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 Purchase 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 Purchase to CrewAI via MCP
Follow these steps to integrate the Odoo Purchase 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 7 tools from Odoo Purchase
Why Use CrewAI with the Odoo Purchase MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Odoo Purchase 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 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 Purchase + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Odoo Purchase MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Odoo Purchase 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 Purchase, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Odoo Purchase 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 Purchase against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Odoo Purchase MCP Tools for CrewAI (7)
These 7 tools become available when you connect Odoo Purchase to CrewAI via MCP:
odoo_confirm_purchase_order
order, transitioning from "draft" to "purchase" state. This locks the order, notifies the vendor, and creates an incoming receipt (stock.picking) for warehouse processing. Use when the user approves a vendor quote or wants to place the order. Confirm a draft RFQ, converting it into a confirmed purchase order and triggering receipt creation
odoo_create_purchase_order
order in "draft" state (an RFQ). The partnerId must be an existing vendor (res.partner with supplier_rank > 0) — use odoo_search_vendors to find vendor IDs. Lines must be a JSON array: [{"product_id": <id>, "product_qty": <qty>, "price_unit": <cost>}]. Each line also gets an auto-generated description. Create a new purchase order (as a draft RFQ) for a vendor with product lines, quantities, and prices
odoo_get_po_lines
order.line records for the given PO. Returns each line with product name, ordered quantity, unit cost, subtotal, and planned delivery date. Use to inspect what is being purchased, verify pricing, or check delivery schedules per line item. Get the individual line items of a purchase order showing products, quantities, costs, and expected delivery dates
odoo_get_purchase_order
order with all key fields. Use after listing POs to drill into a specific order for vendor details, amounts, and expected receipt dates. Get the complete details of a specific purchase order by its numeric ID
odoo_list_purchase_orders
order records ordered by creation date. Returns PO number, vendor name, state (draft/sent/purchase/done/cancel), total and untaxed amounts, responsible buyer, expected receipt date, and order date. Filter by state to see only draft RFQs, confirmed POs, or completed orders. Use when the user asks about procurement activity, pending orders, or vendor purchases. List purchase orders in Odoo with vendor, amounts, buyer, and current processing status
odoo_list_rfqs
order records in "draft" state only. These are RFQs that need vendor pricing, negotiation, or approval before being confirmed. Use when the user asks specifically about pending RFQs, quotes from vendors, or procurement requests awaiting approval. List all Requests for Quotation (draft purchase orders) that have not yet been confirmed to vendors
odoo_search_vendors
partner records where supplier_rank > 0 — these are partners flagged as vendors/suppliers. Returns vendor name, email, phone, city, and country. Use to find vendor IDs before creating purchase orders, or when the user asks about supplier information. Search for vendors and suppliers in Odoo by name, returning contact details and location
Example Prompts for Odoo Purchase in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Odoo Purchase immediately.
"Search for leads from the website"
"Show recent sales orders"
Troubleshooting Odoo Purchase MCP Server with CrewAI
Common issues when connecting Odoo Purchase to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Odoo Purchase + CrewAI FAQ
Common questions about integrating Odoo Purchase MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Odoo Purchase with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Odoo Purchase to CrewAI
Get your token, paste the configuration, and start using 7 tools in under 2 minutes. No API key management needed.