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 |
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
Server capabilities have not been inspected yet.
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 have distinct purposes targeting specific Hybris resources or operations, with clear boundaries like flexible_search vs search_products. However, health_check and get_system_info have some overlap in monitoring functionality, which could cause minor confusion.
Tools follow a consistent verb_noun naming pattern throughout, such as get_product, search_products, and trigger_cronjob. The only minor deviation is clear_cache, which uses an adjective instead of a verb, but overall the naming is highly predictable and readable.
With 16 tools, the count is slightly high but reasonable for a Hybris server covering cache, scripting, data operations, catalog, orders, and system monitoring. It feels comprehensive without being overwhelming, though it borders on the heavy side.
The tool set covers key Hybris domains well, including data import/export, product/category management, order handling, and system operations. Minor gaps exist, such as no update or delete operations for products or orders, but agents can work around these using scripts or other tools.