Connecting to our MCP server
CloudPress 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. You add it once in your client, sign in to CloudPress 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 CloudPress workspace. Trial workspaces cannot authorize AI clients or other apps — you'll need to upgrade or create a paid workspace first.
- An AI client that supports remote MCP servers (for example, Claude or OpenAI Codex).
- Your CloudPress brand host. Most people use
my.cloudpress.com. If you sign in at a white-label address (for example,brand.example.com), use that host instead.
How it works
The CloudPress MCP server lives at one URL — https://my.cloudpress.com/mcp — and your
client connects to it directly over the internet. There's nothing to download, and you
don't paste in a token or password: when you add the server, your client sends you to
CloudPress in your browser to sign in and approve access, once.
Use your own brand host
Replace my.cloudpress.com 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 CloudPress as a remote MCP server using the URL above. The exact menu wording depends on your client.
Claude supports CloudPress as a custom connector.
- Open Claude's connector settings and add a custom connector (in current desktop builds, Customize → Connectors → Add custom connector).
- Give it a Name, for example
CloudPress. - Set the Remote MCP server URL to
https://my.cloudpress.com/mcp. - Click Add.
- Open Codex's MCP server settings and add a new server (in current desktop builds, Settings → MCP Servers → Add Server).
- Enter the server URL
https://my.cloudpress.com/mcp. No other fields are needed. - Save.
After you add it, the client prompts you to authenticate with your CloudPress 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 CloudPress
Your client opens a CloudPress page in your browser. Sign in with your normal CloudPress email and password if you aren't already signed in.
This is the standard secure OAuth sign-in: your AI client never sees your password, only the limited access you approve in the next step. See OAuth 2.1 for details.
3. Choose a workspace
CloudPress shows an authorization screen titled Authorize (your client's name), with the prompt "Choose a workspace and review the permissions this application is requesting."
- Under Workspace, open the picker (labeled Choose a workspace…) and select the CloudPress workspace the assistant should act on. The note below the picker confirms the app will be granted access to that one workspace only.
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.
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
Arecord pointingblog.example.comat203.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 writes for site rename and restart, DNS records and zones, CDN caching and cache purge, edge rules, and Shield settings. It can't do any of the following, no matter what you grant: create, delete, or resize a site; place or change orders and billing; run backups and restores; or manage users, accounts, or API keys. For those, use the dashboard or the REST API. The full list of available tools is in the MCP Server reference.
If something goes wrong
Common issues
- The picker shows "No eligible workspace." Only paid workspaces on the brand you signed in to are eligible. 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://my.cloudpress.com/mcpbut 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