Odoo eCommerce MCP Server for Claude Desktop 6 tools — connect in under 2 minutes
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.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Odoo eCommerce and 2,500+ MCP Servers from a single visual interface.




{
"mcpServers": {
"odoo-ecommerce": {
// Your Vinkius token — get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 eCommerce 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 eCommerce to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 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 eCommerce MCP Server exposes 6 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 eCommerce to Claude Desktop via MCP
Follow these steps to integrate the Odoo eCommerce MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using Odoo eCommerce
Look for the 🔌 icon in the chat — your 6 tools are now available
Why Use Claude Desktop with the Odoo eCommerce MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Odoo eCommerce through the Model Context Protocol.
Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network
Odoo eCommerce + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Odoo eCommerce MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Odoo eCommerce MCP Tools for Claude Desktop (6)
These 6 tools become available when you connect Odoo eCommerce to Claude Desktop via MCP:
odoo_list_ecommerce_orders
order records where website_id is set — online store orders only. Returns order number, customer, total, status, website, and date. Use when the user asks about online sales or eCommerce revenue. List orders placed through the Odoo Website storefront with customer, amount, and status
odoo_list_product_categories
category records with full hierarchy path. Use when the user asks about product organization or needs category IDs for product creation. List the product category tree used to organize products in the Odoo shop and inventory
odoo_list_shop_customers
partner records where customer_rank > 0. Returns name, email, phone, city, country. Use for customer analytics or to find buyer contact info. List eCommerce customers who have made purchases, with contact details and location
odoo_list_shop_products
template records where sale_ok=true. Returns product name, sale price, category, type, SKU, stock qty, and website publish status. Use when the user asks about the product catalog or shop inventory. List products available on the Odoo eCommerce shop with prices, stock, and publish status
odoo_list_websites
Returns website name, domain, and creation date. Use when the user asks about available storefronts. List all Odoo websites configured — useful for multi-website or multi-brand setups
odoo_search_shop_products
template by name where sale_ok=true. Returns matching products with price, category, type, SKU, stock, and publish status. Use to find a specific product in the online shop. Search the Odoo eCommerce product catalog by name with prices, stock, and category
Example Prompts for Odoo eCommerce in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with Odoo eCommerce immediately.
"Search for leads from the website"
"Show recent sales orders"
Troubleshooting Odoo eCommerce MCP Server with Claude Desktop
Common issues when connecting Odoo eCommerce to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Odoo eCommerce + Claude Desktop FAQ
Common questions about integrating Odoo eCommerce MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
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.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
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.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect Odoo eCommerce 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 eCommerce to Claude Desktop
Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.
