odoo_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_DB | No | Database name | odoo |
| ODOO_URL | No | Base URL of your Odoo instance | https://odoo.geosigmoid.group |
| ODOO_PASSWORD | Yes | Password or external API key | |
| ODOO_USERNAME | Yes | Your login email |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_tasksA | List the caller's Odoo tasks (tasks they are assigned to). By default terminal states (done/cancelled/closed) are excluded; pass include_done=true to see everything. Optional filters: project_id, stage_id, exact state code, deadline window due_after/due_before (YYYY-MM-DD). limit=0 means no limit. |
| get_taskA | Fetch one task by id with full detail fields (hours, progress, stage...). |
| update_taskA | Update mutable fields of a task; executes immediately unless dry_run. Field args: name, description (replaces), append_description (appends to the existing description after a blank line), allocated_hours (planned effort), progress (0-100; computed field - prefer allocated_hours), priority (0 low .. 3 urgent), deadline (YYYY-MM-DD), state (workflow code from get_task_states), stage (exact stage display name). With dry_run=true returns {"dry_run": true, "vals": {...}} without writing. |
| post_task_messageA | Post a message to a task's chatter (followers get notified). Returns {"message_id": id}, or {"dry_run": true, ...} with dry_run=true. |
| get_task_statesA | List this server's valid task workflow states as {code, label, terminal}. |
| list_stagesA | List the task stages (project.task.type) available on the server. |
| list_timesheetsA | List the caller's timesheet entries, newest first. Optional filters: task_id restricts to one task; days restricts to the last N days; limit caps the row count (default 50). |
| create_timesheetA | Log hours worked on a task (defaults to today); returns {"entry_id": id}. hours must be > 0; date must be YYYY-MM-DD. With dry_run=true returns {"dry_run": true, "vals": {...}} without writing. |
| update_timesheetA | Modify an existing timesheet entry; returns {"ok": true} on success. Pass at least one of hours (> 0), date (YYYY-MM-DD), description or task_id (moves the entry, keeping its project consistent). With dry_run=true returns {"dry_run": true, "vals": {...}} without writing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: tasks (get, list, update, message, states) and timesheets (list, create, update), plus stage listing. There is no overlap or ambiguity between tool purposes.
Tool names follow a consistent verb_noun pattern throughout: get_task, list_my_tasks, update_task, post_task_message, list_stages, create_timesheet, etc. Minor variation between 'get_task_states' and 'list_stages' is natural and still fits the pattern.
With 9 tools, the set is well-scoped. Each tool serves a clear purpose within the task and timesheet domain, and the count is in the ideal range for usability.
Task and timesheet operations cover the main read/update workflows, including states, stages, and messaging. However, there are notable gaps: no create_task, no delete_task, and no delete_timesheet, which prevents full lifecycle management.