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

The honest difference is who does the work.

Choose Studio when you want the site done for you

Sitekick AI Studio fits when:

  • You want a professional site without becoming a web designer.
  • You would rather describe the business than move elements around.
  • You want the site looked after after launch, not just built once.

Studio is the newer product, and its promise is simple: describe the business, review what AI builds, publish, and let Studio keep it healthy.

Choose CMS when you want the site in your hands

Sitekick AI CMS fits when:

  • You enjoy hands-on editing and want control of every detail.
  • You already have content and a look in mind, and want to execute it.
  • You prefer a traditional editor where what you see is exactly what you get.

CMS is a mature, complete product with a full visual editor, a design editor for branding, support for more than 100 languages, blogging, and e-commerce pages. Its documentation lives at the Sitekick AI CMS documentation.

Both are safe choices

Neither product is going away. CMS customers keep full access to the editor, their sites, and their plans, and Studio is where most new development is happening.

If you are still unsure, try Studio first — a brief takes minutes, and you will learn more from a draft than from any comparison table.