Choosing between Sitekick AI CMS and 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"
    }
  }
}

Choosing between Sitekick AI CMS and Studio

Sitekick CMS is deployed. Studio custom applications remain unlaunched and inactive. Studio marketing or a waitlist does not provide an active Studio account.

CMS supports ongoing AI editing through Your Sitekick, saved conversations, reviewable tasks, page alternatives and whole-site projects. You can combine those workflows with advanced visual and WordPress tools; conversational editing is not reserved for Studio.

Use Work with Your Sitekick for current CMS help. CMS MCP editing requires separate service setup, supported client registration and authorization; do not assume it is immediately available to every account.

Studio is the future custom-application direction. The other Studio pages describe proposed workflows, not verified live features, plan entitlements or a reason to move a working CMS website today. Wait for an explicit availability announcement before relying on those workflows.