Skip to main content
Glama

Server Details

Shop connected e-commerce stores: search, compare, cart, and checkout with buyer approval.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
themewireco/synchronity
GitHub Stars
0
Server Listing
Synchronity
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 26 tools

Disambiguation4/5

Most tools have clearly distinct roles, and the long descriptions do a good job of clarifying boundaries (e.g. quick_checkout vs create_cart/add_to_cart, delegation vs payment steps). The main confusion risk is between get_cart and get_active_cart, which both retrieve a cart but differ in whether they resume an expired conversation cart or just show contents; an agent could easily misselect. get_payment_status and get_order also overlap on the 'is it paid?' question.

Naming Consistency4/5

The set overwhelmingly follows a snake_case verb_noun convention (create_cart, get_product, apply_coupon, set_shipping_address, list_orders, submit_payment_otp). The only deviation is quick_checkout, which uses an adjective-noun pattern instead of a verb prefix, slightly breaking the predictable pattern but not causing real confusion.

Tool Count4/5

26 tools is slightly above the ideal range, but the domain — multi-site e-commerce spanning catalog, cart, checkout, delegation, and multi-step payments — genuinely justifies the count. Most tools map to a distinct step in a complex lifecycle (3 delegation steps, 4 payment steps, 4 cart operations), so while it feels heavy, few tools are redundant.

Completeness4/5

The surface covers the full shopper lifecycle well: discovery, search, compare, reviews, cart management, coupons, shipping, checkout, payment, delegation, orders, and back-in-stock alerts. Minor gaps exist — there is no remove_coupon or update_order/cancel_order, and order management is read-only after the sale — but these are workable around for most flow and don't create dead ends.

Available Tools

26 tools
add_to_cartAInspect

Add a product variant (or base product) to an existing cart. Reuse the active cart_id from the chat history if one already exists. Only call create_cart first if no cart exists yet.

Inputs: site_id (required), email, items, addons, +4 more. Returns: kind, items, total, cartId, +3 more

apply_couponAInspect

Apply a discount or promotional code to the cart. Returns the updated cart with discount applied.

Inputs: code (required), cart_id (required), site_id (required). Returns: kind, items, total, cartId, +3 more

check_delegationA
Read-only
Inspect

Poll for human approval of a delegation request. When status is "approved", returns the delegation_token to use as buyer_delegation_token in execute_checkout.

Inputs: device_code (required). Returns: status, delivery, user_code, approvalUrl, +2 more

compare_productsA
Read-only
Inspect

Compare products across multiple registered e-commerce sites simultaneously. Uses fail-open strategy: partial results from successful sites are returned even if some sites time out.

Inputs: query (required), site_ids (required), category, in_stock, +2 more. Returns: results

create_cartAInspect

Create a new shopping cart for a specific site. Returns a cart_id. IMPORTANT: Reuse the active cart_id across multiple products in the same session. Do NOT call create_cart again if you already have a cart_id for this site in the chat history.

Inputs: site_id (required), currency. Returns: items, cart_id

execute_checkoutA
Destructive
Inspect

Execute checkout for a cart to create an order. Requires a buyer delegation token (from user auth) and a shipping address. The order is created UNPAID (status "pending"). IMPORTANT — do NOT stop here or just hand the user the payment_url. Immediately continue the in-chat payment flow: call get_payment_methods for the returned order_id, present the available channels to the buyer, and ask which they want to use; then drive initiate_payment → (submit_payment_otp if needed) → poll get_payment_status until the order is paid. The payment_url in the response is only a manual fallback if the buyer declines in-chat payment. Always offer to collect payment in the chat first.

Inputs: cart_id (required), site_id (required), customer_name (required), shipping_city (required), +11 more. Returns: items, total, status, order_id, +1 more

get_active_cartA
Read-only
Inspect

Retrieve the buyer's in-progress cart for a site (resumes a conversation). Call this before assuming a new cart when a shopping conversation continues or after a cart error. Returns the cart with its items rebuilt if the connector cart expired, or null if no cart exists.

Inputs: site_id (required). Returns: kind, items, total, cartId, +3 more

get_cartA
Read-only
Inspect

Retrieve current cart contents, including items, pricing, discounts, and totals. The card already shows the line items and totals to the user, so keep your text reply to one brief sentence — do not re-list the cart contents.

Inputs: site_id (required), cart_id. Returns: kind, items, total, cartId, +3 more

get_orderA
Read-only
Inspect

