Odoo Claude MCP

What rosenvladimirov/odoo-claude-mcp MCP server does

The rosenvladimirov/odoo-claude-mcp MCP server exposes Odoo data and operations through the Model Context Protocol. It is designed for self-hosted Odoo installations running versions 15 through 19 and provides a single MCP surface for Claude, Claude Code, Claude Desktop, and other compatible clients.

The suite combines an Odoo RPC service with supporting services for GitHub, OCA repositories, filesystem access, Portainer, Microsoft Teams, and a browser-based Claude Code terminal. The repository describes more than 197 tools: 92 native tools and 105 proxied tools. Included Odoo-oriented workflows cover record operations, module deployment through RPC, semantic search, memory, and Bulgaria-related fiscal and VAT functionality.

How it works

Clients connect to a unified gateway over HTTPS with a bearer token. The gateway routes requests to the backend MCP services and can apply shared authentication, user profiles, Odoo connections, memory storage, and audit logging. One deployment can serve multiple Odoo databases and tenants rather than requiring a separate process for every connection.

The Odoo service communicates with Odoo through RPC. Qdrant provides the vector-store component for semantic search, while Ollama supports local language-model and embedding use cases. The terminal component combines xterm.js and tmux to provide browser-based access to Claude Code.

Setup and configuration

The rosenvladimirov/odoo-claude-mcp MCP server can be deployed with Docker Compose for local development or with K3s/Kubernetes and Kustomize overlays. The documented Compose flow clones the repository, copies .env.example to .env, sets the Odoo URL, database, username, credentials, and tokens, then starts the stack with docker compose up -d.

The default Compose profile starts the core services. Portainer and Microsoft Teams are optional and can be enabled with the portainer, teams, or full profiles. A local Compose override is available when no Cloudflare sidecar is being used. The repository also documents Linux/macOS and Windows installer scripts.

After deployment, clients can connect through the /mcp endpoint using an authorization header. The stack exposes a health endpoint at http://localhost:8084/health for verification.

Tools and capabilities

The rosenvladimirov/odoo-claude-mcp MCP server supports:

• Odoo CRUD and RPC-based operations across Odoo 15–19
• Multi-connection and multi-tenant deployments
• Odoo module, view, and data deployment through RPC
• GitHub and OCA repository workflows
• Filesystem operations and a browser terminal using xterm.js and tmux
• Optional Portainer and Microsoft Teams MCP services
• Qdrant-backed semantic search and Ollama-based local model support
• Bulgaria localization features involving НАП, fiscal positions, and VAT
• Token-based gateway authentication, per-user profiles, audit logs, and rate limiting

Limitations and notes

This project is self-hosted and requires a reachable Odoo instance plus deployment configuration. Odoo credentials or API keys must be supplied for the RPC service. Portainer and Teams are not started by the default Compose command and require their own environment variables when enabled. Public Claude.ai connectivity requires an HTTPS endpoint and token authentication. The material does not establish compatibility with every MCP client or define the complete environment-variable list, so optional integrations should be configured from the repository's .env.example and deployment files.