Zé Delivery MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZE_ALLOW_MUTATIONS | No | Enable mutations (place order, cancel order, etc.). Must be enabled and explicit_user_intent true for pay tools to do anything. | false |
| ZE_MCP_ALLOWED_ORIGIN | No | Allowed Origin for HTTP transport DNS-rebinding mitigation. | http://127.0.0.1:3000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ze_connection_statusC | Local doctor: token present, mutations off by default, unofficial Zé Delivery GraphQL. |
| ze_capabilitiesB | What this unofficial MCP can read and which writes stay gated. |
| ze_privacy_auditA | Shows redaction defaults (street/phone/GPS) and that place-order is off unless both gates are set. |
| ze_list_categoriesA | Read-only listCategories on the unofficial public GraphQL. Does not place an order. |
| ze_list_groupsA | Read-only listRootProductGroups (Ofertas, Cervejas, …). Does not place an order. |
| ze_load_categoryD | Read-only loadCategory (live 200 with checkout-information-not-found without session). |
| ze_get_cartC | loadCart { cart { id } }. Field names other than cart failed GraphQL validation. |
| ze_product_detailC | loadProduct(id) with category. Read-only. |
| ze_list_payment_methodsC | listPaymentMethods (200 with internal error without a full session). Last-four redacted. Does not charge. |
| ze_load_checkoutA | Read-only loadCheckout. Does not complete payment. |
| ze_checkout_previewA | Read-only loadCheckout query. Does not run the manageCheckout mutation and does not charge. |
| ze_searchA | Read-only searchProducts(queryTerm) on the unofficial GraphQL. Does not add to cart. |
| ze_order_historyA | Past consumer orders. Read-only. Street/phone/GPS redacted. |
| ze_track_orderB | loadOrder(orderNumber). Status only. Does not return GPS polylines or courier phone. |
| ze_bulk_add_to_cartB | bulkAddToCart(bulkAddToCartInput). Dual-gated plus fail-closed 18+ confirmation. Does not checkout. |
| ze_clear_cart_itemsC | clearCartItems. Dual-gated. Does not checkout. |
| ze_apply_couponB | applyCoupon(couponCode: String!). Dual-gated. Does not checkout. |
| ze_rate_orderC | rateOrder(orderNumber, rating). Requires explicit_user_intent. Does not charge. |
| ze_complete_checkoutB | completeCheckout needs access token (401 without). Dual-gated plus 18+ confirmation. |
| ze_place_orderA | Fail-closed. Needs ZE_ALLOW_MUTATIONS and explicit_user_intent. Guest tokens cannot charge. Default examples never enable this. |
| ze_cancel_orderA | Fail-closed. Needs ZE_ALLOW_MUTATIONS and explicit_user_intent. Guest tokens cannot charge. |
| ze_logoutA | Deletes ~/.ze-mcp/tokens.json. Requires explicit_user_intent. |
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 22 tools
Several tools overlap in purpose: ze_checkout_preview and ze_load_checkout both describe the same read-only loadCheckout operation, and ze_place_order versus ze_complete_checkout has unclear boundaries around checkout versus order placement. The three meta tools (ze_connection_status, ze_capabilities, ze_privacy_audit) also cover similar ground, and ze_list_groups/ze_list_categories/ze_load_category are not clearly differentiated.
The ze_ prefix and snake_case are consistent, and many names follow verb_noun (ze_search, ze_apply_coupon, ze_cancel_order). However, there is a mix of noun-phrase names like ze_order_history, ze_product_detail, ze_connection_status, ze_capabilities, and ze_privacy_audit, plus ze_checkout_preview inverts the verb-object order. The pattern is readable but not consistently applied.
22 tools is on the heavy side for the apparent scope, especially with duplicate checkout-reading tools and several overlapping meta/status tools. The count feels padded rather than deliberately minimal, though not so large as to be overwhelming.
Core browsing and ordering flows exist, but there are major gaps: ze_get_cart only returns the cart id, not its contents, and there is no remove-item or update-quantity tool. There is also no login flow to complement ze_logout, and order tracking deliberately omits details like GPS and courier info, leaving agents unable to fully support cart management or order follow-up.