Odoo Helpdesk MCP. Log tickets and manage support workflow in chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Odoo Helpdesk connects your AI client directly to Odoo ERP's ticketing system. You can manage, track, and update support tickets—from logging a new issue with `odoo_create_ticket` to checking SLA deadlines using `odoo_list_sla_policies`.
It keeps all customer service data in one place without forcing you to switch tabs.
What your AI agents can do
Odoo create ticket
Logs a new helpdesk ticket in Odoo. You must provide the subject, customer email, team ID, description, and priority level.
Odoo list helpdesk teams
Lists all support teams in Odoo Helpdesk, showing their name, how many members they have, and if SLA tracking is active.
Odoo list sla policies
Retrieves configured Service Level Agreement (SLA) policies for the helpdesk, detailing target response times and resolution deadlines by team and stage.
You log a support request by providing the subject, customer email, assigned team, and desired priority via odoo_create_ticket.
The system retrieves all configured helpdesk teams, including their member count and if they track SLAs, using odoo_list_helpdesk_teams.
You view service level agreements (SLAs) for the support desk, seeing target response times and resolution deadlines per team via odoo_list_sla_policies.
The agent finds existing issues or requests by searching keywords in ticket subjects using odoo_search_tickets.
You modify a ticket's properties—like changing its priority, renaming it, or reassigning the agent—using odoo_update_ticket.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Odoo Helpdesk MCP Server: 7 Tools for Support Workflow
Use these tools to create new tickets, search existing ones, monitor SLA policies, list teams, and manage customer data within Odoo.
019d75e2odoo create ticket
Logs a new helpdesk ticket in Odoo. You must provide the subject, customer email, team ID, description, and priority level.
019d75e2odoo list helpdesk teams
Lists all support teams in Odoo Helpdesk, showing their name, how many members they have, and if SLA tracking is active.
019d75e2odoo list sla policies
Retrieves configured Service Level Agreement (SLA) policies for the helpdesk, detailing target response times and resolution deadlines by team and stage.
019d75e2odoo list ticket types
Lists available classification labels used in Odoo to categorize tickets, such as 'Bug' or 'Feature Request'.
019d75e2odoo list tickets
Returns a list of all helpdesk tickets in Odoo. You see the customer, team, current stage (kanban), priority, and SLA status.
019d75e2odoo search tickets
Searches for specific helpdesk tickets by subject or keyword to find a particular issue or request quickly.
019d75e2odoo update ticket
Modifies an existing ticket in Odoo. You can change the priority, rename it, reassign ownership, or update other fields.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Odoo Helpdesk, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Odoo Helpdesk connects your AI client right into Odoo ERP's ticketing system. You can manage every support ticket—logging new issues, tracking assignments, and updating details—all without leaving your chat window. You get a full view of your customer service data in one place.
To start a case, use odoo_create_ticket. It lets you log a brand-new helpdesk issue by providing the subject, the customer's email, the assigned team ID, a detailed description, and the priority level. You can check what support teams are available in Odoo Helpdesk using odoo_list_helpdesk_teams; this tool shows you each team’s name, how many members they have, and whether or not they track SLAs.
You need to know if you're meeting deadlines? Run odoo_list_sla_policies. This pulls up all the Service Level Agreement (SLA) policies set for your support desk, giving you precise details on target response times and resolution deadlines broken down by team and ticket stage. Want to see what kinds of issues people are reporting? You can call odoo_list_ticket_types to get a list of every classification label Odoo uses—like 'Bug' or 'Feature Request'—so you know how to categorize tickets properly.
When you need an overview, start by listing all open cases with odoo_list_tickets. This gives you a roster showing the customer associated with the ticket, which team owns it, its current stage in the process, its priority level, and its SLA status. If you're hunting for something specific, don't scroll through everything; use odoo_search_tickets to quickly find existing issues or requests by searching keywords in the ticket subject.
Need to make changes? You can modify an existing ticket’s details using odoo_update_ticket. This lets you change its priority, rename it for clarity, reassign ownership to a different agent, or update any other field on file. If you want to see all the support teams configured in Odoo Helpdesk, run odoo_list_helpdesk_teams again; this shows you the name of each team and if they're tracking SLAs.
You can also check what’s available for categorization by listing ticket types with odoo_list_ticket_types. Finally, to get a full list of all support tickets in Odoo Helpdesk at a glance, use odoo_list_tickets.
How Odoo Helpdesk MCP Works
- 1 First, ask your AI client to list current support teams using
odoo_list_helpdesk_teams. This gives you the necessary team IDs. - 2 Next, use that ID along with ticket details (subject, description) and priority in a single call to
odoo_create_ticket. - 3 Finally, your AI client executes the operation within Odoo, logging the new ticket into the specified kanban stage.
The bottom line is you use listing tools to gather context (like team IDs or SLA targets), then pass that data to a creation or update tool for the final action.
Who Is Odoo Helpdesk MCP For?
This is for operations managers and support agents who spend too much time clicking between CRM, ticketing dashboards, and sales order screens. If you're tired of context switching to manage customer issues, this tool lets your AI agent handle it all from one chat interface.
You log a new ticket using odoo_create_ticket and check if the team has active SLAs by calling odoo_list_sla_policies to ensure proper workflow.
You find a client's history by running odoo_search_tickets or pull up their contact details and associated sales orders using the general Odoo functions.
You check overall team workload by listing all tickets with odoo_list_tickets, and you verify which teams are responsible for billing or technical support using odoo_list_helpdesk_teams.
What Changes When You Connect
- See the full picture of your team's workload instantly. Running
odoo_list_ticketsgives you a clean view of every open ticket, its priority, and who it's assigned to—no need to jump into the Odoo dashboard just to check status. - Keep SLAs top-of-mind during logging. You can call
odoo_list_sla_policiesfirst to know exactly what response times your team is committed to before you even create the ticket withodoo_create_ticket. - Stop searching through customer emails for details. Use
odoo_search_ticketsto find a specific client issue by subject or keyword, pulling up all relevant data—assignee, stage, and priority—in one shot. - Update records without leaving the chat. Instead of navigating deep into Odoo just to change a ticket's status or reassign it, you use
odoo_update_ticketdirectly through your agent. - Understand your process flow immediately. You can check available categories using
odoo_list_ticket_types, making sure that when you log an issue, the client gets routed under the right classification label.
Real-World Use Cases
The urgent escalation
A customer calls in with a critical bug. The agent uses odoo_search_tickets to check if an issue with that subject already exists. If not, they run odoo_create_ticket, specifying the 'Bug' type and setting the priority to 'Urgent' (3), ensuring immediate visibility for the team.
Checking service commitments
The operations manager asks: 'What is our response time goal for billing issues?' The agent runs odoo_list_sla_policies, which returns the specific targets. This data informs how they should advise new support staff on best practices.
Client history deep dive
A sales rep needs to know everything about a client before calling them back. They first use odoo_list_helpdesk_teams to verify the correct technical team, then they run odoo_list_tickets filtered by that customer's name to see their complete support history.
Reshuffling ownership
A ticket was assigned to the wrong agent. Instead of manually finding the record, the manager uses odoo_update_ticket, referencing the ticket ID and specifying a new assignee. The change is logged instantly.
The Tradeoffs
Trying to find *all* open issues.
Asking for 'the current support queue' without filtering by date or team, resulting in a massive dump of data that is impossible to read.
→
Always start with odoo_list_tickets. If you need something specific, immediately follow up by adding filters like 'Show me only tickets assigned to the Billing Team and marked as New.'
Manually checking team structure.
A new agent has to guess if they should write about 'Technical Support' or 'Level 2 Tech.' and might get an error when trying to create a ticket because the ID is wrong.
→
First, run odoo_list_helpdesk_teams. This confirms the exact team names and IDs you need before attempting any ticket creation via odoo_create_ticket.
Updating a ticket without context.
Saying 'Update that important ticket' when multiple tickets exist for that customer. The agent has no idea which ticket ID to target, leading to the wrong record being modified or an API error.
→
When It Fits, When It Doesn't
Use this server if your primary need is managing the lifecycle of a support ticket within Odoo—creating it, assigning it, updating its status, and tracking its SLA. Specifically, use odoo_search_tickets when you know what about the issue (a subject or keyword). Use odoo_list_tickets when you need to see the entire group of open tickets. Don't use this if your goal is purely sales forecasting or inventory tracking—you'll need a specialized Odoo module for that. If you are just trying to find general contact info, querying the main CRM tools is easier; reserve odoo_list_sla_policies only when SLA compliance metrics are genuinely part of the conversation.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Odoo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Sifting through dashboards just to check ticket status shouldn't take 8 clicks.
Right now, checking on a client issue means logging into Odoo, navigating to the Helpdesk module, filtering by customer name, then clicking through different stages (New, In Progress). You copy the issue ID and paste it elsewhere just to update someone or verify who owns the ticket.
With this MCP server, you simply tell your agent: 'Show me all open tickets for Acme Corp.' The result appears immediately. Your AI client handles the complex querying with `odoo_list_tickets` and gives you a clean list of every active issue.
Odoo Helpdesk MCP Server: Log issues and manage support workflow in chat.
Instead of opening a separate form for every new request, which requires knowing the correct team ID (Technical vs. Billing) and setting the priority manually, you just tell your agent to 'Log an issue about billing.' The tool handles finding the right `team_id` and structuring the ticket perfectly using `odoo_create_ticket`.
The workflow is simple: talk naturally, and the system executes precise actions across CRM and support. You get immediate, accurate data without ever needing to open a single tab.
Common Questions About Odoo Helpdesk MCP
How do I find out what teams are available when using odoo_create_ticket? +
You must first run odoo_list_helpdesk_teams. This returns the list of active team IDs, which you then pass into your ticket creation request to ensure correct routing.
What is odoo_search_tickets used for? +
This tool lets you find an existing ticket by searching keywords in the subject or name. It's faster than listing all tickets when you only remember a small detail about the issue.
Can I change a ticket's owner using odoo_update_ticket? +
Yes. odoo_update_ticket allows you to modify any writable field on an existing record, including reassigning the ticket to a different agent or updating its priority.
Do I need odoo_list_sla_policies for every ticket? +
No. You only need odoo_list_sla_policies when you specifically want to know the time constraints (response/resolution deadlines). Otherwise, use odoo_list_tickets for current status.
What does odoo_list_ticket_types show me? +
It lists all predefined classification labels for tickets. This lets you see if a ticket should be logged as a 'Bug,' 'Feature Request,' or something else. You use this before creating a record to keep your data organized.
How do I check the entire support backlog using odoo_list_tickets? +
It returns a comprehensive list of all tickets, showing who owns them, their current stage (New, In Progress, etc.), and if they have active SLA policies. This gives you an immediate view of team workload.
When using odoo_update_ticket, how do I change the ticket's priority? +
You pass the new priority level (0 to 3) and the ticket ID to update it. Changing the priority instantly affects the SLA tracking status shown on the record.
Can odoo_list_helpdesk_teams help me with team assignments? +
It lists all available support teams, giving you their names and member counts. You use this data to select a valid team ID when calling odoo_create_ticket.
Which Odoo versions are supported? +
This server uses the JSON-RPC protocol, which is compatible with Odoo 14, 15, 16, 17, and 18. Both Odoo Community and Enterprise editions are supported.
Does it work with Odoo.com (SaaS)? +
Yes! Works with both Odoo.com hosted instances and self-hosted Odoo servers. Just provide your instance URL and API key.
How do I generate an API Key? +
Go to Settings → Users → select your user → API Keys tab → New API Key. Give it a descriptive name and copy the generated key.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ThinkStack
Manage AI chatbots via ThinkStack u2014 query bots, manage knowledge sources, review conversations, and configure actions from your AI agent.
Junip
Manage product reviews, questions, and campaigns via Junip API.
BugHerd
Manage BugHerd projects, tasks, and comments through AI Agents.
You might also like
Elastic Email
Equip your AI agent to manage email campaigns, track contacts, and monitor delivery logs via the Elastic Email API.
Concord CLM
Enable your AI agent to manage contracts, send documents for signature, and track agreement statuses via the Concord CLM API.
Webshare
Manage residential and datacenter proxies, rotation settings, and authorized IPs on Webshare — the fast and affordable proxy network.