eCommerce

synchronity.app

Integrates with e-commerce platforms to search, retrieve product details, reviews, and manage back-in-stock notifications.

1 endpoint26 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://api.synchronity.app/mcp

No auth detected

MCP server metadata

Name: synchronity-mcp
Version: 0.2.0

Capabilities

toolsresources

Server instructions

Synchronity is a shopping server for the e-commerce stores a user has connected to their Synchronity account. It covers product search and details, reviews, cart building, shipping options, coupons, checkout, payment status, and order history. COVERAGE: these tools read only from connected stores, live from each merchant. Product data, prices, stock, and orders returned here are specific to this user's connected stores and are not derived from public web listings. SITE IDS: every tool except list_sites takes a site_id. list_sites returns the connected stores with their IDs and matches partial or approximate store names. BROWSING vs SEARCHING: search_products with no query returns the store's catalog, which is what an open-ended request for what a store carries needs. Passing a query searches for a specific product name or keyword. Price, category, and stock filters are applied server-side and change which products come back. CART: add_to_cart adds a line, set_cart_quantity sets a line's absolute quantity (0 removes it), and remove_from_cart drops a line. get_cart returns the authoritative totals including tax, shipping, and discounts, which is what checkout charges. RESUMING: get_active_cart(site_id) returns the buyer's in-progress cart for a store, so an interrupted or continued shopping session can pick up its existing items instead of starting over. CHECKOUT: checkout and payment complete only with the buyer's explicit approval, given as a one-time code emailed to them and entered by them. An order is complete when the payment status is paid or the order is processing or completed; any other status means it is not.

Known tools 26

list_sites

List all registered e-commerce sites.

Inferred read-only

search_products

Find products on a registered store.

Inferred read-only

get_product

Retrieve detailed information about a specific product including variants, pricing, images, and availability.

Inferred read-only

get_product_reviews

🔍 **RECOMMENDED STEP** — Fetch product reviews and authenticity consensus before making purchase decisions.

Potential side effects

request_back_in_stock

Subscribe the buyer to a back-in-stock alert for an out-of-stock product.

Inferred read-only

compare_products

Compare products across multiple registered e-commerce sites simultaneously.

Inferred read-only

create_cart

Create a new shopping cart for a specific site.

Potential side effects

add_to_cart

Add a product variant (or base product) to an existing cart.

Inferred read-only

quick_checkout

Assemble checkout-ready cart(s) in ONE call for a multi-product (and optionally multi-store) request.

Inferred read-only

remove_from_cart

Remove a line item from the cart.

Potential side effects

set_cart_quantity

Set a cart line's quantity (the server cart is the checkout source of truth, so this updates it live).

Inferred read-only

apply_coupon

Apply a discount or promotional code to the cart.

Inferred read-only

get_cart

Retrieve current cart contents, including items, pricing, discounts, and totals.

Inferred read-only

get_active_cart

Retrieve the buyer's in-progress cart for a site (resumes a conversation).

Inferred read-only

set_shipping_address

Set the cart shipping destination (collected from the buyer) and return available shipping options with costs.

Inferred read-only

select_shipping_option

Select one of the shipping options returned by set_shipping_address.

Inferred read-only

execute_checkout

Execute checkout for a cart to create an order.

Potential side effects

get_order

Retrieve details for an order by its ID, including items, status, shipping, and tracking information.

Inferred read-only

list_orders

List recent orders for a site, optionally filtered by status (pending, processing, completed, cancelled, refunded).

Inferred read-only

request_delegation

Start the human delegation (approval) flow needed for checkout/payment.

Potential side effects

submit_delegation_otp

Submit the 6-digit code the buyer received by email (from request_delegation with an email) to approve the delegation in-chat.

Potential side effects

check_delegation

Poll for human approval of a delegation request.

Inferred read-only

get_payment_methods

STEP 1 of the in-chat payment flow.

Potential side effects

initiate_payment

STEP 2 of the in-chat payment flow.

Potential side effects

submit_payment_otp

STEP 3 (mobile_money only, when initiate_payment returned instruction.

Inferred read-only

get_payment_status

FINAL STEP of the in-chat payment flow.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.synchronity-mcp]
url = "https://api.synchronity.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "synchronity-mcp": {
      "type": "http",
      "url": "https://api.synchronity.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: synchronity-mcp
Remote MCP URL: https://api.synchronity.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "synchronity-mcp": {
      "url": "https://api.synchronity.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "synchronity-mcp": {
      "type": "http",
      "url": "https://api.synchronity.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "synchronity-mcp",
  "transport": "streamable-http",
  "url": "https://api.synchronity.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.