Skip to content

Connecting to our MCP server

What this is

SuperSpace runs a Model Context Protocol (MCP) server so an AI assistant — like Claude or OpenAI Codex — can work with your sites, domains, DNS, CDN, and Shield on your behalf, right from a chat. This page walks a newcomer through adding the server, signing in once, and what the assistant can then do.

The MCP server is the same thing your AI client calls when it "uses SuperSpace." You add it once in your client, sign in to SuperSpace in your browser to authorize it, and from then on you can ask the assistant to do things like "list my sites" or "add a DNS record." For the full technical reference, see MCP Server.

Before you start

  • A paid SuperSpace workspace. Trial workspaces cannot authorize AI clients or other apps — you'll need to upgrade or create a paid workspace first.1
  • An AI client that supports remote MCP servers (for example, Claude or OpenAI Codex).
  • Your SuperSpace brand host. Most people use control.superspace.nl. If you sign in at a white-label address (for example, brand.example.com), use that host instead.

How it works

The SuperSpace MCP server lives at one URL — https://control.superspace.nl/mcp — and your client connects to it directly over the internet. There's nothing to download and no config file to edit for modern clients. You don't paste in a token or password: when you add the server, your client sends you to SuperSpace in your browser to sign in and approve access, and the access it's granted is stored for you automatically.
Server URL https://control.superspace.nl/mcp
What to enter Just the URL — no tokens, headers, or passwords up front
How you authorize A browser sign-in and approval, once, after you add the server

Use your own brand host

Replace control.superspace.nl with the host you actually sign in to. White-label brands each have their own address. The /mcp URL must match the brand you sign in to authorize — access is locked to the brand it was granted under.

Steps

1. Add the server in your AI client

Add SuperSpace as a remote MCP server using the URL above. The exact menu wording depends on your client.

Claude supports SuperSpace as a custom connector.

  1. Open Claude's connector settings and add a custom connector (in current desktop builds, Customize → Connectors → Add custom connector).
  2. Give it a Name, for example SuperSpace.
  3. Set the Remote MCP server URL to https://control.superspace.nl/mcp.
  4. Click Add.
  1. Open Codex's MCP server settings and add a new server (in current desktop builds, Settings → MCP Servers → Add Server).
  2. Enter the server URL https://control.superspace.nl/mcp. No other fields are needed.
  3. Save.

After you add it, the client prompts you to authenticate with your SuperSpace account to finish the connection.

Older clients

A few older clients can't talk to a remote MCP server directly and need a small local bridge instead. If yours is one of them, follow Advanced: manual installation in the MCP Server reference.

2. Sign in to SuperSpace

Your client opens a SuperSpace page in your browser. Sign in with your normal SuperSpace email and password if you aren't already signed in.

This is the standard secure OAuth sign-in — the same kind of "Sign in to authorize this app" flow you've seen elsewhere. Your AI client never sees your password; it only receives limited access that you approve in the next step. For the underlying details, see OAuth 2.1.

3. Choose a workspace

SuperSpace shows an authorization screen titled Authorize (your client's name), with the prompt "Choose a workspace and review the permissions this application is requesting."

  1. Under Workspace, open the picker (labeled Choose a workspace…) and select the SuperSpace workspace the assistant should act on. The note below the picker confirms the app will be granted access to that one workspace only.

Only paid workspaces appear here

Only your paid (non-trial) workspaces on the current brand show up in the picker. If you see a No eligible workspace page instead, you don't yet have a paid workspace on this site — upgrade your trial or create a paid workspace, then try again.

4. Review the permissions and authorize

Below the workspace picker, the Permissions list shows exactly what you're granting. The screen lists only the permissions your client asked for, each with a checkbox that starts checked — clear any you don't want the assistant to have. Across all clients, the permissions that can appear are:

Permission What it lets the assistant do
View sites List your sites and read their configuration and metrics
Manage sites Create, modify, and remove sites
View domains List domains and read registration details
Manage domains Register, modify, and remove domains
View DNS List DNS zones and records
Manage DNS Create, modify, and remove DNS zones and records
View billing Read subscriptions and orders — no payment changes

When you're happy with the selection, click Authorize. To back out without granting anything, click Cancel.2

After you authorize, the browser hands control back to your AI client and the connection is live. You can close the tab.

What the assistant can do now

Once connected, you can ask the assistant in plain language and it will use the permissions you granted. A few examples:

  • "List my sites and which one gets the most traffic."
  • "Add an A record pointing blog.example.com at 203.0.113.10."
  • "Rename site abc to Marketing Blog and restart it."
  • "Show my CDN cache hit rate this week, then purge the cache."
  • "What does my latest order include?"

The assistant has broad read access plus a curated set of safe writes — site rename and restart, DNS records and zones, CDN caching and cache purge, edge rules, and Shield settings. A handful of sensitive actions are intentionally off-limits to AI clients no matter what you grant: creating, deleting, or resizing a site; placing or changing orders and billing; backups and restores; and managing users, accounts, or API keys. For those, use the dashboard or the REST API. The full, authoritative list of available tools is in the MCP Server reference.

Writes are protected against accidental repeats

Every change the assistant makes is tagged so that an automatic retry can't accidentally do the same thing twice (for example, creating a record twice). You don't have to do anything — it's handled for you.

If something goes wrong

Common issues

  • The picker won't accept your workspace, or shows "No eligible workspace." Only paid workspaces on the brand you signed in to are eligible. Trial workspaces and workspaces on a different brand are excluded. Upgrade or switch brands and retry.
  • The assistant says it can't do something. You probably didn't grant that permission, or the action isn't available to AI clients at all (see the list above). Reconnect and grant the matching permission, or use the dashboard.
  • Connecting from the wrong address. Access is locked to the brand host you authorized against. If you added https://control.superspace.nl/mcp but sign in elsewhere, use your own brand's host in the URL instead.

Next steps

  • Try a read-only request first, like "list my sites," to confirm the connection
  • Skim the MCP Server reference for the complete list of tools
  • Learn how authorization works under the hood in OAuth 2.1
  • Prefer scripting it yourself? Start with the API Overview

  1. Trial workspaces are blocked from authorizing apps and don't appear in the workspace picker. This is a deliberate safeguard, not a bug. ↩

  2. On the authorization screen the back-out button is labeled Cancel; clicking it denies the request and grants nothing. ↩