Skip to main content
Glama
parth-unjiya

odoo-mcp-gateway

by parth-unjiya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ODOO_DBYesOdoo database name
MCP_HOSTNoHTTP host (streamable-http mode)127.0.0.1
MCP_PORTNoHTTP port (streamable-http mode)8080
ODOO_URLNoOdoo server URLhttp://localhost:8069
MCP_LOG_LEVELNoLogging levelINFO
MCP_TRANSPORTNoTransport mode (stdio or streamable-http)stdio

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginB

Authenticate with Odoo. Methods: 'api_key', 'password', or 'session'.

list_modelsB

List available Odoo models. Optionally filter by keyword.

get_model_fieldsB

Get field definitions for an Odoo model.

search_readC

Search and read records from any Odoo model.

get_recordC

Read a single record by ID from any Odoo model.

search_countB

Count records matching a domain in an Odoo model.

create_recordC

Create a new record in an Odoo model.

update_recordC

Update an existing record in an Odoo model.

delete_recordB

Delete a record from an Odoo model.

read_groupC

Read grouped/aggregated data from an Odoo model.

execute_methodC

Execute a method on an Odoo model.

check_inA

Record attendance check-in for the current user.

        Finds the employee linked to the current user and creates
        an attendance record with check_in set to now.
check_outA

Record attendance check-out for the current user.

        Finds the open attendance record and sets check_out to now.
get_my_attendanceC

Get attendance records for the current user.

        Args:
            limit: Max records to return (default 10)
            month: Filter by month (YYYY-MM format, optional)
get_my_leavesB

Get leave requests for the current user.

        Args:
            state: Filter by state (draft, confirm, validate, refuse)
            limit: Max records (default 20)
request_leaveB

Submit a leave request.

        Args:
            leave_type_id: Leave type ID (e.g. annual leave, sick leave)
            date_from: Start date (YYYY-MM-DD)
            date_to: End date (YYYY-MM-DD)
            reason: Optional description
get_my_profileB

Get the current user's employee profile.

get_my_quotationsB

Get quotations/orders where the current user is the salesperson.

        Args:
            state: Filter by state (draft, sent, sale, done, cancel)
            limit: Max records (default 20)
get_order_detailsB

Get full order details with lines, totals, and partner info.

        Args:
            order_id: The sale order ID
confirm_orderB

Confirm a quotation, turning it into a sale order.

        Args:
            order_id: The sale order ID to confirm (must be in draft/sent state)
get_sales_summaryA

Get aggregated sales stats for the current user.

        Returns counts by state, totals by month, and top customers.

        Args:
            period: Filter period (YYYY-MM format, optional).
                If omitted, returns all-time stats.
get_my_tasksB

Get tasks assigned to the current user.

        Args:
            state: Filter by task state (e.g. 01_in_progress, 1_done)
            project_id: Filter by project ID
            limit: Max records (default 20)
get_project_summaryB

Get project stats: task counts by stage, overdue, recent activity.

        Args:
            project_id: The project ID to summarize
update_task_stageC

Move a task to a different stage.

        Args:
            task_id: The task ID to update
            stage_id: The target stage ID
get_my_ticketsB

Get helpdesk tickets assigned to the current user.

        Args:
            state: Filter by stage name (optional)
            priority: Filter by priority (0=Low, 1=Medium, 2=High, 3=Urgent)
            limit: Max records (default 20)
create_ticketB

Create a new helpdesk ticket.

        Args:
            name: Ticket subject/title
            description: Detailed description
            team_id: Helpdesk team ID (optional)
            priority: Priority level (0=Low, 1=Medium, 2=High, 3=Urgent)
update_ticket_stageB

Move a helpdesk ticket to a different stage.

        Args:
            ticket_id: The ticket ID to update
            stage_id: The target stage ID

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_modelAnalyze an Odoo model's structure, fields, and relationships. Provides a comprehensive prompt for understanding any model.
explore_dataExplore data in an Odoo model based on a natural language question.
create_workflowGuide through a workflow on an Odoo model.
compare_recordsCompare two or more records from the same model.
generate_reportGenerate an analytical report from Odoo data.
discover_custom_modulesDiscover and understand custom Odoo modules installed.
debug_accessDebug access issues for a model.

Resources

Contextual data attached and managed by the client

NameDescription
list_models_resourceList all accessible Odoo models. Returns JSON array of model objects with name, description, is_custom, and access_level.
categories_resourceList available model categories with counts. Returns JSON object mapping category names to model counts.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 27 tools

Disambiguation4/5

Most tools have distinct purposes, but some potential confusion exists between generic tools like create_record/update_record/delete_record and specific ones like create_ticket/update_ticket_stage. The generic tools could overlap with domain-specific operations, though descriptions help clarify their scope.

Naming Consistency4/5

Tools follow a consistent snake_case pattern with clear verb_noun structure (e.g., get_my_tickets, update_task_stage). Minor deviations include 'login' (no noun) and 'read_group' (unusual verb order), but overall naming is predictable and readable.

Tool Count3/5

With 27 tools, the count feels heavy for a single server, bordering on excessive. While Odoo is a broad ERP system, the toolset includes both generic (e.g., create_record) and specific operations, which could be streamlined or better organized.

Completeness5/5

The toolset provides comprehensive coverage for Odoo's core domains: attendance, sales, helpdesk, projects, and HR. It includes CRUD operations, specific workflows (e.g., confirm_order, request_leave), and utility tools (e.g., list_models, login), leaving no obvious gaps for agent interaction.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources