Connectors · Commerce
Squarespace Commerce MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Squarespace Commerce and the rest of your systems. It gives your agent 54 Squarespace Commerce actions (25 reads, 21 writes and 8 that wait for a confirmation) and holds the Squarespace Commerce credential itself, so the agent never does. It paces Squarespace Commerce's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "squarespace_commerce.products.list", intent: "check which Squarespace Commerce account is connected"}# Products: list · read · 1 upstream call- 54actionsin one signed file
- 25readlook, never change
- 21writecreate and update
- 8wait for a yesdestructive, confirmed first
Set up
Connect Squarespace Commerce in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Squarespace Commerce.
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
access_tokenSquarespace API key (Settings > Advanced > Developer API keys) or an OAuth access token
account { op: "connections.requirements", service: "squarespace_commerce" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "squarespace_commerce.products.list" }# products: list · read · 1 upstream callcheck { action: "squarespace_commerce.orders.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Squarespace Commerce at a glance
- Sign-in
- Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
- You provide
access_token- Limits we pace to
- 300 calls a minute, per connection
- API covered
- Commerce API (OpenAPI 2; 1.0, v1 and v2 paths)
api.squarespace.com - Built from
- Squarespace Commerce's documentation, read 23 October 2026developers.squarespace.comdevelopers.squarespace.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 25 of 25 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 4, so ask can line Squarespace Commerce up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Squarespace Commerce.
54 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.
- 25readlook, never change
- 21writecreate and update
- 8destructivewait for a confirmation
Store
5425 read · 21 write · 8 destructive
Products: list · Orders: list · Profiles: list · Contacts: list
Top actions
The Squarespace Commerce API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 36 of Squarespace Commerce's 36 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
squarespace_commerce.products.listProducts: list | Retrieves information for products; products can be filtered within a date range and by product type. | read | commerce.product.list112 connectors |
squarespace_commerce.orders.listOrders: list | Retrieves information about all orders. | read | commerce.order.list82 connectors |
squarespace_commerce.profiles.listProfiles: list | Retrieves all profiles; profiles can be filtered and sorted. | read | commerce.customer.list45 connectors |
squarespace_commerce.contacts.listContacts: list | Returns a paginated list of contacts for the website. | read | crm.contact.list177 connectors |
squarespace_commerce.orders.createOrders: create | Creates an order using information from a third-party sales channel. | write | commerce.order.create67 connectors |
squarespace_commerce.products.getProducts: get | Retrieves information for specific products, including information for any variants or images. | read | commerce.product.get112 connectors |
squarespace_commerce.products.deleteProducts: delete | Delete specified product Squarespace Commerce API `DELETE /v2/commerce/products/{productId}` (`deleteProduct`). | destructive | commerce.product.delete80 connectors |
squarespace_commerce.profiles.getProfiles: get | Retrieves information for specific profiles. | read | commerce.customer.get45 connectors |
squarespace_commerce.contacts.createContacts: create | Creates a new contact. | write | crm.contact.create161 connectors |
squarespace_commerce.inventory.listInventory: list | Retrieves real-time stock information for all product variants. | read | commerce.inventory_item.list7 connectors |
squarespace_commerce.inventory.adjustInventory: adjust | Adjusts stock quantities for product variants. | write | commerce.inventory_adjustment.create7 connectors |
squarespace_commerce.orders.fulfillOrders: fulfill | Updates the status of a specific order to fulfilled, with options to include shipment information and send a customer notification. | write | commerce.fulfillment_order.create5 connectors |
Try it
Prompts to paste into Claude.
Each one names the Squarespace Commerce actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Which Squarespace Commerce orders from the last seven days are still unfulfilled?
calls
squarespace_commerce.orders.list - Writewrite
Orders: create in Squarespace Commerce. Show me exactly what you will send before you save it.
calls
squarespace_commerce.orders.create - Across systemsread
Which contacts are in both Squarespace Commerce and HaloPSA, and how many are in only one of them?
calls
squarespace_commerce.contacts.listhalopsa.users.list
Across your systems
Squarespace Commerce, joined to the rest of your business.
One ask fetches from Squarespace Commerce and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.
Which contacts are in both Squarespace Commerce and HaloPSA, and how many are in only one of them?
squarespace_commerce.contacts.list+halopsa.users.list, oncrm.contact· HaloPSAWhich contacts are in both Squarespace Commerce and NetSuite, and how many are in only one of them?
squarespace_commerce.contacts.list+netsuite.views.contacts, oncrm.contact· NetSuite
crm.contact 192commerce.product 109commerce.order 86commerce.customer 51ask { intent: "which contacts are in both Squarespace Commerce and HaloPSA, and how many are in only one of them", steps: [ { action: "squarespace_commerce.contacts.list", as: "people", input: {}, limit: 100, max_pages: 5 }, { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 }, { join: { left: "people", right: "people2", on: "crm.contact", group_by: "people.email", select: ["people.email", "count(people2.id) as in_halopsa"] } } ]}Governance for Squarespace Commerce
Destructive actions wait for a yes.
8 Squarespace Commerce actions are destructive. These are all of them:
- Products: delete
squarespace_commerce.products.delete - Contacts: delete
squarespace_commerce.contacts.delete - Discounts: delete
squarespace_commerce.discounts.delete - Product variants: delete
squarespace_commerce.product_variants.delete - Product images: delete
squarespace_commerce.product_images.delete - Webhook subscriptions: delete
squarespace_commerce.webhook_subscriptions.delete - Address book: delete
squarespace_commerce.address_book.delete - Webhook subscriptions: rotate secret
squarespace_commerce.webhook_subscriptions.rotate_secret
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Products: delete?
intent: the user asked me to products: delete
account { op: "keys.create", name: "squarespace-commerce-agent", allowed_actions: ["squarespace_commerce.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "squarespace_commerce.products.delete", approver: "[email protected]" }, { match: "squarespace_commerce.contacts.delete", approver: "[email protected]" }, { match: "squarespace_commerce.discounts.delete", approver: "[email protected]" } ]}Cost
What Squarespace Commerce costs on actionlake.
Every Squarespace Commerce action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Squarespace Commerce refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 54 Squarespace Commerce actions
- 8actions pageeach page of a long list is one call
- 25reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Squarespace Commerce action.
54 actions by area: the id your agent calls, what it does, and its effect.
Store54
squarespace_commerce.address_book.createAddress book: createwritesquarespace_commerce.address_book.deleteAddress book: deletedestructivesquarespace_commerce.address_book.getAddress book: getreadsquarespace_commerce.address_book.listAddress book: listreadsquarespace_commerce.address_book.updateAddress book: updatewritesquarespace_commerce.analytics.transaction_summariesAnalytics: transaction summariesreadsquarespace_commerce.authorization.memberAuthorization: memberreadsquarespace_commerce.authorization.websiteAuthorization: websitereadsquarespace_commerce.contacts.createContacts: createwritesquarespace_commerce.contacts.deleteContacts: deletedestructivesquarespace_commerce.contacts.getContacts: getreadsquarespace_commerce.contacts.listContacts: listreadsquarespace_commerce.contacts.queryContacts: queryreadsquarespace_commerce.contacts.updateContacts: updatewritesquarespace_commerce.discounts.createDiscounts: createwritesquarespace_commerce.discounts.deleteDiscounts: deletedestructivesquarespace_commerce.discounts.getDiscounts: getreadsquarespace_commerce.discounts.listDiscounts: listreadsquarespace_commerce.discounts.updateDiscounts: updatewritesquarespace_commerce.fulfillment_options.listFulfillment options: listreadsquarespace_commerce.inventory.adjustInventory: adjustwritesquarespace_commerce.inventory.getInventory: getreadsquarespace_commerce.inventory.listInventory: listreadsquarespace_commerce.orders.createOrders: createwritesquarespace_commerce.orders.fulfillOrders: fulfillwritesquarespace_commerce.orders.getOrders: getreadsquarespace_commerce.orders.listOrders: listreadsquarespace_commerce.product_images.deleteProduct images: deletedestructivesquarespace_commerce.product_images.get_statusProduct images: get statusreadsquarespace_commerce.product_images.reorderProduct images: reorderwritesquarespace_commerce.product_images.updateProduct images: updatewritesquarespace_commerce.product_variants.createProduct variants: createwritesquarespace_commerce.product_variants.deleteProduct variants: deletedestructivesquarespace_commerce.product_variants.set_imageProduct variants: set imagewritesquarespace_commerce.product_variants.updateProduct variants: updatewritesquarespace_commerce.products.create_gift_cardProducts: create gift cardwritesquarespace_commerce.products.create_physicalProducts: create physicalwritesquarespace_commerce.products.create_serviceProducts: create servicewritesquarespace_commerce.products.deleteProducts: deletedestructivesquarespace_commerce.products.getProducts: getreadsquarespace_commerce.products.listProducts: listreadsquarespace_commerce.products.updateProducts: updatewritesquarespace_commerce.profiles.getProfiles: getreadsquarespace_commerce.profiles.listProfiles: listreadsquarespace_commerce.store_pages.listStore pages: listreadsquarespace_commerce.transactions.getTransactions: getreadsquarespace_commerce.transactions.listTransactions: listreadsquarespace_commerce.webhook_subscriptions.createWebhook subscriptions: createwritesquarespace_commerce.webhook_subscriptions.deleteWebhook subscriptions: deletedestructivesquarespace_commerce.webhook_subscriptions.getWebhook subscriptions: getreadsquarespace_commerce.webhook_subscriptions.listWebhook subscriptions: listreadsquarespace_commerce.webhook_subscriptions.rotate_secretWebhook subscriptions: rotate secretdestructivesquarespace_commerce.webhook_subscriptions.send_testWebhook subscriptions: send testwritesquarespace_commerce.webhook_subscriptions.updateWebhook subscriptions: updatewrite
Questions
The Squarespace Commerce MCP server, answered.
Is there a Squarespace Commerce MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 54 Squarespace Commerce actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Squarespace Commerce.
What do I need to connect Squarespace Commerce?
Squarespace API key (Settings > Advanced > Developer API keys) or an OAuth access token. The free call account { op: "connections.requirements", service: "squarespace_commerce" } lists exactly what to paste.
Can an AI agent delete or change things in Squarespace Commerce?
Only if its key allows it, and only with an explicit confirmation. 8 Squarespace Commerce actions are destructive, including products: delete, contacts: delete and discounts: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Squarespace Commerce API limit?
actionlake paces every call to the limits in the Squarespace Commerce service file: 300 calls a minute per connection. Repeated reads are answered from cache (25 Squarespace Commerce actions can be), which never reaches Squarespace Commerce.
What does a Squarespace Commerce action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (8 Squarespace Commerce actions page). Cache hits, searches, dry runs and calls Squarespace Commerce refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Squarespace Commerce API does it cover?
The Commerce API (OpenAPI 2; 1.0, v1 and v2 paths) at api.squarespace.com. It is built from Squarespace Commerce's documentation as read on 23 October 2026. 54 actions in 1 area, each one in the signed service file (version 1.0.0).
Can I combine Squarespace Commerce with my other systems?
Yes. ask joins Squarespace Commerce to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Squarespace Commerce maps crm.contact, which 192 other connectors also map.
Does actionlake keep my Squarespace Commerce data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Squarespace Commerce credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Squarespace Commerce today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.