Retrieve details for an order by its ID, including items, status, shipping, and tracking information. Orders are buyer-private — pass buyer_delegation_token (the delegation token from this buyer's checkout approval) so the gateway can confirm the buyer owns this order. If checking if an order is paid: a status of 'pending' or 'pending_payment' means the order has NOT been paid. Do NOT assume that the vendor storefront has synchronization delays or database lag; treat 'pending' as unpaid. When an order is unpaid, offer to collect payment in the chat by starting the in-chat payment flow (get_payment_methods → initiate_payment → get_payment_status) rather than only pointing the user at the payment_url. Do not mark the purchase task as successful until the status updates to 'processing' or 'completed'.

Inputs: site_id (required), order_id (required), buyer_delegation_token. Returns: items, total, status, order_id, +1 more

get_payment_methodsA
Read-only
Inspect

STEP 1 of the in-chat payment flow. Returns the payment channels available for an order (e.g. "mobile_money", "card") plus a gateways array of the enabled payment gateways (each with id, label, and its channels). When more than one gateway is listed, ask the buyer which they want to use and pass it as gateway to initiate_payment. Call this first, after an order exists. Then call initiate_payment with the chosen channel (and gateway if more than one). site_id falls back to DEFAULT_SITE_ID if omitted.

Inputs: order_id (required), site_id. Returns: mobile_money_provider_labels

get_payment_statusA
Read-only
Inspect

FINAL STEP of the in-chat payment flow. Returns the current PaymentSession for an order. Poll this (every ~5 seconds) after initiate_payment/submit_payment_otp until payment_status becomes "paid" or "processing" (success — the order is confirmed) or "failed" (tell the user; they can retry by initiating a new payment). Do NOT treat the purchase as complete until this returns "paid" or "processing". No delegation needed (read-only).

Inputs: order_id (required), site_id. Returns: message, reference, instruction, payment_status

get_productA
Read-only
Inspect

Retrieve detailed information about a specific product including variants, pricing, images, and availability. May also return addons — customer-selectable options defined by the store (e.g. engraving, gift wrap, size add-ons). When a product has addons, present them to the buyer and collect every addon with required: true before calling add_to_cart; for any option carrying a price_modifier, show that surcharge so the buyer knows the added cost. The card already shows the product details to the user, so keep your text reply brief and do not re-describe what the card displays.

Inputs: site_id (required), product_id (required). Returns: url, kind, image, price, +7 more

get_product_reviewsA
Read-only
Inspect

🔍 RECOMMENDED STEP — Fetch product reviews and authenticity consensus before making purchase decisions. Returns: average rating, trust score (0.0-1.0), review sentiment analysis, authenticity flags (fake reviews, seller issues, negative trends), and recent reviews with verified purchase status. Always call this for each product before adding to cart to verify quality and detect scams.

Inputs: site_id (required), product_id (required), page, limit. Returns: reviews, authenticity_consensus

initiate_paymentA
Destructive
Inspect

STEP 2 of the in-chat payment flow. Starts a payment session for an order and returns a PaymentSession with an instruction the agent renders in chat. REQUIRES a buyer_delegation_token — obtain it exactly like execute_checkout: call request_delegation, have the user approve in chat, then check_delegation to get the token (spending money always needs human approval). For channel "mobile_money" you MUST collect the buyer's phone (Ghana: 055… or +233…) and provider — use codes mtn, vod (Vodafone/Telecel), or tgo (AirtelTigo); aliases telecel→vod, tigo→tgo are accepted. ALWAYS quote the Show this instruction to the buyer line from the response verbatim (Paystack display_text). For channel "card", no phone/provider is needed; the response instruction contains an authorization_url you send the user to. After calling: if instruction.action == "submit_otp", ask the user for the OTP and call submit_payment_otp. If instruction.action == "approve_on_phone", tell the user to approve the prompt on their phone, then poll get_payment_status. If instruction.action == "redirect" (card), send the user the authorization_url, then poll get_payment_status.

Inputs: channel (required), order_id (required), phone, gateway, +3 more. Returns: message, reference, instruction, payment_status

list_ordersA
Read-only
Inspect

List recent orders for a site, optionally filtered by status (pending, processing, completed, cancelled, refunded). Orders are buyer-private — pass buyer_delegation_token (from this buyer's checkout approval); only that buyer's orders are returned.

Inputs: site_id (required), page, status, per_page, +1 more. Returns: orders

list_sitesA
Read-only
Inspect

List all registered e-commerce sites. Use this first to find a site by name (e.g. "Pronto Partners") and get its site_id, which is required by all other tools.

Inputs: no named parameters. Returns: sites

quick_checkoutAInspect

Assemble checkout-ready cart(s) in ONE call for a multi-product (and optionally multi-store) request. Creates a cart per store, adds all items, and sets the shipping address — then returns the cart(s) with delivery options to choose. Use this when the buyer lists several products at once (optionally across stores) and/or gives their address up front, instead of calling create_cart/add_to_cart/set_shipping_address separately. Does NOT select delivery, check out, or pay — the buyer picks delivery (select_shipping_option) and approves checkout/payment per store afterward. Out-of-stock items are reported; pass customer.email to auto-arm a back-in-stock alert for them.

Inputs: items (required), shipping_address (required), customer. Returns: object

remove_from_cartA
Destructive
Inspect

Remove a line item from the cart. Requires the item_id from the cart contents.

Inputs: cart_id (required), item_id (required), site_id (required). Returns: kind, items, total, cartId, +3 more

request_back_in_stockAInspect

Subscribe the buyer to a back-in-stock alert for an out-of-stock product. Use when the buyer asks to be notified/told/pinged when an item restocks ("notify me when X is back", "let me know when it's in stock"). Collect the buyer's email so the alert can reach them (without it only the demand is recorded for the merchant). The buyer is emailed when the product is next seen in stock. Returns whether an email alert was armed.

Inputs: site_id (required), product_id (required), email, variant_id, +1 more. Returns: object

request_delegationAInspect

Start the human delegation (approval) flow needed for checkout/payment. PREFERRED: pass the buyer's email — the gateway emails them a 6-digit code and returns a device_code; ask the user for the code and call submit_delegation_otp. This keeps approval fully in-chat (no link) and you never see the code, so you cannot approve on their behalf. If you omit email, it falls back to a browser approval link (device flow) which the user must open; then poll check_delegation. You can never approve a delegation yourself.

Inputs: site_id (required), email, scopes, marketing_opt_in. Returns: status, delivery, user_code, approvalUrl, +2 more

search_productsA
Read-only
Inspect

Find products on a registered store. To BROWSE a store's catalog (open-ended requests like "what do they sell", "show me what's available"), call with NO query — this returns the store's products. To SEARCH, pass query (a product name/keyword). Returns paginated products as an interactive card. ALWAYS translate a buyer's budget or price constraint into the price params on THIS call instead of filtering in your reply: "under/below/within X" or "X budget" → max_price: X; "over/above/at least X" → min_price: X; "between X and Y" → both. Likewise pass in_stock: true for "available"/"in stock" and category when they name one. The card renders exactly what this call returns, so the filter MUST be applied here — never fetch the full catalog and then narrow it in text. Call once with your best intent (browse OR a single query); if a real search is genuinely empty, ask the user to clarify rather than re-firing reworded queries. The card shows products, prices, IDs, and Add-to-cart controls — keep your text reply to one brief sentence and do not re-list what the card shows.

Inputs: site_id (required), page, query, queries, +5 more. Returns: kind, siteId, products, siteName

select_shipping_optionAInspect

Select one of the shipping options returned by set_shipping_address. Binds the rate to the cart so the total includes shipping; call before execute_checkout so the hosted checkout opens pre-filled.

Inputs: cart_id (required), site_id (required), option_id (required). Returns: kind, items, total, cartId, +5 more

set_cart_quantityA
Destructive
Inspect

Set a cart line's quantity (the server cart is the checkout source of truth, so this updates it live). Requires the item_id from the cart contents and the new absolute quantity. A quantity of 0 removes the line. Returns the updated cart card.

Inputs: cart_id (required), item_id (required), site_id (required), quantity (required). Returns: kind, items, total, cartId, +3 more

set_shipping_addressAInspect

Set the cart shipping destination (collected from the buyer) and return available shipping options with costs. Call after items are in the cart and before select_shipping_option. country_code is required; include postal_code/state for accurate rates.

Inputs: cart_id (required), site_id (required), country_code (required), city, +2 more. Returns: kind, items, total, cartId, +5 more

submit_delegation_otpAInspect

Submit the 6-digit code the buyer received by email (from request_delegation with an email) to approve the delegation in-chat. On success returns a delegation_token to use as buyer_delegation_token for checkout/payment. You cannot obtain this code yourself — the user must read it from their email and give it to you.

Inputs: code (required), device_code (required), site_id. Returns: status, delivery, user_code, approvalUrl, +2 more

submit_payment_otpA
Destructive
Inspect

STEP 3 (mobile_money only, when initiate_payment returned instruction.action == "submit_otp"). Submits the one-time password the buyer received to authorise the mobile-money charge. REQUIRES the same buyer_delegation_token used for initiate_payment. After submitting, poll get_payment_status until payment_status is "paid"/"processing" or "failed".

Inputs: otp (required), order_id (required), site_id, buyer_delegation_token. Returns: message, reference, instruction, payment_status

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables product discovery, seller-offer comparison, and bounded, approval-gated cart operations with account-scoped planning and read-back reconciliation.
      40
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely search products, obtain signed quotes, create checkouts, and track orders without directly handling prices or payment amounts, enforcing spending policies and audit trails.
      1
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.