2,500+ MCP servers ready to use
Vinkius

Odoo Purchase MCP Server for Claude Desktop 7 tools — connect in under 2 minutes

Built by Vinkius GDPR 7 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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 Purchase 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-purchase": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Odoo Purchase
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 Purchase MCP Server

Connect Odoo ERP to any AI agent — manage your entire business without switching tabs.

Claude Desktop is the definitive way to connect Odoo Purchase to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the Odoo Purchase MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Odoo Purchase

Look for the 🔌 icon in the chat — your 7 tools are now available

Why Use Claude Desktop with the Odoo Purchase MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Odoo Purchase through the Model Context Protocol.

01

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Odoo Purchase + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Odoo Purchase MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Odoo Purchase MCP Tools for Claude Desktop (7)

These 7 tools become available when you connect Odoo Purchase to Claude Desktop via MCP:

01

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

02

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

03

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

04

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

05

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

06

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

07

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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Odoo Purchase immediately.

01

"Search for leads from the website"

02

"Show recent sales orders"

Troubleshooting Odoo Purchase MCP Server with Claude Desktop

Common issues when connecting Odoo Purchase to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Odoo Purchase + Claude Desktop FAQ

Common questions about integrating Odoo Purchase MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.

Connect Odoo Purchase to Claude Desktop

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