ALVRT

• Find Relevant Odoo Skill — Return the Odoo skill most relevant to a question, with its content. Prefer this tool — it picks the right skill by keyword match and returns its full markdown guide in one call. Use when you're about to execute a domain workflow (selling, buying, inventory, etc.) and want the reference material first. If `find_skill` returns nothing, fall back to `get_skill(name)` with a guessed name. Args: question: The user's question or t
• Get Odoo Skill — Read an Odoo workflow skill by name. Returns the full SKILL.md content — load this as context before executing a multi-step workflow in that domain. Args: name: Skill name as returned by `find_skill` (e.g. "selling"). Returns: The markdown body of the SKILL.md file. Empty string if the skill name is not known.
• Search Records — Search for records in an Odoo model. Args: model: The Odoo model name (e.g., 'res.partner') domain: Odoo domain filter - can be: - A list: [['is_company', '=', True]] - A JSON string: "[['is_company', '=', true]]" - None: returns all records (default) fields: Field selection options - can be: - None (default): Returns smart selection of common fields
• Get Record — Get a specific record by ID with smart field selection. This tool supports selective field retrieval to optimize performance and response size. By default, returns a smart selection of commonly-used fields based on the model's field metadata. Args: model: The Odoo model name (e.g., 'res.partner') record_id: The record ID fields: Field selection options: - None (default): Returns smart select
• List Models — List all models enabled for MCP access with their allowed operations. Args: connection: Optional. Target a specific Odoo connection by the id from server_info's `connections` list. Hosted multi-tenant only; ignored when self-hosting a single connection. Returns: List of models with their technical names, display names, and allowed operations (read, write, create, unlink).
• List Resource Templates — List available resource URI templates. Since MCP resources with parameters are registered as templates, they don't appear in the standard resource list. This tool provides information about available resource patterns you can use. Returns: Resource template definitions with examples and enabled models.
• Server Info — Get MCP server version and connection status. Returns: Server version, git commit, API version, and Odoo connection status.
• Create Record — Create a new record in an Odoo model. Args: model: The Odoo model name (e.g., 'res.partner') values: Field values for the new record connection: Optional. Target a specific Odoo connection by the id from server_info's `connections` list. Hosted multi-tenant only; ignored when self-hosting a single connection. Returns: Created record details with ID, URL, and confirmat
• Update Record — Update an existing record. Args: model: The Odoo model name (e.g., 'res.partner') record_id: The record ID to update values: Field values to update connection: Optional. Target a specific Odoo connection by the id from server_info's `connections` list. Hosted multi-tenant only; ignored when self-hosting a single connection. Returns: Updated record deta
• Delete Record — Delete a record. Args: model: The Odoo model name (e.g., 'res.partner') record_id: The record ID to delete connection: Optional. Target a specific Odoo connection by the id from server_info's `connections` list. Hosted multi-tenant only; ignored when self-hosting a single connection. Returns: Deletion confirmation with the deleted record's name and ID.
• Create Records (Bulk) — Create multiple records in a single operation (max 1000). Much faster than calling create_record repeatedly. Use this when importing data, creating batches of records, or any scenario with more than a few records. Args: model: The Odoo model name (e.g., 'res.partner') vals_list: List of dicts, each containing field values for one record. Example: [{"name": "Alice"}, {"name": "Bob"}]
• Update Records (Bulk) — Update multiple records with the same values in a single operation (max 1000). Use this for mass updates like tagging contacts, changing statuses, or applying the same change to many records at once. Args: model: The Odoo model name (e.g., 'res.partner') record_ids: List of record IDs to update values: Field values to apply to all specified records connection: Optional. Target a specific Odoo co
• Delete Records (Bulk) — Delete multiple records in a single operation (max 1000). Args: model: The Odoo model name (e.g., 'res.partner') record_ids: List of record IDs to delete connection: Optional. Target a specific Odoo connection by the id from server_info's `connections` list. Hosted multi-tenant only; ignored when self-hosting a single connection. Returns: List of deleted record IDs wi
• Import Records (Upsert with External IDs) — Import records using Odoo's native load() method with external ID support. This is the recommended way to import data. It supports idempotent upsert: if a record with the given external ID already exists, it will be updated instead of duplicated. Running the same import twice produces the same result. Uses the same mechanism as Odoo's built-in CSV import. Args: model: The Odoo model name (e.g., 'res.partne
• Set Binary Field (Upload Image/File to a Record Field) — Upload bytes into a Binary or Image field on an existing record. Use this for: avatar/logo on res.partner, product images on product.template, company logo, attachment bytes on custom Binary fields. IMPORTANT — bytes must NOT pass through the model. `source` must be an http(s) URL; the server fetches the bytes from that URL directly and streams them to Odoo. Do NOT base64-encode a local file and paste it into this call — L
• Post Chatter Message (Send Message / Log Note) — Post a message in the chatter of any thread-enabled Odoo record. Equivalent to clicking 'Send Message' (subtype=mt_comment, default) or 'Log Note' (subtype=mt_note) in the Odoo UI. Sends synchronously within the same request — no waiting on the email queue cron. Args: model: Odoo model with chatter enabled — 'res.partner', 'crm.lead', 'sale.order', 'account.move', 'helpdesk.ticket', etc. record_
• Execute Odoo Method (call a standard Odoo action) — Call a public method on an Odoo model or recordset. This is the standard Odoo way to trigger an action that is not plain create/read/update/delete: confirming a sales order, posting an invoice, marking a CRM lead lost, validating a delivery, and so on. It runs Odoo's own method unchanged. Some methods return a wizard instead of completing (e.g. validating a delivery that is short on stock asks whether to create a backorder
• Register Payment (form) — Register a payment on posted invoices or bills, through a form. Runs Odoo's own register-payment wizard (`account.move. action_register_payment`). Prefer this over `execute_method` for payments: in a client that supports MCP Apps the user gets a form with journal, amount, date and memo right in the chat and submits it there; the result comes back to you as usual. Elsewhere it behaves exactly like `execute_method`: call with

Schemas and invoke metadata: Directory API