For AI agents

Paste one prompt. It's live.

Your agent already knows how to build the site. These are the words that get it onto your own domain, on UK hosting, with rollback if it gets something wrong.

Prompts

Copy, paste, done

Pick your agent. Each prompt points it at our docs, which are plain Markdown written for agents to read.

Claude Code

Works over SSH or our MCP server. Paste this in the folder with your site. About Claude Code (opens in a new tab)

Prompt
Deploy this site to clicked.cloud. Read https://clicked.cloud/docs/quickstart.md and follow it. Build the site, deploy the output to my site, check it loads, and tell me the live URL.

Cursor

Use Agent mode. Connect our MCP server first (below), then paste this. About Cursor (opens in a new tab)

Prompt
Use the clicked MCP server to deploy this project. Docs: https://clicked.cloud/docs/mcp.md. After adding my SSH key, build it, deploy the build folder as a new release, make it live, and give me the URL.

Codex

Codex can run our CLI in your terminal. Paste this in the project. About Codex (opens in a new tab)

Prompt
Deploy this site to clicked.cloud with the clicked CLI. Read https://clicked.cloud/docs/cli.md first. Run the build, then deploy the output folder, and tell me the live URL when it's done.
Step 1 · SSH key

Let your agent in, and only your agent

An SSH key is a pair of files: a private half that stays on your computer, and a public half you paste into your dashboard. Your agent uses it to deploy. Only the sites you add it to can be reached.

  1. Run the lines on the right (they reuse your usual key if you have one), or ask your agent to do it.
  2. In your dashboard, open the site, then SSH keys → Add a key, and paste the line that starts with ssh-ed25519.
  3. Wait 7 to 10 minutes while it reaches the server. The key shows active when it's ready.
Terminal
cat ~/.ssh/id_ed25519.pub 2>/dev/null || ssh-keygen -t ed25519 -C "clicked.cloud" -f ~/.ssh/id_ed25519
cat ~/.ssh/id_ed25519.pub
Or ask your agent
Use my existing ~/.ssh/id_ed25519.pub, or make one there (type ed25519) if I don't have one, then print the public key so I can paste it into my clicked.cloud dashboard.
Step 2 · MCP server

Or give it our tools directly

Our MCP server lets your agent deploy, roll back, search domains and edit DNS. Give your app the address https://clicked.cloud/mcp and it opens our sign-in page: you use the link we email you and click Allow. There's no token to copy, and you can disconnect it any time under Account → Security. In Claude on the web it's a custom connector; step-by-step pictures here.

Prefer a terminal? Our clicked command installs straight from this site (it needs Node.js, no accounts) and signs in the same way.

Agents can't cancel, delete a site or move a domain away. Those stay with you.

Claude Code
claude mcp add --transport http --scope user clicked https://clicked.cloud/mcp
Cursor · .cursor/mcp.json
{
  "mcpServers": {
    "clicked": { "url": "https://clicked.cloud/mcp" }
  }
}
Codex
codex mcp add clicked --url https://clicked.cloud/mcp
codex mcp login clicked
The clicked command
npm install -g https://clicked.cloud/cli/clicked-0.1.0.tgz
clicked login
How deploys work

Every deploy is a release you can undo

Each deploy goes into its own folder, named by the time it was made. Going live points your site at the new folder; rolling back points it at the last one. Nothing is overwritten.

Deploy
clicked deploy ./out --site hartleysbakes.co.uk
Changed your mind
clicked rollback --site hartleysbakes.co.uk
Docs for agents

Plain Markdown, made to be read by machines

Point your agent at any of these. People can read them too.

Domains

Need a domain for it?

.co.uk, .com, .london, .studio or any of 448 endings, registered in your name.