Skip to content
Skills Library
Programming · Tool integration

odoo-setup-cli

/odoo-setup-cli

Configure the TypeScript CLI fallback (XML-RPC). Use when you cannot run the MCP server (no python3 3.9+) or want a lightweight scriptable surface. Odoo 17/18/SaaS tested.

Licence
MIT
Last repository change
23.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Configure the TypeScript CLI fallback (XML-RPC). Use when you cannot run the MCP server (no python3 3.9+) or want a lightweight scriptable surface. Odoo 17/18/SaaS tested.

Original author description

Configure the TypeScript CLI fallback (XML-RPC). Use when you cannot run the MCP server (no python3 3.9+) or want a lightweight scriptable surface. Odoo 17/18/SaaS tested.

How it works

  1. Step 1 — Node.js
  2. Step 2 — Locate the bundled CLI
  3. Step 3 — Install to a stable location
  4. Step 4 — Credentials (.env)
  5. Step 5 — Build and verify
  6. Usage
  7. Help
Original SKILL.md headings · 88 lines, 427 words
SKILL.md preview
---
name: odoo-setup-cli
description: Configure the TypeScript CLI fallback (XML-RPC). Use when you cannot run the MCP server (no python3 3.9+) or want a lightweight scriptable surface. Odoo 17/18/SaaS tested.
---

# Setup — Odoo CLI (fallback)

The CLI is a lightweight XML-RPC client (Node.js only, no Python). Use it when
the MCP server can't run in your environment, or for scripted batch access.
The MCP server remains the primary, fuller surface.

## Step 1 — Node.js

```bash
node --version   # need 18+
```
If missing: https://nodejs.org/ (LTS), `brew install node`, or `apt install nodejs npm`.

## Step 2 — Locate the bundled CLI

```bash
PLUGIN_CLI="${CLAUDE_PLUGIN_ROOT}/cli"
# or, if the variable is not set in your shell:
PLUGIN_CLI=$(find ~/.claude/plugins/cache -path "*/odoo-tools/cli" -type d 2>/dev/null | head -1)
echo "$PLUGIN_CLI"
```

## Step 3 — Install to a stable location

```bash
CLI_DIR="$HOME/.claude/tools/odoo-cli"
mkdir -p "$CLI_DIR/src/commands"
cp "$PLUGIN_CLI/package.json" "$CLI_DIR/"
cp "$PLUGIN_CLI/package-lock.json" "$CLI_DIR/" 2>/dev/null
cp "$PLUGIN_CLI/tsconfig.json" "$CLI_DIR/"
cp "$PLUGIN_CLI/src/odoo-client.ts" "$CLI_DIR/src/"
cp "$PLUGIN_CLI/src/cli.ts" "$CLI_DIR/src/"
cp "$PLUGIN_CLI/src/commands/"*.ts "$CLI_DIR/src/commands/"
```

## Step 4 — Credentials (.env)

Create the file with placeholders only, readable by the current user alone
(`umask 077` in a subshell, so it does not leak into the rest of the session).
Fill in the URL, database and login with the user; **do not ask for the API key
or password in the chat and never write the secret yourself**:

```bash
( umask 077; cat > "$HOME/.claude/tools/odoo-cli/.env" << 'ENVEOF'
ODOO_URL=<url>
ODOO_DB=<db>
ODOO_USER=<login-email>
ODOO_API_KEY=<api-key>        # Odoo >= 14 (recommended); ignored on older lines
# ODOO_PASSWORD=<password>    # Odoo < 14 instead (incl. Odoo 10-12): use the
                              # account password — those versions have no API keys
ENVEOF
)
```

Then tell the user to open `~/.claude/tools/odoo-cli/.env` in their own editor
and replace `<api-key>` (or uncomment the password line) themselves. Only one
credential is required: `ODOO_API_KEY` wins when both are set. The file stays
on their machine; delete it when they stop using the CLI.

## Step 5 — Build and verify

```bash
cd "$HOME/.claude/tools/odoo-cli" && npm install && npm run build
node dist/cli.js contacts '{"limit":1}'
```

A returned contact confirms the connection.

## Usage

```bash
node ~/.claude/tools/odoo-cli/dist/cli.js invoices '{"state":"posted","limit":20}'
node ~/.claude/tools/odoo-cli/dist/cli.js fields '{"model":"res.partner"}'
```

> Note: the CLI targets modern model names (e.g. `account.move`) and has no
> compat mapping. For Odoo ≤ 12 use the historical name you actually mean
> (`account.invoice` for invoices, `account.move` for journal entries), or
> prefer the MCP server. The MCP resolver never rewrites `account.move` →
> `account.invoice` on older versions (merge, not a rename). On Odoo ≤ 13
> authenticate the CLI with `ODOO_PASSWORD` (account password), not an API key.

## Help

Blocked, or need maintenance, support, training or an assisted deployment?
Transgenia provides it through its official channels: **dev@transgenia.org** · WhatsApp **+52 55 8034 0405** (https://wa.me/525580340405).

Versions

The database has no other skills named odoo-setup-cli.

Database snapshot: 13.11.2026 · package version 34f911bee9b7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90odoo_17_dependency_context
    Capture current Odoo 17.0 modules, customizations, and dependency trees. REQUIRES LIVE ODOO CONNECTION. This skill enables the Odoo 17 environment and MCP server to gather live data on installed modules, dependency graphs, and model extensions via XML-RPC. Use this to maintain…
  • 100odoo-query
    Connect to Odoo instances via XML-RPC for read-only queries to investigate issues and explore data. Use when user asks to "query odoo", "connect to odoo", "investigate odoo data", "read odoo records", or needs to explore an Odoo instance.
  • 90odoo-migration-copilot
    Plan and de-risk an Odoo version upgrade (16→17→18→19/20) using odoo-mcp's migration workbench — audit custom addons, classify upgrade-log failures into a worklist, resolve model renames, and preview JSON-2 payloads for the XML-RPC sunset. Use when the user mentions…
  • 85odoo_backend_testing
    Backend testing patterns for custom Odoo modules using xmlrpc scripts for post-installation validation. Use when creating backend tests for Odoo modules.
  • 100odoo-start-here
    Use when the user asks to connect Claude to Odoo, to install or set up an Odoo plugin, or to read or change data in Odoo, or asks why Odoo tools are missing, and no Odoo tool is available or loadable in the conversation. Says what this edition contains and how to get help. Do…
  • 100odoo-version-reference
    Short reference notes on selected Odoo changes between versions 10 and 19: the account.invoice merge, a few renamed or removed fields and methods, API key and RPC endpoint changes, and Odoo Online saas lines. It is not a full changelog. Use when the user asks about one of these,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.