Greenweez MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GREENWEEZ_CAMOFOX_URL | Yes | URL of the local Camofox Browser service (loopback). Required for the MCP server to function. | |
| GREENWEEZ_CAMOFOX_API_KEY | Yes | Strong API key for the Camofox Browser service. Required for the MCP server to function. | |
| GREENWEEZ_CAMOFOX_USER_ID | No | Optional stable user ID to separate multiple Greenweez accounts on the same machine. | |
| GREENWEEZ_SESSION_DIRECTORY | No | Optional directory to store session bundles, keys, and confirmation tokens. |
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 |
|---|---|
| connect_greenweezA | Retourne un wizard local avec deux liens directs : connexion à un compte existant ou création officielle de compte. Les identifiants restent sur Greenweez. |
| search_productsA | Recherche publique dans le catalogue Greenweez et retourne une page de produits avec les prix observés. |
| get_productB | Lit une fiche produit publique par sa référence et son slug, y compris les informations alimentaires publiées. |
| get_cartA | Relit le panier réel du compte connecté sans demander les adresses, paiements ni données de profil. |
| preview_add_to_cartA | Relit la fiche, l’offre, le stock et le panier, puis crée une confirmation à usage unique valable deux minutes. Ne modifie pas le panier. |
| confirm_add_to_cartA | Consomme une confirmation d’ajout, refuse tout panier modifié entre-temps, ajoute exactement une unité, puis vérifie le panier réel. |
| preview_remove_from_cartB | Relit le panier et crée une confirmation à usage unique pour retirer toute la ligne ciblée. Ne modifie pas le panier. |
| confirm_remove_from_cartB | Consomme une confirmation de retrait, refuse tout panier modifié entre-temps, retire la ligne ciblée, puis vérifie le panier réel. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard_greenweez | Démarre le wizard local Greenweez avant toute action de panier ou de compte. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct: search vs get product, add vs remove, preview vs confirm. However, the preview/confirm pairs (4 tools) could cause an agent to misselect between the add and remove variants without careful reading, and connect_greenweez vs get_cart have somewhat related 'session/account' purposes.
The tool names follow a consistent verb_noun pattern: get_, search_, connect_, preview_, confirm_ prefixes all with clear object names (cart, product, add_to_cart, remove_from_cart). The naming is largely consistent, with preview/confirm pairs being well-paired. Minor deviation: connect_greenweez uses verb_domain-service instead of verb_noun, depa...
8 tools is a reasonable, well-scoped count for an e-commerce cart/catalog server. Each tool maps to a distinct part of the shopping workflow (connect, search, browse, add, remove). Slightly on the larger side but appropriate for the domain.
The server covers the core shopping flow: connecting, searching, viewing products, adding and removing from cart. Notable gaps include a dedicated 'update cart quantity' tool (only add-one/remove-whole-line exist) and no checkout/order placement, but the stated scope (browse and manage cart) is largely covered.