Moving from Sitekick AI CMS to Studio

Connect to Sitekick docs

Search and read the public documentation from an MCP-compatible assistant. No account or API key is required.

Add this URL as a remote MCP server in your client. It can only read public docs.

Claude Code

claude mcp add --transport http sitekick-docs https://docs.sitekick.ai/mcp

Codex

codex mcp add sitekick-docs --url https://docs.sitekick.ai/mcp

Other clients

{
  "mcpServers": {
    "sitekick-docs": {
      "url": "https://docs.sitekick.ai/mcp",
      "type": "http"
    }
  }
}

Moving from Sitekick AI CMS to Studio

Studio custom applications remain unlaunched and inactive. There is no currently documented customer migration workflow to perform. Do not change your domain, retire a CMS site or assume account, plan or content transfer based on the proposed Studio guides.

Continue using Sitekick CMS: ongoing conversational editing and whole-site projects are CMS features. See Work with Your Sitekick.

If Studio becomes available, review its announced eligibility, migration support and domain procedure before making a change. A waitlist records interest; it is not an active paid Studio account.