Continente MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTINENTE_CREDENTIALS_FILE | No | Absolute path to the credentials file if kept elsewhere. Default is ~/.continentept-mcp/credentials.env |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search the Continente.pt catalogue. No login needed. Results keep the website's relevance order, with products from your saved favorites first, and show each price with what it is for (per item, piece, kg or litre), the pack size and productId. Reads at most five result pages, so completeness may be "unknown" for broad queries. |
| get_productA | Get one product by productId: price, availability and sale rules (sale unit, minimum, maximum and step). Check this before choosing a quantity for weighted or bulk products. No login needed. |
| list_favoritesA | List the products saved as favorites on the account. Uses a local snapshot that is refreshed automatically when missing; snapshots older than 24 hours are marked stale. Pass refresh: true to fetch the current list from the website. |
| get_cartA | Read the shopping cart: each line with productId, cartItemId, kind (product or bag), quantity, unit price (per item or per kg) and lineTotal, plus the totals (products, bags, deposit, delivery, discounts and grandTotal, the amount to pay). Use it to check current quantities before changing them and to verify any uncertain change. |
| add_cart_itemA | Add an amount of a product to the cart, on top of any quantity already there. quantity is in the product sale unit (default 1). Use set_cart_item_quantity instead when the user wants a specific total. If the result has mutation.outcome "unknown", the cart may have changed: call get_cart before any further change and never repeat the request automatically. |
| set_cart_item_quantityA | Make the cart hold exactly this quantity of a product, adding it if it is not there yet. Zero removes it. Pass cartItemId from get_cart when the product has more than one line. If the result has mutation.outcome "unknown", the cart may have changed: call get_cart before any further change and never repeat the request automatically. |
| remove_cart_itemA | Remove a product line from the cart. Succeeds without changes if it is already absent. Pass cartItemId from get_cart when the product has more than one line. If the result has mutation.outcome "unknown", the cart may have changed: call get_cart before any further change and never repeat the request automatically. |
| list_ordersA | List recent orders, newest first, with their product lines. Each order has an orderId for get_order. Use detailLimit or includeLines: false to read fewer details, and pass the returned nextCursor as cursor to continue. |
| get_orderA | Get the product lines of one order by its orderId from list_orders (not the displayed order number). |
| list_frequently_bought_productsA | Rank products by how many recent orders contained them, with total quantities per unit. orderLimit sets how many recent orders to read (default 10); limit caps the products returned (default 25). Useful for building a usual shopping list. |
| get_session_statusA | Report local state without contacting the website: browser status, whether credentials and saved cookies exist, the last observed login state and favorites snapshot freshness. Never returns secrets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| basket-planner | Workflow for choosing products, checking sale quantities and changing the cart safely. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct resource+action: browsing (search_products, get_product), cart reads/writes (get_cart, add_cart_item, set_cart_item_quantity, remove_cart_item), orders (list_orders, get_order), and account data. The potentially confusable cart tools are explicitly differentiated, e.g. add_cart_item vs set_cart_item_quantity are clarified with a direct pointer to use one over the other.
All names follow a consistent snake_case verb_noun pattern (list_favorites, get_order, add_cart_item, remove_cart_item, get_session_status). No mixing of conventions or vague verbs.
11 tools is well-scoped for a grocery e-commerce domain, with each tool earning its place across browsing, cart, and order workflows. Nothing redundant or filler.
The surface covers catalogue browsing, full cart lifecycle, order history, and frequently-bought analysis well. Minor gaps remain: favorites can only be listed (no add/remove), and there is no checkout/place-order action, though the latter may be an intentional safety omission.