Shop

Search Shopify stores, build carts and check out with Shop Pay from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Shop connector does

The Shop MCP server is Shopify's shopping connector for Claude, built on its Shop app. It searches products across Shopify merchants, finds physical stores, builds carts and opens checkouts with no account. Signed in, it can pay with Shop Pay, read your Shop-tracked orders, and request a one-time card for stores outside Shopify. Payment waits for the shopper's approval.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Shop tools (21)

  • create_checkoutDestructive

    Prepare Shop/UCP checkout only when asked. No separate spend request is needed. Use exact variant IDs/quantities. Share continue_url unchanged for Review and pay, including requires_escalation. Never recreate: get/update its ID. Address incomplete via update. Complete ready_for_complete only after buyer approval. Creates no order.

  • get_checkoutRead-only

    Read with the same shop/exact opaque ID before update/completion or after an uncertain write. continue_url is Review and pay, not a product page/purchase proof.

  • update_checkoutDestructive

    Replace full checkout, not patch/payment. Read first; change only authorized fields; retain all other request fields, including empty objects/arrays. Response-only fields drop. Same shop/exact ID; check status/messages/continue_url. After uncertainty, read before retry.

  • complete_checkoutDestructive

    Send user-approved payment to the same shop/exact checkout ID with one exact offered instrument selected:true. Only completed + order proves purchase. After uncertainty, read get_checkout; never repeat completion or start a replacement purchase.

  • create_cartDestructive

    Create a cart only when asked to save items; interest is not permission. Use exact returned variant IDs/quantities. Use create_checkout for Review and pay. Does not order.

  • get_cartRead-only

    Read with the same shop/exact opaque ID before update or after an uncertain cart write.

  • update_cartDestructive

    Replace full cart, not a patch. Read first; change only authorized fields; retain all other request fields, including empty objects/arrays. Response-only fields drop. Same shop/exact ID; check returned state. After uncertainty, read before retry.

  • get_orderRead-only

    Read one order or package tracked by the signed-in buyer's Shop account. Use the unchanged id from search_orders.orders or search_orders.shipments; unknown purchase facts are omitted. Requires sign-in.

  • search_catalogRead-only

    Find and compare offers by query/like. For an item found elsewhere without a usable ID or URL, search by brand and product name for a possible match, not proof of the same listing. Anonymous works; sign-in adds saved preferences. Context soft; filters hard. Matches/options do not prove the variant. Check messages; ground options, availability, price/currency, rating, seller, and URL in the exact offer. Use get_product only for missing facts/options. Amounts are minor units.

  • lookup_catalogRead-only

    Look for matching offers using product/variant IDs, GTINs, UPCs, or public product URLs, including items found elsewhere. Match returned variant inputs to each identifier (exact versus featured); confirm seller and selected options before treating it as the same offer. A miss does not prove the original item unavailable. Use search_catalog for discovery or possible matches without a usable identifier; get_product only for missing facts. Preserve IDs/URLs; amounts are minor units.

  • get_productRead-only

    Resolve missing details/options for a known product, including items found elsewhere resolved through lookup_catalog. Use its returned ID/exact option name-label pairs; verify effective selection because requests may drop. Ground availability, seller, price/currency, rating, and URL in the exact offer. Skip if prior results prove facts. Amounts are minor units.

  • search_locationsRead-only

    Search shop's physical stores by city, neighborhood, street or postal code (query), by radius around coordinates the user gave (distance), or by item availability (filters.items); filters combine. One shop per call. Omit filters to list every store.

  • lookup_locationsRead-only

    Fetch shop's stores by store ID from search_locations — to re-read a store you saved, or check it against filters.items or distance. Same fields as search; results list which input IDs matched. Up to 10 IDs per call.

  • ask_businessRead-only

    Ask shop a free-form question about its policies, services or facts it has published — returns, shipping thresholds, warranties, support hours — and get a plain-text answer. Read-only: nothing is created, changed or bought. Use catalog tools for what a product is or costs, location tools for stores, and the checkout or order for an order. One shop per call; include every detail in the question (no memory between calls).

  • search_ordersRead-only

    Search the signed-in buyer's Shop-tracked orders and shipments from any store. Returns in-progress orders by default; set filters.status to all to search the full order history.

  • get_accountRead-only

    Read signed-in Shop account, addresses, spend permissions, cards. For missing checkout delivery, copy one addresses[] entry unchanged into fulfillment destinations and select its id; preferred_address_id is default. buyer.email is display-only, never checkout input. Missing is unknown (messages say why); empty spend_permissions means none is set.

  • create_spend_requestDestructive

    Request buyer approval for a purchase where the agent enters a payment credential into a website's checkout form using a browser. Provide the purchase terms and spending limit; name a saved card, or omit it to use the account's preferred card. Share the returned continue_url unchanged for review and approval. This does not pay or place an order.

  • get_spend_requestDestructive

    Read a spend request, optionally requesting an issued card. Omit include to read status and terms only. Set include to "card" to obtain the issued card after the buyer approves the request.

  • update_spend_requestDestructive

    Update the request's address, items, totals or spending limit. Omitted fields stay unchanged. Wallet decides whether its current state allows the update.

  • cancel_spend_requestDestructive

    Cancel the spend request; this does not cancel/refund the purchase or revoke an issued credential.

  • complete_spend_requestDestructive

    Report the purchase attempt's outcome as success or error. Include order details when available, or failure information for an error. This records your report, not payment confirmation.

