Two connections, one workflow

Your platform.
Your site.

Use the control plane to request and manage hosting. Use your publication’s own MCP to manage its content and appearance.

Site requests are currently closed on this deployment while hosting readiness is verified.

1. Connect to the control plane

MCP address: https://control.cmsmcp.com/mcp

In an MCP client that supports remote Streamable HTTP, add that endpoint. With email sign-in enabled, authenticate in the browser and approve the app. Scripted clients may use an operator-issued account key as a Bearer token. Keep keys private.

Transport and OAuth flows are covered by automated tests. Named AI clients need their own end-to-end pilot validation.

2. Request your site

  1. Read the available kits

    Call kits_list. Choose a kit ID from the result.

  2. Create one request

    Read hosting_offers_list and hosting_status first. A current paid subscription or time-limited pilot grant is required. Call site_create with name, subdomain, kit, hostingPlan, expectedPlanVersion and a unique requestKey. Reuse that key with the same details if the connection drops.

  3. Wait for approval and provisioning

    Read site_status. Hosting is approved by an operator; a request is not a running site. The live result includes the site’s own MCP and dashboard addresses.

3. Connect to your publication

Add the returned site MCP address as a second connection. Sign in with the owner email registered on your account. Configure your publication, its staff and workflows before publishing.

For control-plane lifecycle edits, first read site_status, then provide its version as expectedVersion. Cancellation stops hosting after host confirmation and keeps the site’s data. Data deletion is a separate capability still to be built.