Squarespace published an official Model Context Protocol server on October 3, 2026. The server lives at https://mcp.squarespace.com/mcp and requires no authentication — no API key, no OAuth flow, no Squarespace account. Any MCP-compatible client (Claude, ChatGPT, Gemini, Claude Code, Cursor) can connect and start calling tools immediately.
This is a notable shift in how SaaS platforms are approaching MCP. Apple's App Store Connect MCP server (covered here) requires authenticated access. Squarespace took the opposite approach: an open, read-only server that anyone can use without signing up.
What the Server Provides
The server exposes two tools and three prompts, all focused on domains:
- domains_generate_names
- Generate brandable domain ideas from a plain-language description. Input: a business, product, campaign, or project description. Output: creative, on-brand suggestions — not keyword permutations. Works from intent ("a ceramics studio in Portland focused on classes") as well as from an established brand name.
- domains_search
- Check real-time availability and pricing for a specific domain or keyword across supported TLDs. Every available result includes current pricing and a direct checkout link.
- Prompt: find_domain
- Guided flow to discover available domains from a concept.
- Prompt: check_domain
- Quick availability check for a specific name.
- Prompt: purchase_domain
- Structured workflow that hands off to a Squarespace checkout link.
Key constraint: The tools are read-only. No tool registers a domain or charges a payment method. Purchases happen only when a user follows a checkout link to squarespace.com and completes the standard checkout flow there.
Why This Matters for MCP
Three things stand out:
1. Zero-friction onboarding
MCP adoption has been slowed by the credential dance — API keys, OAuth apps, service accounts, token rotation. Squarespace removed all of it. The server URL is the only configuration. This lowers the barrier for developers trying MCP for the first time and for end users who just want to ask their assistant to check a domain.
2. A consumer SaaS use case
Most production MCP servers so far target developers (GitHub, Linear, Cloudflare, database access, file systems). Squarespace targets a mainstream consumer workflow: naming and registering a domain. The prompt layer (find_domain, check_domain, purchase_domain) is designed for natural-language interaction, not API integration. This signals MCP moving beyond the developer-tool niche.
3. Read-only as a trust model
The server explicitly declares that tools are read-only and purchases require a human in the loop on Squarespace's site. This is a practical answer to the "agent authorization" question: instead of building fine-grained permissions into the protocol, the server limits itself to safe operations and defers sensitive actions to the platform's existing checkout flow. Expect more servers to adopt this pattern.
How to Connect
Add this to your MCP client configuration:
{
"mcpServers": {
"squarespace": {
"url": "https://mcp.squarespace.com/mcp"
}
}
}
No headers, no environment variables, no command/args — it's a remote HTTP server using the MCP 2026-07-28 stateless spec. Works with the v2 MCP SDK in Claude Code 2.1.271+, the Claude desktop app, and any client that supports remote MCP servers.
Squarespace documents the setup for each client at developers.squarespace.com/mcp/connect-a-client.
What's Missing (and What Might Come Next)
Today the server only covers domains. Squarespace's platform also includes websites, commerce, email campaigns, scheduling, and analytics. If the domain server sees adoption, expect those surfaces to follow — possibly as separate MCP servers (one per product line) or as an expanded tool set.
There's also no webhook or subscription support yet. The 2026-07-28 spec added resources/subscribe and notifications/message, which would let an agent get real-time updates when a domain status changes. That's a natural next step for a domain tool.
The Bigger Picture
Squarespace joins Apple (App Store Connect), Cloudflare (Workers, KV, D1, R2), Stripe (payments), and a growing list of platforms shipping official MCP servers. The pattern is clear: platforms that expose APIs are adding MCP as a first-class interface alongside REST and GraphQL.
For developers building on MCP, this means the tool catalog is expanding horizontally — not just more dev tools, but commerce, content, identity, and now domains. The protocol's value compounds with each server that ships, because every new server makes every MCP client more useful without any client-side changes.
The no-auth, read-only model Squarespace chose may become the default for consumer-facing SaaS. It's the lowest-friction path to adoption, and it sidesteps the hardest authorization questions until the ecosystem has better primitives for them.