You can connect Squarespace to Claude using the Model Context Protocol (MCP), though not for the reason you might expect: Squarespace’s remote MCP server doesn’t touch your site, your pages, or your store — it only searches and generates available domain names. This guide covers what the Squarespace Domains MCP server actually does, how to connect it directly or through a gateway, and why a server named after a full platform is worth checking for scope before you assume it does more than it does.

What the Squarespace Domains MCP server actually does

Squarespace publishes a remote MCP server at mcp.squarespace.com/mcp that does one narrow job: it checks whether a domain name is available and suggests alternatives when it isn’t. Point Claude at it and prompts like these turn into real lookups instead of a guess based on training data:

  • “Is roastedbyyilmaz.com available?”
  • “Give me ten available domain names for a coffee subscription business.”
  • “Is this name available as .com, .co, and .io?”

That’s the whole surface. It doesn’t read or edit a Squarespace site, it doesn’t touch orders, inventory, or billing, and it has no concept of a site you already own — it checks names, nothing else. See the Squarespace server page in gate’s directory for the current tool list and connectivity status.

Why the name is bigger than the tool

Squarespace is a full website builder with pages, a store, billing, and a domain registrar all under one brand — so “Squarespace MCP server” reads like it could mean any of that. In gate’s catalog it’s listed as Squarespace Domains for exactly this reason: the scope is the registrar lookup, not the account. If you were expecting a server that edits your live site, this isn’t it, and as far as gate’s directory tracks, no such server currently exists.

That scoping cuts the other way too, in your favor: because the server only checks public domain availability, there’s no private account data behind it, which is why it skips OAuth entirely. There’s nothing to authorize against — you’re querying the same kind of public registry data a registrar’s own search box would show you, just from inside a chat instead of a browser tab.

Option 1: Connect it to Claude directly

Connecting the Squarespace Domains server on its own takes a couple of steps:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at Squarespace’s documented MCP endpoint at mcp.squarespace.com/mcp.
  • That’s it — no account to sign into before the tools show up.

That’s enough if this is the only extra server you want in Claude. The tradeoff shows up once you add a second server, and then a third, and each one lives in its own entry in your client’s config with no shared view of what’s connected or what it’s allowed to do.

Option 2: Connect it once, through a gateway

If you’re already connecting more than one MCP server or using more than one AI client, wiring each one in directly gets old fast — that’s the connection sprawl covered in what an MCP gateway is. The idea is to connect Squarespace Domains (and everything else you use) to one gateway URL, then point every AI client at that single URL instead of reconfiguring each one separately.

With gate specifically, connecting it looks like this: add gate’s gateway URL to Claude once, then pick Squarespace Domains from the Squarespace server page in the directory. gate’s catalog tracks each server’s currently verified connectivity, so you know before you start whether a server needs OAuth, an API key, or nothing at all. See the full list on the MCP servers page.

What’s worth checking anyway

A no-sign-in, read-only lookup tool is about as low-stakes as an MCP server gets, but the habit of checking still applies, and it’s a useful one to build before you connect a server with real account access:

  • Confirm the domain before you connect. Nothing in MCP stops someone from standing up a server called “Squarespace” that isn’t run by Squarespace. Check the actual endpoint you’re pointing at, not just the label your client shows you — see how to tell a real MCP server from a fake one.
  • A tool description is still worth a glance. Even a narrow, no-auth server has tool descriptions the model reads before deciding what to call — in principle, still a place hidden instructions could live on any server. gate’s free MCP security scanner checks a server’s tool list for prompt injection patterns before you rely on it, no signup required.
  • Don’t assume the name covers the whole product. Before connecting any server whose name matches a platform you use, check what it actually exposes on its directory page rather than assuming from the brand — a registrar lookup and a full site editor carry very different stakes, even under the same name.
Where gate fits: gate’s directory lists each server’s currently verified connectivity — open, key-based, allow-listed, or no-sign-in like this one — along with a plain description of what it actually does, so you know what to expect before you start. Every server is scanned for prompt injection before it goes live, and every call goes into a plain-language log. See the full gateway at /mcp-gateway.

The bottom line

Connecting Squarespace to Claude with MCP is a one-step, no-sign-in setup, direct or through a gateway — but what you get is a domain-name search tool, not a way to manage a Squarespace site. Useful for the specific job of picking a name, and a good reminder that a server’s brand name is not its scope: check the directory page for what a server actually does before you decide it either covers more, or less, than you need.