LABSCO SUMMARY

One call per question, and the answer arrives with a verdict instead of rows to interpret.

pipeline_review, receivables_health and project_dashboard each stand in for a handful of queries plus the joining you would otherwise do afterwards — project_dashboard replaces around twelve separate calls on its own. The verdicts are rule-based and their thresholds are arguments, so calibrating what counts as stalled or overdue in your business is a parameter rather than a fork. Writes are deliberately hard to reach: read-only is the default, the model has to be on an allow-list, deletes need a further switch, and every write returns a preview until confirm=true — the risky path is one you walk into on purpose. If there is no Odoo to point at yet, the repository ships a seeded demo instance to run business_pulse against.

What it is

An analytics layer over an Odoo ERP, reached through Odoo's standard XML-RPC external API with nothing to install inside Odoo. Where a CRUD bridge hands back rows, these tools compose a whole management question into one structured report with a verdict attached. It works on Odoo Online, Odoo.sh and on-premise, and the report tools want Odoo 18+, while the generic query tools still run on older instances.

What you get

business_pulse is the morning briefing in a single call: yesterday's confirmed revenue and new leads, overdue customer invoices, tasks past their deadline and who is off today, with each section skipping itself when the app is not installed
pipeline_review composes open opportunities into totals, probability-weighted revenue, stalled deals, close-date buckets, per-stage and per-salesperson breakdowns and a recent win rate; sales_snapshot compares this period with the last for revenue and order deltas, top customers, top products and stale quotations
receivables_health buckets open invoices and vendor bills as not_due, 1-30, 31-60, 61-90 and 90+, with the share of receivables overdue and the top overdue customers
inventory_risk separates shortages — storable products with negative forecast — from dead stock valued at standard price; procurement_watch covers late receipts, stale RFQs and open spend per vendor; production_health finds manufacturing orders that should have started and ones running longer than expected
Project delivery: project_status_report grades each project off_track, at_risk or on_track from its milestones, team_workload shows who is over- and under-loaded with overdue, due-soon and no-deadline tallies, and standup_digest returns a plain-text digest bucketed OVERDUE, TODAY, UPCOMING and NO DEADLINE
project_profitability joins timesheet hours to analytic cost, revenue and budget burn; project_budget compares planned against actual line by line; project_dashboard returns everything a project detail page needs in one call, and portfolio_health one row per project joined server-side
absence_overview composes approved leave, pending approvals and per-department headcount into coverage-risk flags for the days ahead
The generic layer is there when a report does not fit: odoo_version, list_models, get_model_fields, search_read, search_count, read_records, aggregate_records for server-side grouping, and read_attachment
Writes exist and are gated: create_record, update_records and delete_records, plus create_lead, create_contact, create_task and confirm_sale_order, each returning a dry-run preview unless confirm=true
Every money-reporting tool takes an optional company filter and flags mixed-currency totals instead of silently summing them, and the verdict cut-offs — stalled, overdue and growth percentages — are parameters you can calibrate

Requirements

Runs over stdio as uvx odoo-pulse and needs ODOO_URL, ODOO_DB, ODOO_USERNAME and ODOO_API_KEY; generate the key in Odoo under Settings → Users → Account Security → New API Key. ODOO_READ_ONLY defaults to true, and a write needs four independent things to line up: ODOO_READ_ONLY=false, the model listed in ODOO_WRITABLE_MODELS, ODOO_ALLOW_DELETE=true additionally for deletes, and confirm=true on the call. System models are never writable. Every report tool takes timezone_offset, default 7, because Odoo stores datetimes in UTC. Further model-aware query tools across CRM, Sales, Inventory, Accounting, HR, Project, Manufacturing and PoS are opt-in through ODOO_TOOL_GROUPS. MIT.

Setup effort

One command plus a key — uvx odoo-pulse, then supply credentials

See installation options

USE CASES

Starting the day knowing what needs attention

One briefing covering yesterday's revenue and new leads, overdue invoices, late tasks and today's absences — with the sections for apps you do not run left out.

business_pulseabsence_overview

Working out whether the quarter is on track

Revenue against the previous period with top customers and products, alongside the pipeline's weighted value, stalled deals and recent win rate.

sales_snapshotpipeline_review

Chasing the money that has not arrived

Aging buckets across open invoices and vendor bills, the share of receivables already overdue, and the customers behind most of it.

receivables_healthsearch_read

Finding the project that is quietly slipping

Portfolio health one row per project, the milestone-driven verdict behind each, and the hours, cost and budget burn for whichever one looks worst.

