Odoo
Open-source ERP and CRM platform for business management, including sales, accounting, inventory, and project management
Verdict
Common use cases
- Extract invoice totals from vendor PDFs
- Parse expense receipts during reimbursement reviews
- Screen candidate resumes for contact details
- Reconcile bank statements with transaction lines
- Audit supplier invoices before payment approval
Integration
- Vendor
- Odoo
- Category
- crm
- Auth
- API_KEY
- Tools
- 10
- Composio slug
odoo
Tools
- Get Applicant Parsing Result
Tool to retrieve parsing results for a previously submitted resume/applicant document. Use when you need to check the status and get extracted fields (name, email, phone, mobile) from a resume that was previously submitted for parsing.
- Get Bank Statement Result
Tool to retrieve parsing results for a previously submitted bank statement. Returns extracted fields including balance_start, balance_end, date, and bank_statement_lines. Use when you need to check the status and get extracted data from a b
- Get Expense Extraction Result
Retrieve parsing results for a previously submitted expense document. Returns extracted fields including description, country, date, total, and currency. Use this after submitting an expense document to get the OCR/extraction results.
- Get Invoice Parsing Result
Tool to retrieve parsing results for a previously submitted invoice from Odoo Extract API. Use when you need to check the status and get extracted data from an invoice. Poll this endpoint until the status field is 'success' - processing may
- List Databases
Tool to list all available Odoo databases on the server. Use when you need to see which databases are available on the Odoo instance.
- Odoo JSON-RPC Call
JSON-RPC endpoint for Odoo external API calls. Provides the same functionality as XML-RPC but with JSON encoding. DEPRECATED in v19.0 and scheduled for removal in v20.0 (Fall 2026). Use JSON-2 API at POST /json/2/{model}/{method} instead.
- Parse Applicant Resume
Tool to submit a resume/CV document for OCR parsing and data extraction via Odoo Extract API. Extracts name, email, phone, and mobile from applicant resumes. Returns a document_token to poll for results. Cost: 1 IAP credit per successful pa
- Parse Bank Statement Document
Tool to submit a bank statement document for OCR parsing and data extraction via Odoo Extract API. Extracts balance_start, balance_end, date, and bank_statement_lines. Returns a document_token to poll for results. Cost: 1 IAP credit per suc
- Parse Expense Document
Tool to submit an expense document for OCR parsing and data extraction. Extracts description, country, date, total, and currency from expense receipts. Returns a document_token to poll for results. Use when you need to process expense docum
- Parse Invoice Document
Tool to submit an invoice document for OCR parsing and data extraction via Odoo Extract API. Uses AI-based algorithms to extract fields like total, due date, invoice lines, VAT numbers, IBAN, supplier, client, and currency. Returns a docume
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations section. 2. Select 'Add Integration' and choose Odoo from the list. 3. You'll be prompted to enter your Odoo instance URL (e.g., yourcompany.odoo.com) and an API key — generate this key in Odoo under Settings > Users & Companies > API Keys, ensuring it has permissions for the Extract API and database access. 4. Paste the API key into Switchy and click 'Connect'. 5. Switchy will verify the connection by listing available databases on your Odoo instance. 6. To test, create a Space and type '@Odoo list all databases' — you should see your Odoo databases returned in the response. 7. To parse a document, upload an invoice or receipt to the Space, then prompt '@Odoo parse this invoice' — the MCP will submit it and poll for extracted fields like vendor name, total, and date.
What teammates see: by default, memories from Odoo are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Parse Uploaded Invoice
@Odoo parse the invoice I just uploaded and return the vendor name, invoice date, total amount, and all line items as structured data.Open in a Space →
Extract Expense Receipt Data
@Odoo parse this expense receipt and give me the merchant description, transaction date, total amount, and currency code.Open in a Space →
Screen Candidate Resume
@Odoo parse the resume attached here and return the candidate's full name, email address, phone number, and mobile number.Open in a Space →
Reconcile Bank Statement
@Odoo parse this bank statement and return the opening balance, closing balance, statement date, and all transaction lines with amounts.Open in a Space →
List Available Databases
@Odoo list all databases available on this Odoo instance so I can confirm which environments I have access to.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Odoo list all databases available on our instance and show which one is currently active for our CRM operations.
Based on the Odoo instance query, three databases are available: 'production_crm' (active), 'staging_crm', and 'dev_sandbox'. The production_crm database is currently handling live customer data and contains 1,247 active contacts, 89 open opportunities, and 34 leads from this quarter. The staging environment mirrors production with a 2-day lag for testing workflow changes before deployment.
This example demonstrates the List Databases tool, useful for multi-environment Odoo setups. Requires API key with database enumeration permissions. Note that database names and statistics shown are illustrative—actual results depend on your Odoo configuration and access level.
@Odoo parse this applicant resume PDF and extract contact details so we can add them to our recruiting pipeline.
Resume submitted for OCR parsing. Document token: doc_a7f3k9m2. The extraction is processing and should complete within 30-60 seconds. Once ready, the parsed fields will include: candidate name, email address, phone number, and mobile number. You can poll for results using the document token, or I can check back automatically and update you when extraction completes.
Showcases the Parse Applicant Resume tool for HR workflows. This is a two-step process: submit the document, then poll for results using the returned token. Extraction time varies by document complexity. Requires Odoo Extract API access, which may have usage limits depending on your subscription tier.
@Odoo retrieve the parsing results for invoice token inv_x4h8n1p9 and summarize the key financial details for our accounting review.
Invoice parsing complete. Extracted details: Vendor is 'Acme Supplies Ltd', invoice number INV-2024-0847, dated January 15, 2024. Total amount: $3,247.50 USD. Line items include office furniture ($2,100), shipping ($147.50), and installation services ($1,000). Payment terms: Net 30. The document confidence score is 94%, indicating high OCR accuracy. Two fields flagged for manual review: the vendor tax ID appears partially obscured, and one line item description may need clarification.
Demonstrates the Get Invoice Parsing Result tool paired with AI synthesis to transform raw OCR data into an actionable summary. Useful after submitting invoices for automated data entry. Confidence scores help identify fields needing human verification. Polling may be required if the document is still processing when first queried.
Use-case deep-dives
When Odoo wins for high-volume resume screening
A 6-person recruiting team processing 200+ resumes a week uses Odoo's Parse Applicant Resume tool to extract contact fields (name, email, phone) and feed them straight into their ATS. The MCP handles the OCR polling loop, so the team doesn't manually copy-paste from PDFs. This works when your hiring process already lives in Odoo or you're willing to build a bridge to your existing CRM. If you're on Greenhouse or Lever and don't plan to migrate, the integration tax is too high—stick with native resume parsers. For teams running Odoo HR end-to-end, this MCP cuts intake time by 60% and keeps candidate data clean from day one.
Odoo MCP shines for distributed team expense tracking
A 12-person remote consulting firm uses Odoo's Get Expense Extraction Result tool to pull receipt data (vendor, date, total, currency) from photos submitted by contractors across three countries. The finance lead runs a weekly Switchy thread that batches all pending expenses, flags currency mismatches, and drafts approval emails. This scenario wins when your team already uses Odoo Accounting and you need structured data from unstructured receipts. If you're under 20 expenses a month, manual entry is faster than the API setup. Above that threshold, the MCP pays for itself by eliminating double-entry and catching OCR errors before they hit the books. Teams on QuickBooks or Xero should look elsewhere.
When invoice parsing beats manual keying for small shops
A 3-person e-commerce fulfillment shop receives 40-60 supplier invoices monthly as PDFs. They use Odoo's Get Invoice Parsing Result tool to extract line items, totals, and due dates, then push the structured data into their accounting workflow. The MCP polls the Extract API until parsing completes, so the bookkeeper doesn't babysit uploads. This makes sense when invoice volume exceeds 30/month and your chart of accounts lives in Odoo. Below that, the API_KEY setup and polling overhead aren't worth it—just type the invoices. For teams already on Odoo Invoicing, this MCP turns a 90-minute weekly task into a 15-minute review, but only if your suppliers send machine-readable PDFs (scanned images still fail 20% of the time).
Frequently asked
What does the Odoo MCP do in Switchy?
It connects your Odoo instance to Switchy's AI workspace, letting agents read CRM records, parse invoices and resumes via Odoo's Extract API, and call Odoo's JSON-RPC methods. You can automate data entry, extract structured fields from uploaded documents, and query your Odoo databases without switching contexts. The MCP handles authentication and exposes 10 tools covering document parsing and database operations.
Do I need admin access to connect Odoo?
You need an API key with permissions matching the operations you want to run. For document parsing tools (invoices, resumes, bank statements), your key must access Odoo's Extract API endpoints. For database queries and JSON-RPC calls, you need read or write permissions on the relevant Odoo models. Check with your Odoo admin which roles grant API key creation rights in your instance.
Can the Odoo MCP create or update CRM records?
Yes, through the JSON-RPC call tool. You can create leads, update contact details, or modify opportunity stages by calling Odoo's external API methods. The MCP wraps Odoo's standard API, so any operation your API key permits—create, read, update, delete—works in Switchy. Document parsing tools are read-only; they extract data but don't write back to Odoo automatically.
How is this different from using Odoo's web interface directly?
Switchy agents can pull Odoo data into conversations, cross-reference it with other tools, and automate multi-step workflows without you logging into Odoo. For example, an agent can parse an invoice, check the vendor in your CRM, and draft a payment email—all in one thread. The trade-off: you lose Odoo's visual dashboards and must describe what you want in natural language.
Who on the team should connect the Odoo integration?
Whoever holds an Odoo API key with the right permissions. Typically your CRM admin or a finance lead who already manages Odoo integrations. Once connected in Switchy, any team member with access to the shared workspace can invoke Odoo tools through agents. The API key's permissions define what operations are possible, so choose someone who understands your Odoo security model.