Hybris MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYBRIS_BASE_URL | Yes | Base URL of your Hybris instance | |
| HYBRIS_HAC_PATH | No | HAC path prefix | /hac |
| HYBRIS_PASSWORD | Yes | Admin password | |
| HYBRIS_USERNAME | Yes | Admin username (HAC access required) | |
| HYBRIS_CATALOG_ID | No | Product catalog ID | electronicsProductCatalog |
| HYBRIS_BASE_SITE_ID | No | OCC base site ID | electronics |
| HYBRIS_CATALOG_VERSION | No | Catalog version | Online |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to '0' to disable TLS certificate validation for local development with self-signed certificates. Warning: Only use in development. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsC | Search for products in the Hybris catalog using a query string |
| get_productC | Get detailed information about a specific product by its code |
| get_categoriesB | Get the category tree from the product catalog |
| get_categoryC | Get details about a specific category |
| get_ordersC | Get orders for a specific user |
| get_orderC | Get details of a specific order |
| flexible_searchC | Execute a FlexibleSearch query against the Hybris database. Use FlexibleSearch syntax. |
| execute_groovyC | Execute a Groovy script in the Hybris scripting console |
| import_impexC | Import data using ImpEx format |
| export_impexC | Export data to ImpEx format using a FlexibleSearch query |
| get_cronjobsB | List all cron jobs and their status |
| trigger_cronjobC | Trigger a cron job to run |
| clear_cacheC | Clear the Hybris cache |
| get_system_infoB | Get Hybris system information and health status |
| trigger_catalog_syncC | Trigger a catalog synchronization between versions |
| health_checkB | Check if the Hybris instance is healthy and reachable |
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 16 tools
Most tools are distinct, but get_categories and get_category could be confused; also get_orders vs get_order are mostly clear but get_orders for a specific user vs get_order for a specific order is somewhat ambiguous. The rest are clearly distinct.
All tools use snake_case with verb_noun pattern, e.g., get_categories, execute_groovy, clear_cache, trigger_catalog_sync. Excellent consistency.
16 tools is slightly high but reasonable for a comprehensive Hybris management server covering catalog, orders, search, system admin, and data operations. Each tool has a defined purpose.
Covers core operations: catalog (categories/products), orders (get/list), search (products, flexible), data (impEx import/export), system (health, cache, cronjobs). Missing product creation/update/delete and order modifications, but these are less common for a read/admin tool; gaps are workaround by impEx.