Provider REST API
PaymentsConnect Claude to Shopify
Search orders, products, variants, customers and draft orders, and adjust inventory. Toolspoke puts 12 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.
- Connection
- Provider REST API
- Authentication
- Admin API access token
- Actions exposed
- 12
- Cost per call (typical)
- 1 credit
- Adapter
- Maintained by Toolspoke
Connected in three steps
- 1
Install Shopify
Open the marketplace in your workspace, add Shopify to the project your agents work in, and it appears on the gateway immediately.
- 2
Connect the credential
Authenticate with admin api access token. Where to get one, and what it has to be able to reach, is the next section.
- 3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.
.mcp.json{
"mcpServers": {
"toolspoke": {
"type": "http",
"url": "https://toolspoke.com/mcp"
}
}
}One block covers every tool you have installed. Shopify shows up in the client as soon as your policy allows it, and so does everything else you install later.
Where the address goes, per client
- Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp- Claude and Claude Desktop
Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp- Cursor
~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }- Codex
~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"- VS Code
.vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }
What Shopify asks for
Admin API access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- Shop subdomainRequired
- Just the subdomain, without .myshopify.com - if your admin is at my-store.myshopify.com/admin, enter my-store.
- my-store
- Admin API access tokenRequired
- Shopify admin → Settings → Apps and sales channels → Develop apps → your app → API credentials. Tick only the scopes this install needs (read_orders, read_products, read_customers, read_inventory, plus write_products and write_inventory if it should change anything). The token is shown once.
- shpat_…
- API versionOptional
- Admin API version, as YYYY-MM. Leave blank for 2026-07. Shopify supports each version for about a year, so raise this when the current one nears its end of life.
- 2026-07
What Claude can do in Shopify
12 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.
- Reads
- 10Reads
- Writes
- 1Writes
- Destructive
- 1Destructive
Reads
10Fetches data and changes nothing.
shop_infoReturn the store itself: name, myshopify domain, storefront URL, currency, timezone, weight unit and plan. Call it to confirm which store a connection points at and which currency every money amount elsewhere is in. It takes no arguments and is the cheapest call here, which is why it is the connection's health check.
search_ordersSearch orders with Shopify's search syntax and return compact summaries: order name, dates, financial and fulfilment status, total, the customer, and the first twenty line items. The search string is the same one the admin's order search takes - "financial_status:paid fulfillment_status:unfulfilled", "created_at:>2026-08-01", "email:[email protected]", "name:#1001". Call get_order for one order's full detail. Responses are kept out of the audit log because they carry shoppers' personal data.
get_orderFetch one order in full: totals broken down into subtotal, shipping and tax, the shipping address, the customer, every line item with its variant, plus notes, tags and cancellation state. Use it after search_orders when you need to answer a question about a specific order. The id is a global id - gid://shopify/Order/1234567890 - exactly as search_orders returns it. Responses are kept out of the audit log because they carry a shopper's name and address.
list_productsSearch products and return summaries: title, handle, status, type, vendor, tags and total inventory. The search string is the admin's product search - "status:active", "vendor:Acme", "tag:sale", "title:hoodie", "inventory_total:<5". Call get_product for one product's description and its variants, or list_variants when you want variants across many products.
get_productFetch one product with its description, options and up to fifty variants, each with SKU, price and inventory quantity. Call this before update_product so you know the current values, and before adjust_inventory to get a variant's inventoryItem id. The id is a global id - gid://shopify/Product/1234567890 - as list_products returns it.
list_variantsSearch product variants across the whole catalogue and return SKU, price, inventory quantity and the inventoryItem id each one is stocked against. Use this rather than get_product when the question is about stock or SKUs spanning many products - "inventory_quantity:<5", "sku:ACME-*". The inventoryItem id it returns is one of the two ids adjust_inventory needs; the other is a location id.
list_locationsList the store's inventory locations with their ids, names and addresses. Call this before adjust_inventory: a stock change is always against one location, and the location global id is the second of the two ids that mutation requires.
list_customersSearch customers and return name, email, phone, order count and lifetime spend. The search string is the admin's customer search - "email:[email protected]", "country:Germany", "orders_count:>5", "tag:vip". Call get_customer for one customer's detail. This returns other people's personal data, so the response is never written to the audit log.
get_customerFetch one customer: name, contact details, order count, lifetime spend, default address, tags, notes and their most recent order. The id is a global id - gid://shopify/Customer/1234567890 - as list_customers returns it. This returns another person's name, address and contact details, so the response is never written to the audit log.
list_draft_ordersList draft orders - quotes and manually created carts that have not been paid yet - with their status, total, customer and invoice URL. Use it to find quotes waiting on a customer, or to check whether an order was raised manually rather than through the storefront. Draft orders carry shopper details, so the response is never written to the audit log.
Writes
1Creates or updates something on the other side.
update_productUpdate a product's own fields: title, description, handle, type, vendor, tags or publication status. Reversible - every field it can set can be set back, and it does not touch variants, inventory or price, which is why it is a write rather than a destructive action. Only the fields you pass are changed, but `tags` replaces the whole tag list, so read the current tags with get_product first. Setting status to ACTIVE publishes the product to the storefront.
Destructive
1Deletes or permanently alters something. Worth granting on purpose.
adjust_inventoryChange the stock level of one or more inventory items at a location by a relative delta. Destructive because it changes what shoppers can buy the moment it lands - a negative delta can take a product out of stock on the live storefront, and a positive one can oversell it - and because deltas compound: calling it twice applies the change twice, with no idempotency key to stop that. Get inventory_item_id from list_variants or get_product, and location_id from list_locations. Confirm the current inventoryQuantity first, and pass change_from_quantity so Shopify rejects the adjustment if stock moved underneath you.
What it will not do
Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.
- It cannot call anything else
- The 12 actions above are the whole of it. A call to any other name is refused before it reaches Shopify rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
- It reaches no further than your credential
- Toolspoke holds no access to Shopify of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
- It never hears from Shopify
- Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Shopify. An agent has to ask.
- It does not smooth over provider limits
- Toolspoke does not retry, queue or back off around Shopify's own rate limits. A call that Shopify refuses comes back to the agent as a failed call.
Before you connect it
What can Claude do in Shopify?
12 named actions: 10 that only read, 1 that write and 1 that delete or permanently alter something. They include shop_info, search_orders and get_order. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.
What credentials does the Shopify connector need?
Admin API access token. The connector asks for shop subdomain and admin api access token, and optionally api version. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.
Does the Shopify connector work with Cursor and Codex, or only Claude?
Any client that speaks MCP, and every one of them gets the same 12 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.
What does the Shopify connector not do?
The 12 actions above are the whole of it. A call to any other name is refused before it reaches Shopify rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Shopify of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Shopify. An agent has to ask. Toolspoke does not retry, queue or back off around Shopify's own rate limits. A call that Shopify refuses comes back to the agent as a failed call.
Can I limit which actions an agent can call?
Yes, in two places. The project switches Shopify's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.
What gets recorded when an agent calls Shopify?
Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.