Menu
Mattering Automations connector

A Snipcart MCP for the work after checkout, not just the cart on the page

Connect one Snipcart secret API key and 43 nodes land on the canvas: read and update orders, issue refunds, keep products and inventory in step with your source of truth, run discounts, chase abandoned carts, watch subscriptions, and manage shipping methods. The same key selects Test or Live mode, so a workflow can be built and rehearsed in Test before it ever touches a real order.

43 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Snipcart MCP connector does

The Snipcart connector for Mattering Automations is 43 nodes on Snipcart's REST API: 24 read nodes and 19 action nodes across orders, refunds, order notifications, customers, products, discounts, abandoned carts, subscriptions, shipping methods, allowed domains and the storefront domain setting. Snipcart is the cart and checkout you embed in a site you already own, which means the interesting automation work is almost always downstream of the buy button: fulfilment status, inventory that has to match a warehouse, a refund somebody has to approve, a cart that stopped one step short. Those are the nodes here.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent handling a customer email can look the order up with Snipcart: List Orders, read what shipped with Snipcart: Get Order, and check whether a refund already exists with Snipcart: List Order Refunds, without anyone opening the Snipcart dashboard. Snipcart also publishes an MCP server of its own, which is covered in the FAQ below rather than skipped over.

One property of Snipcart shapes how you should set this up, and it is unusually good news. Snipcart keys are created in Test mode or in Live mode, and Snipcart documents the two environments as isolated from each other: a Test key cannot read Live data and a Live key cannot read Test data. Paths, envelopes and behaviour are the same in both. So a Test credential is a full rehearsal environment rather than a reduced one, and Snipcart's own documentation states that in the Test environment, using Snipcart is 100% free. Connect a Test credential first, build the workflow against it, then connect the Live key when the shape is settled.

The safety modeling is stated rather than implied. Five nodes are flagged destructive: Snipcart: Create Refund, Snipcart: Delete Customer, Snipcart: Delete Discount, Snipcart: Cancel Subscription and Snipcart: Delete Shipping Method. Snipcart's own warning on the first one is the reason it is classed that way: creating a refund is irreversible and submits the refund to the payment gateway that processed the original order, so money leaves the merchant account on the call with no approval step in between. Deleting a shipping method is the quiet one: it is live checkout configuration, so removing the only method covering a region means shoppers there cannot check out. In Test mode none of this touches a real gateway, which is exactly why the Test key is worth setting up first.

One connection, three surfaces

  • Visual automations. Drag Snipcart nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Snipcart node, ready to drop on the canvas

43 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 24

Snipcart: Count Subscriptions

Count subscriptions in the given states. Returns a bare NUMBER, not an object, so the count lands at data itself. The cheapest way to alert on churn: count Stopped or CancellationRequested on a schedule.

Snipcart: Get Abandoned Cart

Read one abandoned cart by its token: line items, quantities, totals, the shopper's email and the cart's current status.

Snipcart: Get Customer

Read one customer account by its id: email, confirmation status, billing and shipping addresses, and lifetime statistics (order count, total spend, subscription count).

Snipcart: Get Default Domain

Read the account's default domain and protocol. This is the domain Snipcart's cart is licensed to run on, so it is worth asserting in a deploy check before a release.

Snipcart: Get Discount

Read one discount by its id, including how many times it has been used (numberOfUsages) and how many uses are still on uncompleted carts (numberOfUsagesUncompleted).

Snipcart: Get Order

Read one order by its token, including line items, applied discounts, taxes, addresses, tracking details and any pending withdrawal requests. This is the full order; the list endpoint's Excerpt format is the light version.

Snipcart: Get Product

Read one product by its Snipcart GUID or your own user-defined id, including stock, the inventory management method (Single, Variant or Disabled), whether out-of-stock purchases are allowed, and per-variant stock levels.

Snipcart: Get Refund

Read one refund on an order by its id: amount, comment, creation and modification dates, and whether the payment gateway processed it.

Snipcart: Get Shipping Method

