convez.ai
MCP ServerIntegração & APIsAvançado
Viindoo

Odoo MCP Client

Viindoo/odoo-mcp-client

Kit de workforce AI para Odoo com MCP integration, skills e agents

Ver no GitHub
BomPluginScore · de 0 a 100

Cliente MCP que integra o servidor Odoo Semantic ao Claude, fornecendo um kit completo de ferramentas de IA para engenharia, vendas, marketing e automação de workflows. Inclui 40 skills, 7 agentes e 9 comandos orquestrados via YAML declarativo para conectar-se a instâncias Odoo v8+.

Instalação

$npx convez-ai Viindoo/odoo-mcp-client

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
9
Forks
7
Acompanhando
0
Saúde
75%
Último commit
há 15 horas
Versão
—
Issues abertas
3
Contribuidores
1

Casos de uso

  • Automatizar workflows complexos no Odoo via orquestração YAML
  • Conectar Claude como agente IA nativo ao Odoo para suportar múltiplas personas
  • Testar e validar lógica de UI e processos de negócio no ERP

Veredito

MCP server robusto e bem arquitetado para integração profunda Claude-Odoo, com orquestração declarativa e cobertura ampla de personas. Requer conhecimento técnico de Odoo e MCP, mas libera alto potencial de automação empresarial.

README

A tradução para o português deste README ainda está na fila.

Odoo MCP Client

License: MIT Backend: AGPL-3.0

odoo-mcp-client is the MIT-licensed client layer that brings the Odoo Semantic MCP server into your AI agent as an Odoo workforce toolkit - covering engineering, sales, marketing, strategy, onboarding, and visual UI testing. Hosted instance: odoo-semantic.viindoo.com - API key and install guide: /install

flowchart TB
    You["You<br/>(natural-language intent)"]

    subgraph client["odoo-mcp-client (MIT)"]
        direction TB
        intake["intake<br/>universal front door"]
        wfrunner["workflow-chaining<br/>declarative YAML executor"]
        skills["odoo-semantic-skills<br/>40 skills / 7 agents / 9 commands"]
        mcp["odoo-semantic-mcp<br/>MCP connection + /connect"]
        intake --> wfrunner --> skills
        intake --> skills
        skills -. "depends on" .-> mcp
    end

    server["OSM MCP Server (AGPL-3.0)<br/>25 tools / 7 resources · indexed Odoo v8+"]
    out["Answer in chat<br/>or file in .odoo-ai/"]

    You --> intake
    You -. "or a skill fires directly" .-> skills
    skills --> server
    mcp --> server
    server --> out

All knowledge and computation live on the OSM server; this repo is a thin routing and orchestration layer.

What is in this repo

This is a monorepo of two Claude Code plugins under plugins/. Each has its own detailed README - start there for usage, install, and reference:

PluginWhat it isREADME
odoo-semantic-skillsThe full Odoo AI workforce toolkit: 40 skills + 7 agents + 9 commands across 9 personas, plus 12 declarative workflows and the drive-to-done orchestration harness. Depends on odoo-semantic-mcp (auto-installed).README
odoo-semantic-mcpThe thin MCP connection layer: registers the odoo-semantic server (25 tools / 7 resources) and ships the /odoo-semantic-mcp:connect command. Install this alone for raw MCP tools only.README

Most users install odoo-semantic-skills, which pulls in odoo-semantic-mcp automatically as a declared dependency - the skills, agents, commands, and the MCP connection all arrive in one step.

Quick install (Claude Code)

Full toolkit (recommended) - skills + agents + commands + MCP, in three steps:

/plugin marketplace add Viindoo/claude-plugins   # one-time, if not already registered
/plugin install odoo-semantic-skills@viindoo-plugins   # auto-pulls odoo-semantic-mcp
/odoo-semantic-mcp:connect

MCP-only - if you only want the MCP tools (no persona skills/agents/commands):

/plugin install odoo-semantic-mcp@viindoo-plugins
/odoo-semantic-mcp:connect

Either way, restart Claude Code afterward so the MCP tools load. You will need an API key (format osm_...) from the install page and the MCP server URL (default https://odoo-semantic.viindoo.com/mcp). Per-plugin install notes, browser MCP setup, and other-AI-tool configs are in each plugin's README.

Migration / upgrading from v1.x

The single odoo-semantic plugin has been split and renamed into odoo-semantic-skills and odoo-semantic-mcp. If you previously installed the old odoo-semantic plugin, uninstall it and reinstall the new plugins:

/plugin uninstall odoo-semantic@viindoo-plugins
/plugin install odoo-semantic-skills@viindoo-plugins   # auto-pulls odoo-semantic-mcp
/odoo-semantic-mcp:connect

Then restart Claude Code.

Note: your API key + MCP URL must be re-entered after installing the new MCP plugin - /odoo-semantic-mcp:connect will prompt for them again. The MCP server name (odoo-semantic, tools mcp__odoo-semantic__*) is unchanged, so anything that references the tool namespace keeps working.

Requirements

  • Odoo Semantic MCP server URL - https://odoo-semantic.viindoo.com/mcp (or your self-hosted instance)
  • API key - format osm_<alphanumeric>, obtain from the install page
  • Claude Code with MCP support (v2.1.x or newer)

For contributors - local dev install

Prerequisite: Python 3.12+ (needed by make setup / make test).

Test changes from a checkout without going through the marketplace. Each plugin lives under plugins/ - point --plugin-dir at the one you are working on:

claude --plugin-dir ./plugins/odoo-semantic-skills   # skills + agents + commands
claude --plugin-dir ./plugins/odoo-semantic-mcp      # MCP connection + connect command

See CONTRIBUTING.md for the full plugin-dev workflow, the release / SHA-pinning pipeline, and the DCO sign-off requirement.

Relationship to the server

LayerRepositoryLicense
Client (this repo) - plugins, skills, agents, snippetsViindoo/odoo-mcp-clientMIT
Server - indexer, Neo4j graph, pgvector, MCP server, web UIodoo-semantic.viindoo.comAGPL-3.0-or-later

To use the hosted instance, sign up for an API key at odoo-semantic.viindoo.com/install. Self-hosting instructions are available in the server's own documentation, accessible after registration.

License

MIT - see LICENSE and NOTICE. Brand assets in branding/ are trademarks of Viindoo Technology JSC and are not covered by the MIT grant - see branding/TRADEMARK.md.

Ver o original no GitHub

Bom para

Relacionados