Odoo HR MCP Server for CrewAI 9 tools — connect in under 2 minutes
Connect your CrewAI agents to Odoo HR through Vinkius, pass the Edge URL in the `mcps` parameter and every Odoo HR 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 HR Specialist",
goal="Help users interact with Odoo HR effectively",
backstory=(
"You are an expert at leveraging Odoo HR 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 HR "
"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)
* 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 HR MCP Server
Connect Odoo ERP to any AI agent — manage your entire business without switching tabs.
When paired with CrewAI, Odoo HR becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Odoo HR 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 HR 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 HR to CrewAI via MCP
Follow these steps to integrate the Odoo HR 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 HR
Why Use CrewAI with the Odoo HR MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Odoo HR 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 HR + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Odoo HR MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Odoo HR 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 HR, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Odoo HR 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 HR against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Odoo HR MCP Tools for CrewAI (9)
These 9 tools become available when you connect Odoo HR to CrewAI via MCP:
odoo_create_leave
leave record in "draft" state. Requires the employee ID (from odoo_search_employees), leave type ID (from odoo_list_leave_types), and date range in format "YYYY-MM-DD HH:MM:SS". The request goes through the standard approval workflow. Use when the user wants to request time off for an employee. Submit a leave request for an employee with specific leave type, start date, and end date
odoo_list_attendance
attendance records ordered by check-in time descending. Returns employee name, check-in timestamp, check-out timestamp (if clocked out), and total worked hours. Use when the user asks about who is currently working, attendance history, or daily hours tracking. List employee attendance records (check-in/check-out times and worked hours) from Odoo
odoo_list_departments
department records showing the organizational structure. Returns department name, department manager, parent department (for hierarchy), and total employee count. Use when the user asks about org structure, department headcounts, or management hierarchy. List all departments in Odoo HR with their managers, parent departments, and headcount
odoo_list_employees
employee records — the full employee directory. Returns name, department, job title, work email, and direct manager for each employee. Use for a headcount overview, department composition analysis, or when the user wants to browse the org chart. List all employees in the Odoo HR directory with departments, job titles, and contact information
odoo_list_expenses
expense records ordered by date. Returns expense description, employee, state (draft/reported/approved/done/refused), total amount, and date. Use when the user asks about pending expense reports, reimbursement requests, or wants to review recent employee expenses. List employee expense reports in Odoo with amounts, approval status, and submission dates
odoo_list_jobs
job records — the defined job positions in the organization. Returns job title, department, number of open recruitments, and recruitment state. Use when the user asks about open positions, hiring pipeline, or workforce planning. List open job positions and recruitment status in Odoo HR with department and vacancy count
odoo_list_leave_types
leave.type records — the categories of leave employees can request. Returns type name and configuration. Use to find the correct leave type ID before creating a leave request, or when the user asks what kinds of time off are available. List available leave types (Paid Time Off, Sick Leave, Unpaid, etc.) configured in Odoo HR
odoo_list_leaves
leave records ordered by date. Returns employee name, department, leave type (e.g., Paid Time Off, Sick Leave), state (draft/confirm/validate/refuse), number of days, and date range. Use when the user asks about upcoming absences, pending leave approvals, vacation schedules, or team availability. List leave requests (vacation, sick, personal days) in Odoo with approval status and duration
odoo_search_employees
employee records by name. Returns employee name, department, job title/position, work email, direct manager, and hire date. Use when the user wants to find a specific employee, look up their department or manager, or get contact details for an internal team member. Search employees in Odoo by name, returning their department, job title, email, and manager
Example Prompts for Odoo HR in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Odoo HR immediately.
"Search for leads from the website"
"Show recent sales orders"
Troubleshooting Odoo HR MCP Server with CrewAI
Common issues when connecting Odoo HR 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 HR + CrewAI FAQ
Common questions about integrating Odoo HR 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 HR 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 HR to CrewAI
Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.