Odoo HR MCP Server for LlamaIndex 9 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Odoo HR as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token — get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Odoo HR. "
"You have 9 tools available."
),
)
response = await agent.run(
"What tools are available in Odoo HR?"
)
print(response)
asyncio.run(main())
* 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.
LlamaIndex agents combine Odoo HR tool responses with indexed documents for comprehensive, grounded answers. Connect 9 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.
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 LlamaIndex 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 LlamaIndex via MCP
Follow these steps to integrate the Odoo HR MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 9 tools from Odoo HR
Why Use LlamaIndex with the Odoo HR MCP Server
LlamaIndex provides unique advantages when paired with Odoo HR through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Odoo HR tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Odoo HR tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Odoo HR, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Odoo HR tools were called, what data was returned, and how it influenced the final answer
Odoo HR + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Odoo HR MCP Server delivers measurable value.
Hybrid search: combine Odoo HR real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Odoo HR to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Odoo HR for fresh data
Analytical workflows: chain Odoo HR queries with LlamaIndex's data connectors to build multi-source analytical reports
Odoo HR MCP Tools for LlamaIndex (9)
These 9 tools become available when you connect Odoo HR to LlamaIndex 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 LlamaIndex
Ready-to-use prompts you can give your LlamaIndex agent to start working with Odoo HR immediately.
"Search for leads from the website"
"Show recent sales orders"
Troubleshooting Odoo HR MCP Server with LlamaIndex
Common issues when connecting Odoo HR to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpOdoo HR + LlamaIndex FAQ
Common questions about integrating Odoo HR MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
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 LlamaIndex
Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.