Connect your own coding agent with Studio
Let Claude Code or another MCP client work on one of your websites, on its staging copy, with a connector you can revoke at any time.
Studio lets your own coding agent, such as Claude Code or any client that speaks MCP, work on one of your websites. You bring the agent and choose the model; the control panel gives it a connector that reaches that one site and nothing else in your account.
What the agent can and cannot do
- It can read the site's details, its health diagnosis, its recent events and its DNS records.
- It works on files only on a staging copy of the site. It cannot list, read or change the live site's files.
- Changing files needs a plan that includes building with the assistant. Without it, the agent can read but not write.
- It cannot publish. Going live is a button a person presses in the control panel.
So before you start, make a staging copy of the site. For WordPress, see Make a WordPress staging copy. For other sites, use Create a staging copy on the site's Advanced tab.
Create a connector
- In your control panel, select My sites, then the website.
- Open the Studio tab.
- Under What will hold it, give the connector a name, for example "Claude Code on my laptop".
- Under Stops working after, choose 30 days, 90 days or a year.
- Select Connect a coding agent.
- Copy the token now. It is only shown once.
The card then shows the MCP server address, the token, and a ready-made command for Claude Code.
Connect Claude Code
Paste the command the card gives you into your terminal. It starts with claude mcp add --transport http and carries the address and the token.
Connect another agent
Any agent that can send a request header can connect. Add the MCP server address the card shows, and send the header Authorization: Bearer <token> with your token.
Connect Claude Desktop or claude.ai
These do not take a pasted token.
- In Claude, add a custom connector with your control panel's address followed by
/v1/mcp. - Sign in to your control panel when it asks.
- Choose the site to approve.
This makes a connector too, listed on the Studio tab like the others. This way of connecting is new, so tell us through Support if your client has trouble.
Going live
When the work on the staging copy is ready:
- On a WordPress site, open the live site's Apps tab and select Push back to production. It shows what would change and snapshots the live site first. It needs backups turned on for the live site.
- The other way to put files live is the site's git remote. See Deploy your site with git.
Revoke a connector
On the Studio tab, select Revoke beside the connector. The agent using it is refused from its next request. Do this straight away if a laptop is lost.
The list also shows when each connector was made, when it was last used, and when it expires.
Related
More in Websites
- Install WordPress or another application in one click
Put WordPress, Joomla, Ghost, Wiki.js, NodeBB or Flarum on your website, with its database and first admin account made for you.
- Upload and manage your website's files
Upload, edit and download your site's files in the file manager, or connect with SFTP, FTP over TLS or SSH.
- Restore a backup, a single file, or something you deleted
Turn on backups for a website, take one before a risky change, and bring back the whole site, one file, a database or a deleted site.
- Change your site's PHP version and settings
Choose the PHP version each website runs, and raise limits such as upload size and memory for one site.

