What MCP is
MCP (Model Context Protocol) is a standard way for AI clients to call external tools. CloudSite exposes site management, publishing, domains, leads, subscriptions and analytics as MCP tools.
That lets you use natural language in Claude Code, Claude Desktop, Cursor, Codex or another MCP-capable client to run routine operations.
Connecting a client
- Create a cs_ access token under Settings → MCP / Agent; it is shown only once.
- Choose read-only or read-write permissions; a read-only token cannot change data.
- HTTP clients connect directly to https://cloudsite.editorapi.com/api/mcp.
- Stdio-only clients use the cloudsite-mcp.mjs bridge script.
Typical site operations
- List the account's sites and their status.
- Generate temporary preview links.
- Upload a locally generated static site as a ZIP or inline files.
- Generate or edit pages with AI.
- Publish to Cloudflare Pages.
- Bind and manage domains.
Working with business data
Enhancement tools cover forms and leads, chat conversations, subscriptions, visitors, tracking, analytics and exports. Read tools return full fields; write tools are constrained by permissions, parameter validation, audit logs and rate limits.
They can be combined into a daily operations summary: analytics totals, new leads and open conversations, handed to AI for a digest and to-do list.
Permissions and security boundaries
- A token only reaches the account that created it and stops working when the membership expires or the account is disabled.
- Admin-only platform finance, review and price settings are not exposed through MCP.
- Risky actions require confirmation and calls are audited.
- MCP does not bypass business rules, quotas, permissions or review.