Read one custom shipping method by its id: rates, weight and order-total conditions, country and province restrictions, postal-code regular expression, shipping zone and guaranteed delivery days.

Snipcart: Get Subscription

Read one subscription: state, schedule, subscriber, payment status, gateway id and upcoming payments. Set version to V3 when the id you hold is an order token; leave it at V1 for a subscription GUID.

Snipcart: Get User Session

Exchange a customer session token for the logged-in shopper's account: email, confirmation status, lifetime order statistics and both addresses, plus the session's expiry. Use it to identify the shopper behind a checkout in progress. The customer object sits at data.customer.

Snipcart: List Abandoned Carts

List carts a shopper started and never completed, with their line items, totals and the shopper's email where known. This is the recovery-campaign feed. Note the pagination differs from the rest of the API: it uses a continuation token, so pass data.continuationToken back on the next call while data.hasMoreResults is true. Rows land at data.items[].

Snipcart: List Allowed Domains

List the additional domains and subdomains the cart is permitted to load on, beyond the default domain - staging hosts, preview deploys, tunnels. Returns a bare JSON array, so rows land at data[].

Snipcart: List Customer Orders

List every order placed by one customer, with totals, payment method, shipping method and addresses. Returns a bare JSON array, so rows land at data[] - unlike List Orders, which is a paged object.

Snipcart: List Customers

List customer accounts with their lifetime order counts and totals, filtered by confirmation status, exact email, partial billing name or creation date range. Offset paginated: rows land at data.items[]. This is the source node behind every customer picker in this connector.

Snipcart: List Discounts

List every discount on the account with its trigger, type, code, rate or amount, usage caps, usage counts, expiry and archived flag. Snipcart returns the WHOLE list as a bare JSON array with no pagination and no filters, so rows land at data[]. This is the source node behind the discount picker.

Snipcart: List Order Digital Goods

List the digital goods attached to an order with their download URLs, how many times each has been downloaded, the download cap, days until expiry, and whether the link is still valid. Returns a bare JSON array, so rows land at data[].

Snipcart: List Order Notifications

List the notifications and internal comments recorded against one order, newest first: invoices, tracking emails, refund notices, digital-download links and free comments, each with its delivery method and the time it was sent. Offset paginated: rows land at data.items[].

Snipcart: List Order Refunds

List every refund already issued against one order, with amounts, comments and whether the payment gateway processed each one. Returns a bare JSON array, so rows land at data[]. Run this before Create Refund to see what has already gone back.

Snipcart: List Orders

List completed orders, newest first, with filters for status, payment status, date range, purchaser, invoice number, product and billing or shipping address. This is the Gate 1 auth probe: it needs no parameters and is the vendor's own example request. Offset paginated: rows land at data.items[] with data.totalItems giving the full count. This is the source node behind every order picker in this connector.

Snipcart: List Products

List products Snipcart has seen in your carts, each with its price, image and SALES STATISTICS (number of sales and total sales value) computed over the from/to window. This is Snipcart's closest thing to a sales report: the date range bounds the statistics, not the rows. Offset paginated: rows land at data.items[]. This is the source node behind every product picker in this connector.

Snipcart: List Shipping Methods

List the account's manually defined shipping methods with their tiered rates, weight and order-total conditions, country and province restrictions, postal-code pattern and guaranteed delivery window. Returns a bare JSON array, so rows land at data[]. Note Snipcart spells the identifier property Id with a capital I on this resource only. This is the source node behind the shipping-method picker.

Snipcart: List Subscription Invoices

List every invoice raised against one subscription, with amounts, invoice numbers, the linked order token and whether each was paid. Returns a bare JSON array, so rows land at data[].

Snipcart: List Subscriptions

List subscriptions with plan name, subscriber, billing interval, price, lifetime spend, next billing date and the last invoice outcome. Note the path lives under /dashboard/, unlike the count endpoint. Offset paginated: rows land at data.items[], with data.totalDeclinedCount giving the count of failing subscriptions. This is the source node behind the subscription picker.

Action nodes 19

Snipcart: Add Allowed Domains

