ecom-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_DB | No | Odoo database name – required for Odoo integration. | |
| ODOO_URL | No | Odoo instance URL – required for Odoo integration. | |
| ODOO_API_KEY | No | Odoo API key – required for Odoo integration. | |
| ODOO_USERNAME | No | Odoo username – required for Odoo integration. | |
| ASANA_ACCESS_TOKEN | No | Asana personal access token – required for Asana integration. | |
| SHOPIFY_ACCESS_TOKEN | No | Shopify access token – required for Shopify integration. | |
| SHOPIFY_STORE_DOMAIN | No | Shopify store domain (e.g., your-store.myshopify.com) – required for Shopify integration. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shopify_get_ordersC | List Shopify orders (any/open/closed/cancelled) |
| shopify_get_orderB | Get a single Shopify order by ID |
| shopify_get_inventoryC | Get Shopify inventory levels, optionally filtered by location |
| odoo_search_readC | Run a search_read against any Odoo model (e.g. sale.order, res.partner, product.product) |
| odoo_get_stock_levelA | Look up available/forecast stock for a product by (partial) name |
| odoo_create_sale_orderB | Create a sale order in Odoo for a customer with line items |
| asana_create_taskC | Create an Asana task in a project |
| asana_get_tasksA | List tasks in an Asana project |
| asana_update_task_statusC | Mark an Asana task complete or incomplete |
| export_report_to_excelC | Export tabular data (e.g. combined order/stock/task data) to an .xlsx file on disk |
| fulfill_shopify_orderB | The ops-hub flow: pull a Shopify order, create the matching Odoo sale order, open an Asana fulfillment task, and return a combined summary. This is the one-call replacement for manually copying an order across three tools. |
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 11 tools
Most tools are clearly separated by system prefix and resource, but odoo_search_read is a generic fallback that overlaps with odoo_get_stock_levelanding fulfill_shopify_order duplicates the multi-tool workflow, creating some selection ambiguity for agents.
Naming follows a mostly verb_noun pattern with system prefixes, but conventions differ: shopify_get_orders vs odoo_search_read, export_report_to_excel lacks a system prefix, and fulfill_shopify_order inverts the prefix order. This mixed style is readable but not fully consistent.
Eleven tools cover three external systems plus reporting and a composite workflow without feeling bloated. Each tool has a clear niche, and the count aligns well with the server's multi-system e-commerce operations scope.
The core order-to-fulfillment lifecycle is covered: fetch Shopify orders, create Odoo sale orders, manage Asana tasks, and export data. Minor gaps exist—no Shopify order updates, no single Asana task detail, and no Odoo sale order modification—but the generic odoo_search_read and composite fulfill tool mitigate most dead ends.