2,500+ MCP servers ready to use
Vinkius

Odoo Inventory MCP Server for VS Code Copilot 9 tools — connect in under 2 minutes

Built by Vinkius GDPR 9 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Odoo Inventory and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "odoo-inventory": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
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.

GitHub Copilot Agent mode brings Odoo Inventory data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Odoo Inventory MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Odoo Inventory

Ask Copilot: "Using Odoo Inventory, help me...". 9 tools available

Why Use VS Code Copilot with the Odoo Inventory MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Odoo Inventory through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Odoo Inventory + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Odoo Inventory MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Odoo Inventory MCP Tools for VS Code Copilot (9)

These 9 tools become available when you connect Odoo Inventory to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Odoo Inventory + VS Code Copilot FAQ

Common questions about integrating Odoo Inventory MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Odoo Inventory to VS Code Copilot

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