squarespace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQUARESPACE_API_KEY | Yes | The Squarespace API key for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List store products (Products v2; up to 50 per page). Use to browse the catalog. Filter with |
| get_productA | Retrieve product(s) by id (Products v2). Accepts a single id, or a comma-separated list of up to 50 ids to fetch several at once. Use when you already know the id(s). |
| list_inventoryA | List inventory items (stock levels) across variants, 50 per page. Use to audit stock. Page forward with |
| get_inventoryA | Retrieve inventory for specific variants (up to 50 ids per call). Use when you know exact variant ids and want their current stock. |
| list_ordersA | List store orders (up to 50 per page, newest-modified first). Filter with |
| get_orderA | Retrieve a single order by its id, including line items and totals. |
| list_transactionsA | List financial transactions for orders and donations (50 per page). Bound the window with |
| list_profilesA | List customer profiles (contacts/customers), 50 per page. Page forward with |
| get_profileA | Retrieve a single customer profile by its id. |
| adjust_inventoryA | MUTATES THE LIVE STORE. Set a variant's stock to an exact This overwrites the current stock level for |
| fulfill_orderA | MUTATES THE LIVE STORE. Mark an order fulfilled with shipment details.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clear, distinct purpose. The list/get pairs (e.g., list_products vs get_product) are differentiated by whether you're browsing with filters or fetching known IDs, and the two mutations (adjust_inventory, fulfill_order) are unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case: list_* and get_* for reads, adjust_inventory and fulfill_order for writes. The naming is predictable and easy to navigate.
At 11 tools, the server is well-scoped for an e-commerce operations context. It covers the major resources (transactions, products, inventory, orders, profiles) without unnecessary duplication or bloat.
The read surface is strong with list/get for all core resources, and the mutations cover inventory adjustment and order fulfillment. However, there are notable gaps: no create/update/delete for products or orders, no order cancellation, and no profile management operations.