We let Claude drive our CMS — here's what SDP Platform's MCP integration actually does

How SDP Platform's MCP connector gives Claude direct tool access to manage pages, posts, and media on a live site.

Most "AI website builder" pitches are vaporware. This one isn't — we hooked Claude straight into SDP Platform's backend and had it manage a real site, live, in a chat conversation.

What the connector actually gives Claude

Through SDP Platform's MCP connector, Claude gets direct tool access to the CMS: it can list every site on the account, read and rewrite pages and posts, upload media to the library, swap featured images, spin up new draft content, and publish — all without a human clicking through an admin panel.

Under the hood, that's a set of purpose-built tools, including:

  • list_websites and list_pages — see every site and page on the account
  • get_page — pull a page's full content, metadata, and current featured image
  • update_page / create_page — edit existing pages or draft new ones
  • create_post / update_post — write and revise blog posts
  • upload_website_image — add media to the library
  • set_content_featured_image — attach a featured image to a page or post

Each tool is wired up once through an authorized connector and stays available in any conversation from that point on.

Why this is different from a chatbot that "knows about" your site

Ask for something in plain language — "find the Turso site and check its featured image" — and Claude resolves it by actually calling the CMS and reading real data back, not guessing or hallucinating what a page probably contains. That distinction matters:

  1. A chatbot that only talks about your site is a novelty.
  2. A chatbot that can list your pages, open one, see its current metadata, and make a precise, scoped edit is a different category of tool entirely.
  3. It closes the gap between describing a change and actually making it.

What this looks like day to day

Content ops that used to mean a dashboard, a login, and a mouse now happen inline in chat:

  • Auditing pages across a site for missing metadata or broken images
  • Drafting a batch of posts from a short brief
  • Swapping a featured image without leaving the conversation
  • Restructuring meta titles and descriptions for SEO

It doesn't replace editorial judgment. Every draft this workflow produces still sits as a draft until a human reviews and publishes it. What it removes is the friction between having an idea for the site and getting that idea into the CMS correctly.

This post is the demo

This article was itself drafted, categorized, and pushed to SDP Platform as a draft by Claude, through this same connector, based on a short conversation about what to write.