--- title: "Squarespace Commerce MCP server for AI agents - actionlake" description: "Give Claude 54 Squarespace Commerce actions through one MCP server: products, orders. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/squarespace-commerce updated: 2026-10-23 --- 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. [Connect Squarespace Commerce free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 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/mcp` the first call ``` do { action: "squarespace_commerce.products.list", intent: "check which Squarespace Commerce account is connected" } # Products: list · read · 1 upstream call ``` - 54 actions in one signed file - 25 read look, never change - 21 write create and update - 8 wait for a yes destructive, confirmed first Set up ## Connect Squarespace Commerce in three steps. 1. 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` 2. 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_token` Squarespace 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 ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "squarespace_commerce.products.list" } # products: list · read · 1 upstream call check { 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 2026[developers.squarespace.com](https://developers.squarespace.com/commerce-apis/latest/schema-processor-version-version-latest.json) [developers.squarespace.com](https://developers.squarespace.com/commerce-apis/overview) **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. - **25** read look, never change - **21** write create and update - **8** destructive wait for a confirmation 1. ### Store 54 25 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.list` Products: list | Retrieves information for products; products can be filtered within a date range and by product type. | read | `commerce.product.list` 112 connectors | | `squarespace_commerce.orders.list` Orders: list | Retrieves information about all orders. | read | `commerce.order.list` 82 connectors | | `squarespace_commerce.profiles.list` Profiles: list | Retrieves all profiles; profiles can be filtered and sorted. | read | `commerce.customer.list` 45 connectors | | `squarespace_commerce.contacts.list` Contacts: list | Returns a paginated list of contacts for the website. | read | `crm.contact.list` 177 connectors | | `squarespace_commerce.orders.create` Orders: create | Creates an order using information from a third-party sales channel. | write | `commerce.order.create` 67 connectors | | `squarespace_commerce.products.get` Products: get | Retrieves information for specific products, including information for any variants or images. | read | `commerce.product.get` 112 connectors | | `squarespace_commerce.products.delete` Products: delete | Delete specified product Squarespace Commerce API `DELETE /v2/commerce/products/{productId}` (`deleteProduct`). | destructive | `commerce.product.delete` 80 connectors | | `squarespace_commerce.profiles.get` Profiles: get | Retrieves information for specific profiles. | read | `commerce.customer.get` 45 connectors | | `squarespace_commerce.contacts.create` Contacts: create | Creates a new contact. | write | `crm.contact.create` 161 connectors | | `squarespace_commerce.inventory.list` Inventory: list | Retrieves real-time stock information for all product variants. | read | `commerce.inventory_item.list` 7 connectors | | `squarespace_commerce.inventory.adjust` Inventory: adjust | Adjusts stock quantities for product variants. | write | `commerce.inventory_adjustment.create` 7 connectors | | `squarespace_commerce.orders.fulfill` Orders: 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.create` 5 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. 1. Read read Which Squarespace Commerce orders from the last seven days are still unfulfilled? calls `squarespace_commerce.orders.list` 2. Write write Orders: create in Squarespace Commerce. Show me exactly what you will send before you save it. calls `squarespace_commerce.orders.create` 3. Across systems read Which contacts are in both Squarespace Commerce and HaloPSA, and how many are in only one of them? calls `squarespace_commerce.contacts.list` `halopsa.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`, on `crm.contact` · [HaloPSA](https://actionlake.com/connectors/halopsa) - Which contacts are in both Squarespace Commerce and NetSuite, and how many are in only one of them? `squarespace_commerce.contacts.list` + `netsuite.views.contacts`, on `crm.contact` · [NetSuite](https://actionlake.com/connectors/netsuite) Also mapped by other connectors `crm.contact` **192** `commerce.product` **109** `commerce.order` **86** `commerce.customer` **51** ask ``` ask { 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"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. 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. do squarespace_commerce.products.delete confirm_policy: **human** Products: delete? **intent:** the user asked me to products: delete run suspended · waiting for a named person · key _squarespace-commerce-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` 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: "lead@example.com" }, { match: "squarespace_commerce.contacts.delete", approver: "lead@example.com" }, { match: "squarespace_commerce.discounts.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Squarespace Commerce only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. 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. - 1 upstream call per action all 54 Squarespace Commerce actions - 8 actions page each page of a long list is one call - 25 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Squarespace Commerce action. 54 actions by area: the id your agent calls, what it does, and its effect. **Store 54** - `squarespace_commerce.address_book.create` Address book: create write - `squarespace_commerce.address_book.delete` Address book: delete destructive - `squarespace_commerce.address_book.get` Address book: get read - `squarespace_commerce.address_book.list` Address book: list read - `squarespace_commerce.address_book.update` Address book: update write - `squarespace_commerce.analytics.transaction_summaries` Analytics: transaction summaries read - `squarespace_commerce.authorization.member` Authorization: member read - `squarespace_commerce.authorization.website` Authorization: website read - `squarespace_commerce.contacts.create` Contacts: create write - `squarespace_commerce.contacts.delete` Contacts: delete destructive - `squarespace_commerce.contacts.get` Contacts: get read - `squarespace_commerce.contacts.list` Contacts: list read - `squarespace_commerce.contacts.query` Contacts: query read - `squarespace_commerce.contacts.update` Contacts: update write - `squarespace_commerce.discounts.create` Discounts: create write - `squarespace_commerce.discounts.delete` Discounts: delete destructive - `squarespace_commerce.discounts.get` Discounts: get read - `squarespace_commerce.discounts.list` Discounts: list read - `squarespace_commerce.discounts.update` Discounts: update write - `squarespace_commerce.fulfillment_options.list` Fulfillment options: list read - `squarespace_commerce.inventory.adjust` Inventory: adjust write - `squarespace_commerce.inventory.get` Inventory: get read - `squarespace_commerce.inventory.list` Inventory: list read - `squarespace_commerce.orders.create` Orders: create write - `squarespace_commerce.orders.fulfill` Orders: fulfill write - `squarespace_commerce.orders.get` Orders: get read - `squarespace_commerce.orders.list` Orders: list read - `squarespace_commerce.product_images.delete` Product images: delete destructive - `squarespace_commerce.product_images.get_status` Product images: get status read - `squarespace_commerce.product_images.reorder` Product images: reorder write - `squarespace_commerce.product_images.update` Product images: update write - `squarespace_commerce.product_variants.create` Product variants: create write - `squarespace_commerce.product_variants.delete` Product variants: delete destructive - `squarespace_commerce.product_variants.set_image` Product variants: set image write - `squarespace_commerce.product_variants.update` Product variants: update write - `squarespace_commerce.products.create_gift_card` Products: create gift card write - `squarespace_commerce.products.create_physical` Products: create physical write - `squarespace_commerce.products.create_service` Products: create service write - `squarespace_commerce.products.delete` Products: delete destructive - `squarespace_commerce.products.get` Products: get read - `squarespace_commerce.products.list` Products: list read - `squarespace_commerce.products.update` Products: update write - `squarespace_commerce.profiles.get` Profiles: get read - `squarespace_commerce.profiles.list` Profiles: list read - `squarespace_commerce.store_pages.list` Store pages: list read - `squarespace_commerce.transactions.get` Transactions: get read - `squarespace_commerce.transactions.list` Transactions: list read - `squarespace_commerce.webhook_subscriptions.create` Webhook subscriptions: create write - `squarespace_commerce.webhook_subscriptions.delete` Webhook subscriptions: delete destructive - `squarespace_commerce.webhook_subscriptions.get` Webhook subscriptions: get read - `squarespace_commerce.webhook_subscriptions.list` Webhook subscriptions: list read - `squarespace_commerce.webhook_subscriptions.rotate_secret` Webhook subscriptions: rotate secret destructive - `squarespace_commerce.webhook_subscriptions.send_test` Webhook subscriptions: send test write - `squarespace_commerce.webhook_subscriptions.update` Webhook subscriptions: update write 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. ## More connectors like Squarespace Commerce Shares the most action names with - [Recharge 19](https://actionlake.com/connectors/recharge) - [ShipBob 14](https://actionlake.com/connectors/shipbob) - [Flipdish 12](https://actionlake.com/connectors/flipdish) - [Adobe Commerce 12](https://actionlake.com/connectors/adobe-commerce) - [Easyship 10](https://actionlake.com/connectors/easyship) - [Thinkific 9](https://actionlake.com/connectors/thinkific) Joins with, on shared entities - [HaloPSA 3](https://actionlake.com/connectors/halopsa) - [Salesforce Sales Cloud 3](https://actionlake.com/connectors/salesforce-sales-cloud) - [SAP S/4HANA Cloud Public Edition 3](https://actionlake.com/connectors/sap-s-4hana-cloud-public-edition) - [Acumatica Cloud ERP 3](https://actionlake.com/connectors/acumatica-cloud-erp) - [Odoo 3](https://actionlake.com/connectors/odoo) - [ERPNext (Frappe) 3](https://actionlake.com/connectors/erpnext-frappe) Browse - [All Commerce connectors](https://actionlake.com/connectors/category/commerce) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Squarespace Commerce; the name is the vendor's own. Counts are from the Squarespace Commerce service file, version 1.0.0. ## Give your agent Squarespace Commerce today. [Connect Squarespace Commerce free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/squarespace-commerce More: https://actionlake.com/llms.txt