Claude Cowork + Odoo MCP.
Cowork is another Anthropic surface that can use custom remote MCP. It is not a different Odoo API. Use the same governed server as Claude and Desktop.
Same protocol, different window
If Cowork can attach a custom connector, it should hit the same MCP URL you already trust for Claude. Do not stand up a second, looser server “just for Cowork.” Remote MCP · connect Odoo to Claude.
Write tools stay off until you have a named approver. Security.
Who should use Cowork on ERP
Ops and finance people who already live in Claude, not a shadow IT MCP on someone’s laptop. Desktop comparison: Claude Desktop.
One connector catalogue
If Cowork, Claude, and Desktop each get a different MCP URL, you will patch three security stories. One URL, one server, one user, three clients. Write that down as policy.
If Cowork cannot attach custom MCP on your plan, do not invent a side channel. Use the product that can, or change plan. Anthropic’s connector docs are the source, not a blog.
People who should not get Cowork+ERP
Anyone who should not have Odoo UI access should not get Cowork with Odoo tools. MCP is not a way around HR’s access review. Same profile, same review.
Official documentation
FAQ
Is Cowork a different Odoo connector?
It should not be. One MCP server, several clients.
Does Cowork get extra Odoo rights?
Only if you configured extra tools. Don’t.
Keep going
Start read-only. Ask a real question.
Sandbox on sample Odoo 19 data, or we put MCP on your instance.