Read from the server on 2026-11-18, including each tool's own safety annotations.

Limits

  • Newer protocol only. The server answered our 2025-06-18 initialize with an unsupported-version error and listed tools only under 2026-07-28 with server/discover. Shop says older clients cannot connect.
  • Two different payment gates. A spend request is approved by the shopper on a Shop-hosted page before any card is issued, which the server controls. complete_checkout is gated by Shop's instructions telling the assistant to confirm the total and payment method first, so keep your client's approval prompt on for it. Carts and checkouts are created and replaced with no approval step.
  • Never repeat a completion. Shop tells the assistant not to resend complete_checkout after an uncertain result, and to read the checkout instead.
  • Spend requests have hard edges. Cancelling one does not cancel or refund a purchase, or revoke a card already issued, per Shop.
  • One merchant per checkout. A basket from several stores needs one checkout each.
  • Data can be missing or wrong. Shop warns that AI-inferred attributes may be inaccurate.
  • Signed-in tools can be refused. Shop says spend-request tools depend on permissions granted to the client and can fail even when get_account works.
  • We called no tool. Our probe was server/discover, tools/list, resources/list and skills/list, anonymous.

Frequently asked questions

Is Shop MCP free to use?

Yes. Shop's developer site says anonymous Shop MCP search needs no account and no API key, and our anonymous connection on 2026-11-18 listed all 21 tools without a challenge. Searching, looking up stores and opening a checkout cost nothing. You pay only for what you buy, at the merchant's price, and only after you approve the purchase on the merchant's page or in Shop.

Does Shop MCP need an AI agent?

No. Shop says any app can call Shop MCP over HTTPS, because each tool call is a single HTTP request and the server speaks its commerce protocol through MCP tool calls rather than through a model. Claude and other MCP clients are one way in. Shop also publishes a command-line tool and a quickstart for calling the same tools from your own code.

How does personalised search work in Shop MCP?

It needs the shopper to sign in with their Shop account. Shop says that once they do, every search sent with their token is ranked by their preferences, what they browse and what they have bought. Shop also states that none of that preference data reaches the connecting app. Signed out, search still works and returns the same results for everyone.

Are Shop MCP search results always complete?

No. Shop's developer FAQ warns that AI-inferred product attributes may be missing or wrong, and tells builders to handle missing fields and verify availability before linking. The tool descriptions say the same thing in their own way: a search match does not prove the exact variant, and a missed lookup does not prove a product is unavailable. Check the merchant's page before paying.

Sources

Use it in an agent

Put Shop to work.

Connect Shop once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.