Skip to content

1.1.0

Choose a tag to compare

@tuanle96 tuanle96 released this 02 Jul 16:08

Community-roadmap release: the server becomes a platform, the 16→19/20 migration wave gets real tooling, and the MCP surface gets typed. 41 tools · 11 prompts · 885 tests.

Highlights

  • Tool plugins — ship your own tools as pip packages (odoo_mcp.tools entry points, stable plugin_api v1). Opt-in only via ODOO_MCP_PLUGINS; fail-isolated; reported in health_check. Runnable example in examples/plugin-example/, guide + threat model in docs/plugins.md.
  • Data-quality pack — new data_quality_report tool: duplicates, missing required values, orphaned references, format anomalies — evidence-first, field-ACL-aware, read-only, async-capable. docs/data-quality.md
  • Migration workbench v1 — new analyze_upgrade_log tool classifies install/update failures into a no_action / needs_review / needs_script worklist with fix suggestions; the same action taxonomy now annotates scan_addons_source and upgrade_risk_report. New workflow prompt pre_migration_data_quality.
  • Typed output schemas — the 10 read tools now advertise real outputSchema (Pydantic models) instead of a generic object; the remaining groups are up for grabs as good first issues.
  • OAuth hardening — issuer validation on introspection responses, ODOO_MCP_AUTH_REQUIRE_ISS / ODOO_MCP_AUTH_REQUIRE_AUD, and a TTL introspection cache (ODOO_MCP_AUTH_CACHE_TTL).
  • One-click install — every release now ships an odoo-mcp-<version>.mcpb bundle for Claude Desktop (requires uv): download, double-click, fill in URL/db/login/API key.
  • Server instructionsODOO_MCP_INSTRUCTIONS_FILE adds your deployment briefing to the MCP instructions field (idea: #19, thanks @oadiazp).
  • Per-deployment tool filteringODOO_MCP_TOOLS_INCLUDE / ODOO_MCP_TOOLS_EXCLUDE trim the surface for small agents.

Fixed

  • XML-RPC ServerProxy now created with allow_none=True — payloads/metadata containing None no longer raise cannot marshal None (#25, thanks @WassoufZ).

Notes

  • MCP spec 2026-07-28 / python-sdk 2.0: migration is fully mapped (spiked against mcp==2.0.0b1); this release stays on mcp>=1.27,<2 — the SDK 2.0 port ships as its own release after the SDK is stable.
  • Full details in the CHANGELOG. Roadmap: #27.