Permit one or more extra domains or subdomains to run the cart. The request body is a root-level JSON ARRAY of {domain, protocol} objects. The natural automation is whitelisting a preview deploy's hostname on every build, then removing it when the branch closes.

Snipcart: Archive Product

Archive a product. Snipcart's DELETE on a product sets archived to true rather than removing it: sales history and existing orders keep their reference, and the product reappears in List Products when `archived` is set to "true". It is therefore NOT flagged destructive - but be aware that no endpoint in this API un-archives a product, so the reversal is a dashboard action rather than a second node.

Snipcart: Batch Update Order Statuses

Move many orders to new statuses in one call. The request body is a JSON ARRAY of {id, status} objects, where id is the order token. Use it to mark a day's picking run as Shipped in a single request instead of one PUT per order. Statuses are freely reversible, so this is a reversible write.

Snipcart: Cancel Subscription

DESTRUCTIVE AND IRREVERSIBLE. Ends a shopper's recurring billing relationship, and nothing in this API restarts it - the customer has to subscribe again through checkout. A V1 subscription is cancelled with the payment gateway immediately; a V3 subscription moves to CancellationRequested and stops at the next billing date. Cancelling refunds nothing already collected; use Create Refund separately for that.

Snipcart: Create Discount

Create a discount. Which fields are required depends on the trigger (Code needs a code, Total needs totalToReach, Product needs itemId) and on the type (Rate needs rate, FixedAmount needs amount, Shipping needs shippingCost, AlternatePrice needs alternatePrice). A newly created discount can be deleted or archived, so this is a reversible write.

Snipcart: Create Order Notification

Add a notification or internal comment to an order. WITH delivery_method set to Email OR Bcc THIS SENDS A REAL EMAIL TO THE CUSTOMER, and an email cannot be unsent - leave delivery_method blank or None to record a dashboard-only comment. It moves no money, so it is a reversible write, but treat the Email path as one-way.

Snipcart: Create Refund

DESTRUCTIVE - MOVES REAL MONEY AND CANNOT BE UNDONE. Snipcart's own documentation warns that creating a refund is irreversible and submits the refund to the payment gateway that processed the original order. There is no un-refund endpoint: the funds leave the merchant account on this call, with no second approval step between the node firing and the money moving. Refunds the given amount against an order, optionally refunding taxes proportionally and emailing the customer.

Snipcart: Create Shipping Method

Create a custom shipping method: a named option with tiered rates that can vary by order weight (IN GRAMS) or order total, restricted to countries and provinces and to addresses matching a postal-code pattern. Snipcart states that creating a shipping method ENABLES SHIPPING on the account if it was disabled, which changes what every shopper sees at checkout.

Snipcart: Delete Customer

DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes a customer account, including the login the shopper uses to see their own order history and manage their subscriptions. Snipcart answers 204 with no body and this API offers no way to recreate the record. Use it for genuine erasure requests, not for tidying a list.

Snipcart: Delete Discount

DESTRUCTIVE AND IRREVERSIBLE. Permanently removes a discount; there is no restore. Snipcart REFUSES the delete with HTTP 400 for a discount already used on a completed order and tells you to archive instead - which means the deletes that DO succeed are precisely the ones with no history holding them in place. Prefer Update Discount with archived set to "true", which is reversible.

Snipcart: Delete Shipping Method

DESTRUCTIVE AND IRREVERSIBLE. Snipcart states the shipping method is permanently removed with no recovery, and this is LIVE CHECKOUT CONFIGURATION: delete the only method covering a region and shoppers there can no longer check out. Answers 204 with no body, or 404 if the id does not exist. Recreating it means re-entering the whole rate table by hand.

Snipcart: Import Products From URL

Import products into Snipcart by pointing it at a URL: an HTML page carrying Snipcart's buy-button markup, or a JSON product document. Snipcart fetches the URL and registers every product it finds. Returns a bare JSON array of the imported products, so rows land at data[]. Imported products can be archived afterwards, so this is a reversible write.

Snipcart: Remove Allowed Domains

