Skip to main content

odoo-pulse

CI PyPI License: MIT

An AI business analyst for your Odoo ERP. Ask one question, get one answer — numbers, highlights, risks, and a verdict (on-track / at-risk / off-track) — over the Model Context Protocol. CRUD bridges to Odoo already exist; this is the analytics layer that sits on top.

business_pulse — a one-call company briefing

The analyst tools

Each tool answers a whole management question in a single call, returning a structured report with a verdict — not a raw dump you have to interpret.

Tool Answers
business_pulse ⭐ The morning briefing: yesterday's sales, new leads, overdue invoices, late tasks, who's off — with a company-wide verdict
pipeline_review CRM funnel by stage, stalled deals, weighted revenue, recent win rate
sales_snapshot Revenue this period vs last (Δ%), top customers/products, stale quotations
receivables_health AR/AP aging buckets, % overdue, top debtors
inventory_risk Shortages (negative forecast) and dead stock
absence_overview Who's off this week, pending approvals, thin-coverage departments
procurement_watch Purchasing: late receipts, stale RFQs, open spend per vendor
production_health Manufacturing: orders behind their planned start, stuck WIP
project_profitability Projects: hours logged vs allocated, cost/revenue/margin, budget burn verdict
project_budget Budget vs actual per project, line by line — over-plan lines and spend the budget doesn't capture
team_workload · project_status_report · standup_digest Project delivery: overloaded members, at-risk projects, and a daily stand-up digest

Every money-reporting tool takes an optional company= filter and flags mixed-currency totals instead of silently summing them; verdict cut-offs (stalled %, overdue %, growth %) are parameters, so you can calibrate them to your business.

Timezone semantics

All report tools take timezone_offset (default 7). Odoo stores datetime fields in UTC; the tools shift them by timezone_offset hours before bucketing by calendar day, and day windows in domains are expressed as UTC datetime boundaries. Date-only fields (e.g. project.milestone.deadline, invoice_date_due, project.task.date_deadline) are compared as-is.

Version-dependent fields

find_partner searches mobile only on instances that still have it (removed in Odoo 19), and list_timesheets reports an actionable error when hr_timesheet is not installed.

Under the hood it's the standard Odoo XML-RPC external API — nothing to install inside Odoo, works on Odoo Online, Odoo.sh, and on-premise. Requires Odoo 18+: the generic tools (search_read, read_records, …) still run on older versions, but the report tools are not guaranteed there.

Try the playground

No Odoo account? Boot a demo Odoo pre-seeded with a story to tell (a stalled deal, a 90-day-overdue invoice, a stock shortage, someone off today):

docker compose -f deploy/playground/compose.yml up -d

First boot pulls ~4 GB of images (Odoo + Postgres) and seeds the demo data — allow 5-10 minutes depending on your connection. Then point Claude at it and ask it to run business_pulse. Full walkthrough: docs/guides/playground.md.

Install & connect

Add it to Claude Code (no install step — uvx fetches it):

claude mcp add odoo-pulse \
  --env ODOO_URL=https://acme.odoo.com \
  --env ODOO_DB=acme \
  --env ODOO_USERNAME=you@example.com \
  --env ODOO_API_KEY=your-api-key \
  --env ODOO_READ_ONLY=true \
  -- uvx odoo-pulse

Generate the API key in Odoo under Settings → Users → (your user) → Account Security → New API Key. Config for Claude Desktop and Cursor, plus pip and Docker alternatives: docs/guides/install.md. If a key may have been exposed, see If an API key may have been exposed.

Or one-click:

Install in Cursor Install in VS Code

Read-only by default, safe writes when you want them

The server is read-only out of the box (ODOO_READ_ONLY=true). Writes require four independent controls to line up: ODOO_READ_ONLY=false, ODOO_WRITABLE_MODELS (a comma-separated model allow-list), ODOO_ALLOW_DELETE=true additionally for deletes, and a per-call confirm=true — every write tool returns a dry-run preview without it. System models are never writable. Details: docs/reference/tools.md#write-operations.

More tools

Beyond the analyst reports, there are ~60 model-aware query tools spanning CRM, Sales, Inventory, Accounting, HR, Project, Manufacturing, PoS, and Enterprise apps — opt in via ODOO_TOOL_GROUPS. Full catalogue and configuration: docs/reference/tools.md.

Testing

The suite mocks the XML-RPC layer, so no real Odoo or network is needed:

pip install -e ".[dev]"
pytest

For a live check against a real Odoo (read-only), see docs/reference/tools.md#live-smoke-test-against-a-real-odoo.

License

MIT

Metadata

Release files for odoo-pulse 1.9.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for odoo-pulse 1.9.1
File Size Uploaded
odoo_pulse-1.9.1.tar.gz 342.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for odoo-pulse 1.9.1
File Interpreter ABI Platform
odoo_pulse-1.9.1-py3-none-any.whl Python 3 none any Details

Total release size: 455.8 kB

Release files / odoo_pulse-1.9.1.tar.gz

Download URL odoo_pulse-1.9.1.tar.gz
Size 342.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ae45691de37c84ad47690b3ac1f840a013b89c42307950d57163dbedb4a0784d
BLAKE2b-256 checksum
How to use checksums
fd3afc19db1a744762b9cd23e0dbd5de2b3133e035020eded470dde7d4f3435f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.

Transparency log

Release files / odoo_pulse-1.9.1-py3-none-any.whl

Download URL odoo_pulse-1.9.1-py3-none-any.whl
Size 113.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
22404a0964a06d72e63d41a9e3ab9c9ebd9f992cbd36f5b7d683094a516d4f7e
BLAKE2b-256 checksum
How to use checksums
514bd534d73f71a134402e59bb968e765f93ff9ad5574451dc0c7dc6f94003fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page