2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 9 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Odoo Inventory as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
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 Inventory. "
            "You have 9 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Odoo Inventory?"
    )
    print(response)

asyncio.run(main())
Odoo Inventory
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.

LlamaIndex agents combine Odoo Inventory 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 Inventory 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 Inventory to LlamaIndex via MCP

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 9 tools from Odoo Inventory

Why Use LlamaIndex with the Odoo Inventory MCP Server

LlamaIndex provides unique advantages when paired with Odoo Inventory through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine Odoo Inventory tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Odoo Inventory tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Odoo Inventory, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Odoo Inventory tools were called, what data was returned, and how it influenced the final answer

Odoo Inventory + LlamaIndex Use Cases

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

01

Hybrid search: combine Odoo Inventory real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Odoo Inventory to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Odoo Inventory for fresh data

04

Analytical workflows: chain Odoo Inventory queries with LlamaIndex's data connectors to build multi-source analytical reports

Odoo Inventory MCP Tools for LlamaIndex (9)

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

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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 LlamaIndex

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

01

"Search for leads from the website"

02

"Show recent sales orders"

Troubleshooting Odoo Inventory MCP Server with LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Odoo Inventory + LlamaIndex FAQ

Common questions about integrating Odoo Inventory MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Odoo Inventory tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Odoo Inventory to LlamaIndex

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