Stop permitting one or more domains to run the cart. The request body is a root-level JSON ARRAY of {domain} objects; the protocol is not used for matching. Not flagged destructive because Add Allowed Domains puts a domain straight back - but the cart stops working on that host the moment this runs, so never point it at the live storefront.

Snipcart: Update Customer

Update a customer's email and default billing or shipping address. Email is required by Snipcart on this call even when only an address is changing, so read the customer first and pass the existing email back if you are not changing it.

Snipcart: Update Default Domain

Set the account's default domain. HANDLE WITH CARE: this is live checkout configuration, and pointing it at the wrong host stops the cart working on the real storefront until it is set back. It is a reversible write because one further call restores the previous value, so read Get Default Domain first and keep the old value.

Snipcart: Update Discount

Update an existing discount, or ARCHIVE it by setting archived to "true". Archiving is the right way to retire a discount that has already been used, because Snipcart refuses to delete those - and unlike Delete Discount, it can be undone by setting archived back to "false". Only the fields you fill are sent.

Snipcart: Update Order

Update an order: status, payment status, tracking number and URL, customer email, billing or shipping address, internal notes, custom fields and metadata. Only the fields you fill are sent. Setting status to Shipped with a tracking number is the normal fulfilment write. This does NOT move money - use Create Refund for that.

Snipcart: Update Product Inventory

Update a product's INVENTORY only: the management method, the stock count, whether out-of-stock purchases are allowed, and per-variant stock. Snipcart accepts no other fields on this call - price, name and images come from your own catalog markup, not from here. Fully reversible by writing the previous numbers back.

Snipcart: Update Shipping Method

Update a custom shipping method. Snipcart expects the COMPLETE representation on this call, not a patch, so read the method with Get Shipping Method first and send every field back with your changes applied - otherwise omitted fields are cleared. Reversible by writing the previous representation back.

Connecting Snipcart takes one credential

Snipcart authenticates with HTTP Basic where the secret API key is the username and the password is empty. That empty password is a property of the protocol here rather than a choice, and it is the single most common reason a hand-rolled Snipcart client returns 401 on every endpoint: a client that encodes a placeholder password, or drops the separator entirely, produces a header that looks plausible and is rejected. Mattering builds the header from the key alone, so there is no password field to fill in wrongly. Keys are created from your Snipcart dashboard under the account API keys section, and each key is created in Test or Live mode and only reaches its own mode's data. Snipcart's API reference documents no rate limit for the REST API, so this connector claims none. Nothing in Snipcart's API documentation states whether REST access depends on your plan, so confirm that with Snipcart before building a workflow your storefront has to depend on.

1

Sign in to Snipcart, open your account API keys, and decide which mode you want first. A Test key is the safer starting point and exercises the same paths as a Live one.

2

Create a secret API key in that mode and copy the value. Keep the secret key server side: it is a full-access credential for that mode, not the public key your storefront embeds.

3

In Mattering Automations, open Connectors, click Add Connector, choose Snipcart, and create a credential with that key.

4

Click Test Connection. Mattering calls Snipcart's order list endpoint, which is also Snipcart's own documented example request, so a success proves the host, the path and the Basic header in one call. A 401 means the key is wrong or is being used against the other mode's data.

5

All 43 Snipcart nodes appear in the canvas palette. Run Snipcart: List Orders first to confirm you are looking at the environment you expect.

Common uses for the Snipcart MCP

Fulfilment status that moves without a person retyping it

Snipcart: List Orders reads what came in, filtered by status, payment status or date, and Snipcart: Update Order writes the status, tracking number and shipping method back. Snipcart: Batch Update Order Statuses moves a set of orders in one call, which is what a nightly handoff from a warehouse file actually needs. Snipcart: Create Order Notification adds a note against the order, and with the email delivery method it sends a real message to the customer, so a shipped status and the shipping confirmation can be one step apart rather than one system apart.

Refunds with a person in the loop, not a script in the dark

