cloud71
Docs

Connect cloud71 to your AI

cloud71 has a remote MCP connector, so you can publish and manage your sites from inside Claude, ChatGPT, a coding agent, or any AI app that speaks the Model Context Protocol. Connect once, say “publish this,” and get back a live link.

Connector URL

https://mcp.cloud71.host/mcp

That’s all most clients need — sign-in is OAuth, so there are no API keys to copy. Older clients that only support SSE can use https://mcp.cloud71.host/sse.

Before you start

You need a cloud71 account — the connector deploys to your account, so the first time you connect you’ll log in and approve access.

  • Create a free account (or sign in) at app.cloud71.host.
  • Plan limits still apply — the free plan allows one site, which your AI can keep updating by name.

Connect from Claude

Works in the Claude desktop app and on claude.ai, on Claude plans that support custom connectors.

  1. 1 Open Settings → Connectors.
  2. 2 Click Add custom connector and paste the connector URL: https://mcp.cloud71.host/mcp.
  3. 3 A browser window opens to log in to cloud71 — sign in and approve the requested access.
  4. 4 The connector shows as connected and its tools become available in any new chat.

Connect from ChatGPT

Custom MCP connectors are available in ChatGPT’s connector settings (developer mode).

  1. 1 Go to Settings → Connectors and enable Developer mode (under Advanced).
  2. 2 Choose Add / Create connector, name it cloud71, and enter the MCP server URL: https://mcp.cloud71.host/mcp.
  3. 3 Authenticate via OAuth — log in to cloud71 and approve. The connector is then usable in chats.

Connect from Claude Code

Add the server with one command:

Terminal

claude mcp add --transport http cloud71 https://mcp.cloud71.host/mcp

Then run /mcp inside Claude Code and pick cloud71 to sign in through your browser. To make it available in every project, add --scope user:

claude mcp add --transport http --scope user cloud71 https://mcp.cloud71.host/mcp

Connect from Cursor

Add cloud71 to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it everywhere:

mcp.json

{
  "mcpServers": {
    "cloud71": { "url": "https://mcp.cloud71.host/mcp" }
  }
}

Cursor prompts you to sign in to cloud71 the first time the server connects. After that, ask the agent to deploy.

Connect from VS Code

Add cloud71 to .vscode/mcp.json in your workspace:

.vscode/mcp.json

{
  "servers": {
    "cloud71": { "type": "http", "url": "https://mcp.cloud71.host/mcp" }
  }
}

Start the server when VS Code offers to, sign in to cloud71 in the browser, then ask in the chat’s agent mode.

Connect from any other MCP client

Cline, Goose, and any client that supports remote MCP servers connect the same way: add a remote server with the URL https://mcp.cloud71.host/mcp over Streamable HTTP (or https://mcp.cloud71.host/sse if the client only supports SSE). The first connection opens the cloud71 sign-in in your browser.

Clients that use a JSON config (e.g. mcpServers) take the same URL with an http / streamable-HTTP transport.

What you can do once connected

The connector exposes ten tools. You never call them by name — ask in plain words and your assistant picks the right one.

deploy_files

Publish one file or many — HTML, CSS, JS, PDFs, images, Office docs, or a whole folder — sent as text or base64. Returns the live link. Pass site to update an existing site in place, and optionally a title, a password, a lead form, or an expiry.

list_sites

List your sites with their live links, custom domains, protection, and visits this month.

read_site

Read a site's files back so the assistant can edit them, then redeploy.

update_site

Change a site's title, password, lead form, expiry, or SEO title and description.

manage_domain

Attach a custom domain and get the DNS records to add, check whether SSL is live, or remove the domain.

get_site_stats

Visits and unique visitors by month, top referrers, and how many leads a site collected.

list_versions

List a site's saved versions (the last 5 republishes).

rollback_site

Restore a saved version. The current version is saved first, so a rollback can be undone.

get_qr_code

Get a QR code for a site, as an image and as SVG.

delete_site

Take a site down permanently.

Try saying

  • “Publish this page to cloud71 and give me the link.”
  • “Deploy the dist folder to cloud71 as acme-launch.”
  • “Read my site ‘portfolio’, change the headline, and republish it.”
  • “Put a password on my ‘q3-report’ site and make it expire in 7 days.”
  • “Set the custom domain launch.acme.com on ‘acme-launch’. Is SSL live yet?”
  • “How many people opened ‘pitch’ this month, and where did they come from?”
  • “Roll ‘pricing’ back to the previous version.”
  • “Give me a QR code for my ‘menu’ site.”

Tips for good results

  • Name the site. “…as acme-launch” gives you a stable URL (acme-launch.cloud71.site) that later deploys update in place.
  • Ask for one self-contained HTML file when you want a single page — inline CSS keeps it in one piece.
  • Ask for settings in plain words. “Put a password on it,” “expire it in a week,” or “how many people opened it?” all work from the chat. Passwords, lead capture, SEO, and custom domains need Starter or above; if your plan doesn't include one, your assistant will say so.
  • A few things stay in the dashboard: click heatmaps, team seats, white-label, redirects, and lead exports live in your dashboard.
  • Large videos or image sets are better sent through the REST API or the dashboard than through a chat.

Permissions & security

  • The connector requests three scopes: deploy, sites:read, and sites:write — enough to publish and manage your sites, nothing more.
  • Access is granted by OAuth. cloud71 never sees your AI provider, and your assistant never sees your cloud71 password.
  • Revoke access anytime by removing the connector in your AI client, or from your dashboard.

Troubleshooting

  • “Needs authentication” / 401 — the OAuth login hasn’t completed. Re-run the connect flow and finish the browser approval.
  • “Your free plan allows 1 site” — you’ve hit your plan’s site limit. Ask your AI to update your existing site by name, delete a site, or upgrade.
  • Tools don’t appear — start a fresh chat (and, in desktop apps, fully restart) so the client reloads the connector.

Prefer plain HTTP?

Scripts, scheduled jobs, and agents without MCP support can do the same things over the REST API — one POST with a bearer token publishes a file or a zipped site and returns the link.

Questions?

Email hello@cloud71.host and we’ll help you get connected.