portfolio_healthproject_status_reportproject_profitability

Balancing a team that is unevenly loaded

Per-assignee open work with overdue, due-soon, high-priority and no-deadline counts, plus the unassigned tasks nobody has picked up, and a stand-up digest to read out.

team_workloadstandup_digest

Spotting stock and supply problems before they bite

Products forecast to go negative and on-hand stock that has not moved, next to late receipts and purchase quotations that have gone stale.

inventory_riskprocurement_watchproduction_health

31 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`absence_overview`

Report who is off and where coverage is thin, in one call.

Composes approved hr.leave records overlapping the next days days, pending approval requests, and per-department headcount into an absence calendar, coverage-risk flags (share of a department off at some point in the window >= coverage_threshold), and a verdict.

Args: days: Look-ahead window in days (default 14). coverage_threshold: Department share off in the window that counts as a coverage risk (default 0.3). timezone_offset: UTC offset for "today" (default 7 = Asia/Ho_Chi_Minh).

INSTALLATION

Connect your client

Server setup

TERMINAL

uvx odoo-pulse

MCP Clients

Claude Code

CLAUDE CODE · TERMINAL

claude mcp add odoo-pulse \
  --env ODOO_URL=https://acme.odoo.com \
  --env ODOO_DB=acme \
  --env ODOO_USERNAME=<YOUR_ODOO_USERNAME> \
  --env ODOO_API_KEY=<YOUR_ODOO_API_KEY> \
  --env ODOO_READ_ONLY=true \
  -- uvx odoo-pulse

Claude Code — plugin

CLAUDE CODE — PLUGIN · IN CLIENT

/plugin marketplace add minhhq-a1/odoo-pulse
/plugin install odoo-pulse@odoo-pulse

Claude Desktop, Cursor

JSON

{
  "mcpServers": {
    "odoo-pulse": {
      "command": "uvx",
      "args": [
        "odoo-pulse"
      ],
      "env": {
        "ODOO_URL": "https://acme.odoo.com",
        "ODOO_DB": "acme",
        "ODOO_USERNAME": "<YOUR_ODOO_USERNAME>",
        "ODOO_API_KEY": "<YOUR_ODOO_API_KEY>",
        "ODOO_READ_ONLY": "true"
      }
    }
  }
}

VS Code

VS CODE · JSON

{
  "servers": {
    "odoo-pulse": {
      "command": "uvx",
      "args": [
        "odoo-pulse"
      ],
      "env": {
        "ODOO_URL": "https://acme.odoo.com",
        "ODOO_DB": "acme",
        "ODOO_USERNAME": "<YOUR_ODOO_USERNAME>",
        "ODOO_API_KEY": "<YOUR_ODOO_API_KEY>",
        "ODOO_READ_ONLY": "true"
      }
    }
  }
}

Odoo Pulse

One call per question, and the answer arrives with a verdict instead of rows to interpret.

What it is

What you get

Requirements

Setup effort

Starting the day knowing what needs attention

Working out whether the quarter is on track

Chasing the money that has not arrived

Finding the project that is quietly slipping

Balancing a team that is unevenly loaded

Spotting stock and supply problems before they bite

31 tools

absence_overview

aggregate_records

business_pulse

confirm_sale_order

create_contact

create_lead

create_record

create_task

delete_records

get_model_fields

inventory_risk

list_models

odoo_version

pipeline_review

portfolio_health

procurement_watch

production_health

project_budget

project_dashboard

project_profitability

project_status_report

project_subtask_hours

read_attachment

read_records

receivables_health

sales_snapshot

search_count

search_read

standup_digest

team_workload

update_records

What to know first

Tools you get

Requires

Connect your client

Server setup

MCP Clients

Claude Code

Claude Code — plugin

Claude Desktop, Cursor

VS Code

Same category

Odoo MCP Server by ivnvxd

Odoo MCP Server by alberto-re

Odoo MCP Server

Kingdee K3Cloud ERP

`absence_overview`

`aggregate_records`

`business_pulse`

`confirm_sale_order`

`create_contact`

`create_lead`

`create_record`

`create_task`

`delete_records`

`get_model_fields`

`inventory_risk`

`list_models`

`odoo_version`

`pipeline_review`

`portfolio_health`

`procurement_watch`

`production_health`

`project_budget`

`project_dashboard`

`project_profitability`

`project_status_report`

`project_subtask_hours`

`read_attachment`

`read_records`

`receivables_health`

`sales_snapshot`

`search_count`

`search_read`

`standup_digest`

`team_workload`

`update_records`