alphamega-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALPHAMEGA_BRIDGE_PORT | No | First port in the bridge port range. The extension only knows ports 8765–8769, so this should only be changed for testing. | 8765 |
| ALPHAMEGA_EXTENSION_ID | No | Chrome extension ID allowed to connect to the bridge. Defaults to the ID from the extension manifest. Multiple IDs can be provided comma-separated. Only needed if the extension was built with a different key. | |
| ALPHAMEGA_CACHE_TTL_SEC | No | Catalog cache lifetime in seconds. Set to 0 to disable caching. | 300 |
| ALPHAMEGA_UNBXD_API_KEY | No | Catalog search API key. Defaults to the key embedded in the store's website; set this if the store changes the key. | |
| ALPHAMEGA_UNBXD_SITE_KEY | No | Catalog search site key. Defaults to the key embedded in the store's website; set this if the store changes the site key. | |
| ALPHAMEGA_MIN_REQUEST_GAP_MS | No | Minimum delay in milliseconds between catalog requests. | 200 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unofficial catalogue search and cart management for the Alphamega Hypermarkets online shop (Cyprus), about 15,000 products. Prices are in EUR and include any current discount; unit_price (per kg / litre / piece) is the fair way to compare pack sizes. Queries work in English and Greek and tolerate typos. Product id is the store's SKU and is stable — keep it when building a basket. Typical flow for a shopping list: call match_shopping_list once with every line, then use search_products to refine lines whose candidates do not fit, and get_products for ingredients or full details. Stock is a yes/no flag per fulfilment store (Larnaca Central, Polemidia); exact quantities are not available here. The cart_* tools change the user's real cart on the website, working through a bridge extension in the user's own Chrome where they are signed in. Agree the basket with the user before calling cart_set, and check the per-product results it returns — the shop may cap or reject a quantity. This server never checks out or pays; the user places the order themselves. The cart tools work in the background — do not call cart_open unless the user asks to see the cart or says they are ready to check out.
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 |
|---|---|
| search_productsA | Search the Alphamega catalogue by free text and/or filters. Returns compact product records (id, title, brand, price, unit price, promotion, barcode, category, stock). Omit |
| get_productsA | Look up specific products by store id (SKU) and/or EAN barcode. Returns full details including Greek title, description and ingredients, plus the ids/barcodes that were not found. |
| list_categoriesA | List catalogue categories with product counts. Without |
| suggestA | Autocomplete for a partial or uncertain search term: returns suggested queries and matching subcategory names. Use when a search returns nothing useful. |
| match_shopping_listA | Search for every line of a shopping list in one call and return the top candidates per line. Use this first when building a basket, then pick one candidate per line (compare |
| cart_loginA | Check whether the user's Chrome is signed in to Alphamega and, if not, open the login page there. The user must sign in themselves (phone number + SMS code); never ask them for the code. Call this when another cart tool reports that login is required. |
| cart_viewA | Read the current cart on alphamega.com.cy: lines (id, title, quantity, unit price, line total) and the order summary (subtotal, delivery, order total). Also reports whether the browser is logged in. |
| cart_setA | Set the quantity of one or more products in the user's real cart on alphamega.com.cy. Quantities are absolute, not increments: 2 means the cart will hold exactly 2, and 0 removes the product. Products not listed are left untouched. Returns per-product results (the shop may cap or reject a quantity) and the resulting cart. Requires the user to be logged in (see |
| cart_clearA | Remove every product from the user's cart on alphamega.com.cy. Only use when the user asked to start the basket from scratch. |
| cart_openA | Bring the cart page to the front in the user's Chrome. This takes over their screen, so call it only when the user asks to see the cart or is ready to check out — not as a routine last step. Checkout, delivery slot and payment are always done by the user; this server cannot place orders. |
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 10 tools
Most tools map to a distinct resource+action: catalogue search/lookup/categories vs. a clearly bounded cart_* family. The main soft overlaps are search_products vs. match_shopping_list (bulk variant of search) and cart_login vs. cart_view, which both report login state, though descriptions steer usage well. suggest is clearly a fallback autocomplete rather than a search itself.
All names are snake_case and readable, with a clean verb_noun pattern for catalogue tools (search_products, get_products, list_categories, match_shopping_list). The cart tools form a predictable cart_<action> namespace, which is a deliberate grouping rather than an inconsistency. Minor deviation: bare `suggest` breaks the verb_noun pattern.
Ten tools is well-scoped for a grocery catalogue + cart server, with no redundant entries. Each tool covers a distinct capability (discovery, lookup, basket building, cart mutation, browser login/surface).
Catalogue side is complete (free-text search, SKU/EAN lookup, category tree, autocomplete fallback) and cart side covers view, absolute-quantity set, clear, login and open. Gaps are mostly intentional (no checkout/payment, explicitly user-driven) but there is no order history or delivery-slot query, and quantity changes are absolute-only, forcing read-modify-write for increments.