Summary
Squarespace Commerce APIs for one site: orders and fulfillment with tracking, inventory levels and stock adjustments, products and variants, customer profiles and contacts, and financial transactions. API key bearer.
Guided setup
Connect Squarespace Commerce to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Squarespace Commerce in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Squarespace Commerce
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Squarespace Commerce, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Squarespace Commerce + Microsoft Copilot
Squarespace Commerce APIs for one site: orders and fulfillment with tracking, inventory levels and stock adjustments, products and variants, customer profiles and contacts, and financial transactions. API key bearer.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
SQUARESPACE_API_KEY
Step 1 — Get credentials
Setting up takes about 3 minutes.
- Log in to the Squarespace site. In the left navigation open Settings, scroll to Advanced and click Developer API Keys. API keys need a Commerce Advanced plan.
- Click Generate key, name it, and choose the permissions: Orders (Read and Write to fulfill), Inventory (Read and Write to change stock), Products (Read Only), Profiles, Contacts and Transactions (Read Only).
- Copy the key into
SQUARESPACE_API_KEY. Squarespace shows it only once; it does not expire while the site is active.
Every call carries Authorization: Bearer with the key and a User-Agent header, which Squarespace requires.
Where to start: squarespace_commerce_get_website to confirm the site, then squarespace_commerce_list_orders with fulfillment_status PENDING for orders to ship.
Orders: squarespace_commerce_list_orders, squarespace_commerce_get_order, and squarespace_commerce_fulfill_order (adds shipments with tracking and marks the order fulfilled; can email the customer). Use the order id in calls; orderNumber is what the customer sees. Refunds and cancellations are not part of the API.
Inventory: squarespace_commerce_list_inventory, squarespace_commerce_get_inventory, squarespace_commerce_adjust_inventory. Every adjustment needs a fresh idempotency_key (a UUID): resending the same key does nothing, which makes retries safe.
Products: squarespace_commerce_list_products and squarespace_commerce_get_products (Products API v2: types PHYSICAL, SERVICE, GIFT_CARD and DIGITAL; prices and stock on each variant). Product changes are not included.
People: squarespace_commerce_list_contacts, squarespace_commerce_search_contacts, squarespace_commerce_get_contact (Contacts API) and the older squarespace_commerce_list_profiles, squarespace_commerce_get_profiles (Profiles API, in maintenance mode but still the one with order totals per customer).
Money: squarespace_commerce_list_transactions and squarespace_commerce_get_transactions read payments, refunds and fees per order or donation; nothing here moves money.
Paging and dates: lists return up to 50 records with pagination.hasNextPage and pagination.nextPageCursor; pass the cursor alone to get the next page. modified_after and modified_before must be given together and are UTC ISO 8601. Money values are objects with currency and value (a decimal string). Get-by-id tools take up to 50 ids separated by commas.
Rate limit: 300 requests per minute per key; above that Squarespace answers 429 and blocks the key for one minute.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Squarespace Commercetools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
squarespace_commerce_get_website | Read basic information about the Squarespace site the API key belongs to: id, siteTitle, url, timeZone, currency, language and location.… |
squarespace_commerce_list_orders | List orders, most recently modified first, 50 per page: id, orderNumber, createdOn, modifiedOn, channel, customerEmail, customerId… |
squarespace_commerce_get_order | Read one order by id: the same fields as squarespace_commerce_list_orders, with all line items, discounts, internal notes and fulfillments |
squarespace_commerce_fulfill_order | Mark an order as fulfilled and add shipments with ship date, carrier, service, tracking number and tracking URL. should_send_notification… |
squarespace_commerce_list_inventory | List stock for all product variants, 50 per page: variantId, sku, descriptor (product name and options), isUnlimited and quantity. Next… |
squarespace_commerce_get_inventory | Read real-time stock of specific variants: variantId, sku, descriptor, isUnlimited and quantity |
squarespace_commerce_adjust_inventory | Change stock of variants in one call: increment or decrement by a quantity, set a finite quantity, or make variants unlimited. Needs a… |
squarespace_commerce_list_products | List products, 50 per page: id, type (PHYSICAL, SERVICE, GIFT_CARD, DIGITAL), storePageId, name, description, url, urlSlug, tags… |
squarespace_commerce_get_products | Read up to 50 products by id with their variants, pricing, stock, attributes and images |
squarespace_commerce_list_profiles | List profiles (customers, mailing list subscribers, donors), 50 per page: id, firstName, lastName, email, hasAccount, isCustomer… |
squarespace_commerce_get_profiles | Read up to 50 profiles by id: names, email, address, marketing consent and transactionsSummary |
squarespace_commerce_list_contacts | List contacts (the successor of profiles): id, firstName, lastName, email, phone, createdOn, defaultShippingAddress and marketing… |
squarespace_commerce_search_contacts | Search contacts by name or email text, sorted as asked: the same fields as squarespace_commerce_list_contacts. Read-only although it is a… |
squarespace_commerce_get_contact | Read one contact: names, email, phone, addresses and marketing preferences |
squarespace_commerce_list_transactions | List financial transactions grouped per order or donation (a document), 50 per page: id, createdOn, modifiedOn, customerEmail, salesOrderId… |
squarespace_commerce_get_transactions | Read up to 50 transaction documents by id, with payments, refunds, fees and line items. Read-only |
Example prompts
- "Which Squarespace orders are still waiting to be fulfilled?"
- "Fulfil order 1047 with USPS tracking 9400111899223197428490 and email the customer."
- "Which products have fewer than 5 units in stock?"
- "Add 20 units to the stock of the variant SKU MUG-WHT-12."
- "Show last month's transactions and the total processing fees."
FAQ
Which plan does it need? Squarespace Developer API keys need the Commerce Advanced plan. Generate a key under Settings, Advanced, Developer API Keys with the permissions you need; it is shown once.
What does it cover? One Squarespace site: orders and fulfillment with tracking, inventory and stock adjustments, products and variants (read), customer profiles and contacts, and financial transactions.
Which tools install switched off? None. Products are read-only, and fulfilling orders or changing stock is shown to you before it runs.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?