65 lines
3.5 KiB
Markdown
65 lines
3.5 KiB
Markdown
---
|
|
name: odoo
|
|
description: >
|
|
Access MPM's Odoo ERP system (mpmedia.odoo.com). Use for any question or task
|
|
involving: products, product catalog, stock levels, inventory; knowledge base
|
|
articles; contacts, customers, vendors; sales orders, quotes; CRM leads and
|
|
opportunities; projects and tasks; helpdesk tickets; purchase orders;
|
|
employees and departments. Triggers on: "in Odoo", "our products", "the
|
|
knowledge base", "find a contact", "sales order", "opportunity", "project
|
|
tasks", "helpdesk ticket", "purchase order", "stock", "inventory",
|
|
"employee", "what stage is", "create a task", "update the ticket".
|
|
---
|
|
|
|
# Odoo MPM Skill
|
|
|
|
You have direct access to MPM's Odoo V18 instance at mpmedia.odoo.com via the `odoo-mpm` MCP server.
|
|
|
|
## Connection Details
|
|
- Instance: mpmedia.odoo.com
|
|
- Database: mpmedia-odoo-sh-main-13285275
|
|
- User context: Bryan Gilliom (System Administrator)
|
|
|
|
## Available Modules & Tools
|
|
|
|
### Products (`search_products`, `get_product`, `get_product_stock`)
|
|
Search the product catalog, retrieve product details including pricing and descriptions, and check stock levels across warehouse locations.
|
|
|
|
### Knowledge (`search_knowledge_articles`, `get_knowledge_article`, `create_knowledge_article`, `update_knowledge_article`)
|
|
Read, search, create, and update internal Knowledge base articles. Body content is HTML.
|
|
|
|
### Contacts (`search_contacts`, `get_contact`, `create_contact`)
|
|
Search customers, vendors, and individuals. Use `is_company=true` to filter to companies.
|
|
|
|
### Sales (`search_sales_orders`, `get_sales_order`, `create_sales_order`)
|
|
Look up quotes and sales orders by name (e.g. S00901) or customer. `get_sales_order` includes line items.
|
|
|
|
### CRM (`search_crm_leads`, `get_crm_lead`, `create_crm_lead`, `update_crm_lead`, `list_crm_stages`)
|
|
Manage opportunities in the sales pipeline. Use `list_crm_stages` to get valid stage IDs before updating.
|
|
|
|
### Project (`list_projects`, `get_project`, `search_tasks`, `get_task`, `create_task`, `update_task`, `list_task_stages`)
|
|
Browse projects, search and update tasks. Use `list_task_stages` with a project_id to get valid stage IDs.
|
|
|
|
### Helpdesk (`search_helpdesk_tickets`, `get_helpdesk_ticket`, `create_helpdesk_ticket`, `update_helpdesk_ticket`, `list_helpdesk_teams`)
|
|
Manage support tickets across helpdesk teams.
|
|
|
|
### Purchase (`search_purchase_orders`, `get_purchase_order`)
|
|
Look up purchase orders by name (e.g. P00195) or vendor. `get_purchase_order` includes line items.
|
|
|
|
### Inventory (`search_inventory`, `get_stock_moves`, `list_internal_locations`)
|
|
Check current stock levels and recent stock movements by product.
|
|
|
|
### Employees (`search_employees`, `get_employee`, `list_departments`)
|
|
Look up employee information and department structure.
|
|
|
|
### Utilities (`odoo_search`, `odoo_get_record`)
|
|
Generic tools for any Odoo model — useful for looking up stage IDs, categories, or any other reference data.
|
|
|
|
## Workflow Guidelines
|
|
|
|
- When looking up items by number (e.g. "S00901", "P00195"), use `search_sales_orders` or `search_purchase_orders` with that as the query.
|
|
- Before updating a task or ticket stage, call `list_task_stages` or `odoo_search('helpdesk.stage', 'name', ...)` to confirm valid stage IDs.
|
|
- Knowledge article bodies are stored as HTML — when creating or updating articles, use basic HTML formatting.
|
|
- IDs returned from search tools can be passed directly to `get_*` tools for full details.
|
|
- When the user asks about "our products" without specifying, use `search_products` with no query and limit=20 to show a broad overview.
|