Snipcart: Create Refund is the only node that moves money, and Snipcart documents it as irreversible and submitted straight to the original payment gateway. The pattern worth building is the approval one: a support form or an agent proposes the refund, Snipcart: Get Order and Snipcart: List Order Refunds confirm the amount and that nothing was refunded already, an approval task puts a human between the request and the transfer, and only then does the refund node fire. Rehearse the whole chain with a Test key first, where the refund is placed against dummy payment details and touches no real gateway.

Keep the catalog and stock in step with your source of truth

Snipcart: Import Products From URL loads or refreshes products from a feed, Snipcart: Update Product Inventory adjusts stock levels, and Snipcart: List Products and Snipcart: Get Product read what the store currently believes. A scheduled sweep can compare Snipcart against an ERP, a spreadsheet or a Mattering database and open a task when the two disagree by more than a tolerance. Snipcart: Archive Product is the deliberate name for the delete endpoint, because Snipcart archives rather than deletes and no API call reverses it, so the reversal is a dashboard action.

Abandoned carts, chased on a schedule

Snipcart: List Abandoned Carts returns carts that stopped short, with the shopper email and the cart total, and Snipcart: Get Abandoned Cart opens one up. A workflow can filter for carts above a value threshold, look the shopper up with Snipcart: List Customers to see whether they have ordered before, and route the follow up: an email step for a first time visitor, a task for a sales person on a large basket. The cart list uses a relative time range rather than absolute dates, so a scheduled run naturally reads the recent window.

Discount campaigns that clean up after themselves

Snipcart: Create Discount, Snipcart: Update Discount and Snipcart: List Discounts turn a promotion into a workflow step rather than a calendar reminder: create a code when a campaign starts, and expire or archive it when the campaign ends. One vendor behaviour makes the design obvious in hindsight. Snipcart refuses to delete a discount that has already been used, and points you at archiving instead, so the durable cleanup path is Snipcart: Update Discount with the archived flag rather than Snipcart: Delete Discount, which will succeed only on the codes nobody redeemed.

Watch subscriptions before a churn shows up in a report

Snipcart: List Subscriptions, Snipcart: Get Subscription and Snipcart: List Subscription Invoices read the recurring side of the store, and Snipcart: Count Subscriptions gives a single number a scheduled run can trend. A failed invoice on a subscription is the signal worth acting on the same day: read the state, open a task for the account owner, and let a human decide before Snipcart: Cancel Subscription is ever considered, since nothing in this API restarts a cancelled subscription and it refunds nothing already collected.

Example: A refund that a human approves and an agent prepares

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a support form or an inbound email arrives asking for a refund, carrying an order number or the shopper email.

2

Snipcart: List Orders finds the order by that email or invoice number, and Snipcart: Get Order reads the full record: what was bought, what was paid, and the current payment status.

3

Snipcart: List Order Refunds checks whether a refund already exists on this order, so a duplicate request cannot quietly become a second transfer.

4

A condition compares the requested amount against the order total, and a Mattering task is opened for the store owner with both figures and the order link attached. Nothing has moved yet.

5

On approval, Snipcart: Create Refund submits the refund to the gateway that processed the original payment. This is the irreversible step, which is why every earlier step exists.

6

Snipcart: Create Order Notification records the outcome against the order, and the result is written into a Mattering database so the month's refunds are countable without opening the dashboard.

Snipcart MCP questions, answered

What Snipcart operations are supported?

43 nodes: 24 read nodes and 19 action nodes. Orders (list, get, update, batch status update, digital goods), refunds (list, get, create), order notifications (list, create), customers (list, get, their orders, update, delete), products (list, get, import from a URL, update inventory, archive), discounts (list, get, create, update, delete), abandoned carts (list, get), subscriptions (count, list, get, invoices, cancel), user sessions, shipping methods (list, get, create, update, delete), allowed domains (list, add, remove) and the storefront default domain (get, update). Deliberately not included: Snipcart's browser side JavaScript SDK, which is not a REST surface, and webhook configuration, which Snipcart manages in its dashboard rather than through the REST API.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The read nodes are the comfortable surface to hand an assistant. Keep Snipcart: Create Refund, Snipcart: Cancel Subscription and the three delete nodes behind a condition or an approval task.

Snipcart publishes its own MCP server. Why use this connector?

It does, and for some jobs it is the better answer. Snipcart documents an MCP server of its own, and if what you want is an assistant in your editor answering questions about your store while you work, use it. This connector is built for a different job: unattended operations. These 43 nodes run on a schedule or on a trigger with nobody watching, chain with every other connector in one workflow so a Snipcart order can open a task, write a database row and post to Slack in the same run, hold the credential once in a shared workspace store rather than in each person's local client config, and carry destructive flags so a refund or a cancellation can be gated behind an approval. They are also ordinary canvas steps, not only assistant tools.

Do I need separate credentials for Test and Live?

Yes, and that is the design rather than an inconvenience. A Snipcart secret key is created in Test mode or in Live mode, and Snipcart documents the two environments as isolated: a Test key cannot read Live data and a Live key cannot read Test data. Connect one credential for each and select the right one on the nodes. The practical value is that Test mode is a full second environment rather than a flag, so the whole workflow, including the refund step, can be exercised end to end against dummy payment details before a real card is ever involved. One crossing point exists: the order surfaces accept an include test orders flag that lets a Live key also see Test orders.

Can an AI agent refund a customer by accident?

Snipcart: Create Refund is flagged destructive precisely so you can stop that. Snipcart documents the refund as irreversible and submitted to the payment gateway that processed the original order, and there is no un-refund endpoint. The honest guardrails are structural: keep agents on the read nodes and the status update nodes, put the refund behind a condition or an approval task rather than a bare trigger, and read Snipcart: List Order Refunds first so a repeated request cannot become a second transfer. Snipcart: Cancel Subscription and the three delete nodes carry the same flag for the same reason. Note also that Snipcart: Update Order can set a payment status of refunded, which records a state and does not instruct the gateway, so it is not a substitute for the refund node and does not move money.

What are Snipcart's REST API rate limits?

Snipcart's API documentation publishes none: no requests per minute figure, no rate limit headers and no documented 429 row for the REST API. This connector therefore claims no number. Be careful with the figures that circulate, because they describe something else: the per minute and concurrency limits published in Snipcart's MCP server documentation are limits that server imposes on itself, not limits of the REST API. Build bulk work to be restartable rather than to a threshold nobody published, and prefer Snipcart: Batch Update Order Statuses over a loop of single updates where you can.

Can a workflow start the moment an order is placed?

Not from this connector, which polls rather than listens. There are no trigger nodes here because Snipcart configures webhooks in its dashboard and documents no REST endpoints for managing them, so the connector does not pretend to own that surface. The pattern that works today is a schedule plus Snipcart: List Orders filtered by date or status, which is enough for fulfilment, reconciliation and reporting. If you need same second reaction, point a Snipcart webhook at a Mattering webhook trigger and use these nodes for everything after that first hop.

Why did deleting a discount fail?

Because Snipcart refuses to delete a discount that has already been redeemed and tells you to archive it instead. The awkward part is which discounts that leaves you able to delete: the ones nobody used. So a cleanup automation built only on Snipcart: Delete Discount will fail on exactly the codes that mattered. Use Snipcart: Update Discount with the archived flag as the durable path, and treat the delete node as a tool for codes created in error.

Does this connector work with Snipcart subscriptions?

It reads them and it can cancel them. Snipcart: List Subscriptions, Snipcart: Get Subscription, Snipcart: List Subscription Invoices and Snipcart: Count Subscriptions cover the reporting and monitoring side, and Snipcart: Cancel Subscription is the one write, flagged destructive. One detail decides whether a subscription node finds anything: Snipcart supports two subscription generations, and the identifier is not the same shape in both, so a subscription id from the newer generation passed with the older setting returns a not found rather than an explanation. Each node's description says which value goes where, and the picker fills the field from Snipcart: List Subscriptions so you rarely have to type one.

43 nodes waiting on the canvas

Put Snipcart to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Snipcart is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products