<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rakete</title>
    <description>The latest articles on DEV Community by Rakete (@rakete).</description>
    <link>https://dev.to/rakete</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4104813%2F49b8d65b-5fd7-4b60-938c-119a3e42d936.jpg</url>
      <title>DEV Community: Rakete</title>
      <link>https://dev.to/rakete</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rakete"/>
    <language>en</language>
    <item>
      <title>CMS AI in 2026: MCP Won the Wire Protocol. Most Platforms Still Solve the Wrong Problem.</title>
      <dc:creator>Rakete</dc:creator>
      <pubDate>Mon, 16 Nov 2026 09:41:22 +0000</pubDate>
      <link>https://dev.to/rakete/cms-ai-in-2026-mcp-won-the-wire-protocol-most-platforms-still-solve-the-wrong-problem-4d17</link>
      <guid>https://dev.to/rakete/cms-ai-in-2026-mcp-won-the-wire-protocol-most-platforms-still-solve-the-wrong-problem-4d17</guid>
      <description>&lt;p&gt;If you have connected &lt;strong&gt;Cursor&lt;/strong&gt;, &lt;strong&gt;Claude Code&lt;/strong&gt;, or &lt;strong&gt;ChatGPT&lt;/strong&gt; to a CMS in the last year, you have already voted in an informal standards election. The winner is &lt;strong&gt;&lt;a href="https://modelcontextprotocol.io/" rel="noopener noreferrer"&gt;Model Context Protocol (MCP)&lt;/a&gt;&lt;/strong&gt;: a way for agents to call typed tools instead of guessing from HTML exports or undocumented REST.&lt;/p&gt;

&lt;p&gt;Sanity ships a hosted MCP server. Contentful’s remote MCP server went generally available in 2025–2026. Strapi enables MCP in config. WordPress published an official &lt;strong&gt;MCP Adapter&lt;/strong&gt; that maps the &lt;strong&gt;Abilities API&lt;/strong&gt; to tools. Storyblok and Hygraph document MCP against their Management APIs.&lt;/p&gt;

&lt;p&gt;That convergence is real. It is also incomplete.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;MCP standardizes the cable.&lt;/strong&gt; It does not standardize &lt;em&gt;what problem you are solving&lt;/em&gt; when you plug an agent into a CMS. Vendors still bundle three different jobs into one marketing slide:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Ops agents&lt;/strong&gt; — change structured content from an IDE or chat client.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Editor assistants&lt;/strong&gt; — suggest copy inside the admin UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Public/agent layer&lt;/strong&gt; — tell the wider world (and other people’s models) what your organization is allowed to claim.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most comparisons stop at “we have MCP too.” For builders shipping sites, the interesting question is whether your stack makes those three surfaces &lt;strong&gt;explicit&lt;/strong&gt;, &lt;strong&gt;governed&lt;/strong&gt;, and &lt;strong&gt;composable&lt;/strong&gt;—or whether you get a translation button and a prayer.&lt;/p&gt;

&lt;p&gt;This article maps how leading CMS platforms implement AI workflows today, compares them directly, and explains what &lt;strong&gt;&lt;a href="https://birkly.com" rel="noopener noreferrer"&gt;Birkly&lt;/a&gt;&lt;/strong&gt; optimizes for. Features change quickly; a disclaimer at the end applies.&lt;/p&gt;




&lt;h2&gt;
  
  
  The four workflow shapes you will actually encounter
&lt;/h2&gt;

&lt;p&gt;Before naming vendors, it helps to name &lt;strong&gt;shapes&lt;/strong&gt;. Every “AI CMS” story is some mix of these:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Shape&lt;/th&gt;
&lt;th&gt;Who&lt;/th&gt;
&lt;th&gt;Trigger&lt;/th&gt;
&lt;th&gt;Output&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;External MCP agent&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Developer in Cursor / VS Code&lt;/td&gt;
&lt;td&gt;Natural language → tool calls&lt;/td&gt;
&lt;td&gt;CRUD on entries, schema, assets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;In-admin assistant&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Editor in Studio / admin UI&lt;/td&gt;
&lt;td&gt;Sidebar or inline “generate”&lt;/td&gt;
&lt;td&gt;Suggestions → human accept → save&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Server automation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Your code, webhooks, “functions”&lt;/td&gt;
&lt;td&gt;Publish event, cron, pipeline&lt;/td&gt;
&lt;td&gt;Drafts, patches, translations at scale&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Public agent surface&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Visitor or third-party model&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;/.well-known/*&lt;/code&gt;, browser tools&lt;/td&gt;
&lt;td&gt;What the world may read or safely &lt;em&gt;do&lt;/em&gt; on the site&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Sanity&lt;/strong&gt; is strong on all four if you pay attention to credits and APIs. &lt;strong&gt;Contentful&lt;/strong&gt; leans heavily on the second and third for marketers. &lt;strong&gt;WordPress&lt;/strong&gt; is strongest on external agents &lt;em&gt;if&lt;/em&gt; you assemble adapter + ability plugins—and weakest on structured content for agents to reason about. &lt;strong&gt;Sitecore&lt;/strong&gt; and &lt;strong&gt;Kontent.ai&lt;/strong&gt; ship packaged in-admin agents with workflow gates.&lt;/p&gt;

&lt;p&gt;If your team only evaluates “MCP checkboxes,” you will optimize the wrong layer.&lt;/p&gt;




&lt;h2&gt;
  
  
  Sanity: schema-aware automation for people who write code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.sanity.io/docs/ai/mcp-server" rel="noopener noreferrer"&gt;Sanity’s MCP server&lt;/a&gt; is hosted at &lt;code&gt;mcp.sanity.io&lt;/code&gt;. Agents run GROQ, patch documents, manage releases, and explore schema without you pasting TypeScript definitions into the chat.&lt;/p&gt;

&lt;p&gt;That is table stakes for developers. Sanity’s differentiated bet is &lt;strong&gt;Agent Actions&lt;/strong&gt;—programmatic, schema-aware LLM operations (&lt;code&gt;generate&lt;/code&gt;, &lt;code&gt;transform&lt;/code&gt;, &lt;code&gt;translate&lt;/code&gt;) you invoke from Functions, webhooks, or migration scripts. By default they create &lt;strong&gt;drafts&lt;/strong&gt;; publishing requires an explicit &lt;code&gt;forcePublishedWrite&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Editor-facing&lt;/strong&gt;, &lt;a href="https://www.sanity.io/docs/content-agent/introduction" rel="noopener noreferrer"&gt;Content Agent&lt;/a&gt; is conversational: find gaps, propose bulk edits, and &lt;strong&gt;confirm before apply&lt;/strong&gt; (drafts or Content Releases). &lt;strong&gt;AI Assist&lt;/strong&gt; covers quick field-level help inside Studio.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Typical Sanity workflow&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Developer connects Cursor → MCP → migrates schema or bulk-patches 400 legacy documents.&lt;/li&gt;
&lt;li&gt;Marketer publishes an article → Function fires → Agent Action translates → release branch → human review → publish.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Where Sanity wins:&lt;/strong&gt; treating the content model as the contract for both humans and machines; releases and audit as first-class citizens for AI output.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it costs you:&lt;/strong&gt; you are in Sanity’s ecosystem and pricing; local/self-host is not the positioning. Automation depth assumes engineering time to wire Functions + Actions.&lt;/p&gt;




&lt;h2&gt;
  
  
  Contentful: no-code AI Actions chained into marketing workflows
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.contentful.com/" rel="noopener noreferrer"&gt;Contentful&lt;/a&gt; optimized for marketing operations at scale. &lt;strong&gt;&lt;a href="https://www.contentful.com/help/ai-automations/ai-actions/" rel="noopener noreferrer"&gt;AI Actions&lt;/a&gt;&lt;/strong&gt; let teams define prompt + LLM pairs for translation, SEO rewrites, QA checks, and brand consistency—invoked on &lt;strong&gt;whole fields&lt;/strong&gt; (not arbitrary text selections). &lt;strong&gt;Automations&lt;/strong&gt; chain triggers to actions; &lt;strong&gt;Workflows&lt;/strong&gt; add approval stages.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://www.contentful.com/developers/docs/mcp/model-context-protocol-mcp-server/" rel="noopener noreferrer"&gt;remote MCP server&lt;/a&gt; exposes the same universe to external agents: entries, content types, releases, taxonomy, and even &lt;code&gt;create_ai_action&lt;/code&gt; / &lt;code&gt;invoke_ai_action&lt;/code&gt;. That is unusually complete for an enterprise SaaS.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Typical Contentful workflow&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Writer moves entry to “Ready for SEO.”&lt;/li&gt;
&lt;li&gt;Automation invokes an AI Action on meta title and description fields.&lt;/li&gt;
&lt;li&gt;Workflow routes to editor approval.&lt;/li&gt;
&lt;li&gt;Cursor, in parallel, runs &lt;code&gt;semantic_search&lt;/code&gt; across the space for a refactor project.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Where Contentful wins:&lt;/strong&gt; marketers can own automations without deploying Node functions; governance maps cleanly to spaces, roles, and workflows.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it costs you:&lt;/strong&gt; advanced AI is tiered (Enterprise add-ons matter); agents act as the &lt;strong&gt;connected user&lt;/strong&gt; (proxy permissions), which is fine until you need dedicated agent identities with different blast radius; field-level bulk actions are powerful but awkward when you need entry-level reasoning.&lt;/p&gt;




&lt;h2&gt;
  
  
  WordPress: MCP as a plugin sandwich
&lt;/h2&gt;

&lt;p&gt;WordPress did something principled: the &lt;strong&gt;&lt;a href="https://wordpress.org/plugins/mcp-adapter/" rel="noopener noreferrer"&gt;MCP Adapter&lt;/a&gt;&lt;/strong&gt; is infrastructure, not a content feature. It exposes &lt;strong&gt;Abilities&lt;/strong&gt; as MCP tools. Actual capabilities arrive via plugins—&lt;a href="https://wordpress.org/plugins/postnova-for-mcp/" rel="noopener noreferrer"&gt;Postnova&lt;/a&gt;, &lt;a href="https://wordpress.org/plugins/fyrins-content-manager-for-ai-agents/" rel="noopener noreferrer"&gt;Fyrins&lt;/a&gt;, &lt;a href="https://wordpress.org/plugins/wds-mcp-content-manager/" rel="noopener noreferrer"&gt;WDS MCP Content Manager&lt;/a&gt;, and others.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Typical WordPress workflow&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install MCP Adapter + a content ability pack.&lt;/li&gt;
&lt;li&gt;Create a &lt;strong&gt;dedicated WordPress user&lt;/strong&gt; with constrained capabilities + application password.&lt;/li&gt;
&lt;li&gt;Point Cursor at &lt;code&gt;wp-json/mcp/...&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Agent drafts posts; human reviews in Gutenberg—or does not, if you were careless with capabilities.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Where WordPress wins:&lt;/strong&gt; enormous installed base; you can expose exactly the abilities you want; dry-run patterns exist in newer plugins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it hurts agents:&lt;/strong&gt; content is often blocks and HTML soup, not a strict schema. Agents spend tokens inferring structure. Governance is &lt;strong&gt;your&lt;/strong&gt; problem: capability matrix, plugin choice, and whether the agent user can &lt;code&gt;delete_post&lt;/code&gt;. There is no universal “drafts only unless forced” semantic across plugins.&lt;/p&gt;




&lt;h2&gt;
  
  
  Enterprise “agentic CMS” (Storyblok, Hygraph, Kontent.ai, Sitecore)
&lt;/h2&gt;

&lt;p&gt;A second wave sells &lt;strong&gt;agents inside the product&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.storyblok.com/lp/agents" rel="noopener noreferrer"&gt;Storyblok Agents&lt;/a&gt;&lt;/strong&gt; — chat over stories, scheduled audits, user-confirmed writes; &lt;strong&gt;FlowMotion&lt;/strong&gt; (n8n) for longer automations on Enterprise.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://hygraph.com/ai-agents" rel="noopener noreferrer"&gt;Hygraph AI Agents&lt;/a&gt;&lt;/strong&gt; — agents bound to &lt;strong&gt;workflow steps&lt;/strong&gt; (translate at step 3, SEO at step 4) with side-by-side diff and per-field revert.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Kontent.ai&lt;/strong&gt; — “expert agents” (compliance, SEO, modeling) orchestrated with workflow traceability; some agents use &lt;strong&gt;dedicated permission models&lt;/strong&gt; rather than pure user proxy (&lt;a href="https://www.cmswire.com/digital-experience/the-dxp-label-is-fading-agent-documentation-shows-who-governs/" rel="noopener noreferrer"&gt;industry analysis&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.sitecore.com/platform/ai-and-agents" rel="noopener noreferrer"&gt;SitecoreAI&lt;/a&gt;&lt;/strong&gt; — large libraries of prebuilt agents, brand context, no-code flows across brief → asset → publish.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Typical workflow (Hygraph-style)&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Entry enters “Localization” step → Translation Agent runs → editor sees field-level diff → approves → next step.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Where they win:&lt;/strong&gt; non-developers get repeatable automation; approvals are visual; procurement loves “agents included.”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where they cost you:&lt;/strong&gt; platform lock-in, implementation services, and opaque credit models. External IDE agents become a second workflow unless MCP is kept in parity with in-product agents.&lt;/p&gt;




&lt;h2&gt;
  
  
  Strapi and the self-hosted headless middle
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://strapi.io/" rel="noopener noreferrer"&gt;Strapi&lt;/a&gt; advertises a &lt;strong&gt;built-in MCP server&lt;/strong&gt; (token-scoped tools) and &lt;strong&gt;Strapi AI&lt;/strong&gt; for generating content types from prompts or designs—developer acceleration more than marketer orchestration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where Strapi wins:&lt;/strong&gt; you host it; MCP permissions map to admin API tokens; attractive if DevOps is already yours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it trails Contentful/Sanity:&lt;/strong&gt; review workflows and native automation layers often sit behind Enterprise tiers; you may assemble more pipeline yourself.&lt;/p&gt;




&lt;h2&gt;
  
  
  What developers should demand (regardless of vendor)
&lt;/h2&gt;

&lt;p&gt;After reading a dozen vendor pages and MCP tool manifests, these requirements survive hype:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Schema is the agent contract.&lt;/strong&gt; If the CMS cannot tell an agent field types, relations, and validation rules, you will ship silent data corruption.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drafts by default for machine writes.&lt;/strong&gt; Sanity’s Agent Actions embody this; WordPress often does not unless you enforce it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Separate identities for automation.&lt;/strong&gt; Personal OAuth connectors vs service accounts with capped roles beat one shared API key on an admin user.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Approvals matched to channel.&lt;/strong&gt; In-admin queue for casual editors; client-side tool confirmation for IDE agents; workflow stages for enterprise—&lt;em&gt;but document which one applies where&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Procedures, not only tools.&lt;/strong&gt; Agents fail on &lt;code&gt;{for each entry in blog}&lt;/code&gt; vs detail-page URL context. Playbooks beat raw CRUD.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Public truth distinct from admin ops.&lt;/strong&gt; If your site makes factual claims, models should read a governed, versioned surface—not scraped marketing copy.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most stacks nail #1 partially and #2–#6 unevenly.&lt;/p&gt;




&lt;h2&gt;
  
  
  Birkly: three layers, one connector
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/Raaakete/Birkly" rel="noopener noreferrer"&gt;Birkly&lt;/a&gt;&lt;/strong&gt; is a self-hosted CMS—flat-file content, no runtime npm dependencies on the core, AI wired in from day one. Most vendors excel at one slice (hosted content API, marketer automations, or WordPress plugins). Birkly ties &lt;strong&gt;admin MCP&lt;/strong&gt;, &lt;strong&gt;public agent context&lt;/strong&gt;, and &lt;strong&gt;live-site tools&lt;/strong&gt; into one stack for teams that ship sites themselves.&lt;/p&gt;

&lt;h3&gt;
  
  
  Admin MCP (&lt;code&gt;Settings → AI&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;Paste a connector URL into Cursor, Claude, or ChatGPT. OAuth signs in with &lt;strong&gt;your&lt;/strong&gt; permissions, or a &lt;strong&gt;service agent&lt;/strong&gt; with a fixed role you control.&lt;/p&gt;

&lt;p&gt;From that one connection an agent can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Model and fill &lt;strong&gt;collections&lt;/strong&gt; (structured fields, validation, media ids—not block soup).&lt;/li&gt;
&lt;li&gt;Edit &lt;strong&gt;&lt;code&gt;project/&lt;/code&gt;&lt;/strong&gt; HTML, CSS, and JS beside the CMS (&lt;code&gt;write_project_file&lt;/code&gt;, &lt;code&gt;get_project_info&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Follow &lt;strong&gt;playbooks&lt;/strong&gt; baked into the session (templating, forms, fieldtypes) so fewer “obvious” agent failures.&lt;/li&gt;
&lt;li&gt;Run &lt;strong&gt;Agent Guide&lt;/strong&gt; and full &lt;strong&gt;admin actions&lt;/strong&gt; (&lt;code&gt;cms_admin_action&lt;/code&gt;, plus Commerce/Automation tools when plugins are on).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Sanity&lt;/strong&gt; and &lt;strong&gt;Contentful&lt;/strong&gt; offer excellent &lt;strong&gt;hosted MCP to their content APIs&lt;/strong&gt;—ideal when your frontend is a separate Next.js repo and marketing owns release trains in their cloud. &lt;strong&gt;Birkly’s MCP is built for the case they do not optimize: one external agent session that models content, writes templates, and publishes a working site.&lt;/strong&gt; You need a public HTTPS &lt;code&gt;/mcp&lt;/code&gt; on your instance; you keep the data and the model bill.&lt;/p&gt;

&lt;p&gt;Built-in &lt;strong&gt;admin chat&lt;/strong&gt; uses your API keys (including &lt;strong&gt;Ollama&lt;/strong&gt;). MCP writes confirm in the AI client; optional Birkly approval queue covers in-admin chat.&lt;/p&gt;

&lt;h3&gt;
  
  
  Agent Guide (what AI may say about you)
&lt;/h3&gt;

&lt;p&gt;Most CMS AI features optimize &lt;strong&gt;production&lt;/strong&gt; (more copy, faster translation). We added &lt;strong&gt;&lt;a href="https://docs.birkly.io/" rel="noopener noreferrer"&gt;Agent Guide&lt;/a&gt;&lt;/strong&gt;—a published JSON index with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sources of truth&lt;/strong&gt; (narrative, proof, reference roles)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Claims&lt;/strong&gt; with evidence URLs (only &lt;code&gt;supported&lt;/code&gt; claims appear in public/MCP views)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Products&lt;/strong&gt; with typed outbound links (CMS entry, marketplace, reviews)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Public: &lt;code&gt;/.well-known/agent-guide.json&lt;/code&gt;. MCP read tools: &lt;code&gt;get_agent_guide_context&lt;/code&gt;, claim/product graphs. &lt;strong&gt;AI Assist&lt;/strong&gt; in admin suggests registry entries and cross-links; nothing publishes until a human clicks &lt;strong&gt;Publish&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Publish &lt;code&gt;/.well-known/agent-guide.json&lt;/code&gt;: sources of truth, &lt;strong&gt;supported claims&lt;/strong&gt; with evidence URLs, products with links. MCP read tools expose the same snapshot; drafts never leak. Competitors can approximate this with metadata and enterprise compliance agents; none ship it as a first-class, publish-gated well-known file in the core product.&lt;/p&gt;

&lt;h3&gt;
  
  
  WebMCP (what a visitor’s AI may do)
&lt;/h3&gt;

&lt;p&gt;Separate from admin MCP, &lt;strong&gt;&lt;a href="https://docs.birkly.io/" rel="noopener noreferrer"&gt;WebMCP&lt;/a&gt;&lt;/strong&gt; exposes &lt;strong&gt;visitor-scoped&lt;/strong&gt; tools on the live site—contact forms, cart actions, RSVP—&lt;strong&gt;off by default&lt;/strong&gt;, always with &lt;strong&gt;visitor confirmation&lt;/strong&gt;. Admin MCP never touches the public browser surface.&lt;/p&gt;

&lt;p&gt;Visitor-scoped tools on the public site (forms, cart, RSVP)—off by default, confirm in the browser. Admin MCP never substitutes for this layer.&lt;/p&gt;

&lt;h3&gt;
  
  
  One prompt, one site (“bakery” smoke test)
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Contentful / Sanity default&lt;/th&gt;
&lt;th&gt;Birkly&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Content model&lt;/td&gt;
&lt;td&gt;Studio / content model UI&lt;/td&gt;
&lt;td&gt;MCP &lt;code&gt;create_collection&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seed content&lt;/td&gt;
&lt;td&gt;Entries in UI or MCP&lt;/td&gt;
&lt;td&gt;&lt;code&gt;create_entry&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Frontend&lt;/td&gt;
&lt;td&gt;Separate app repository&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;write_project_file&lt;/code&gt; under &lt;code&gt;project/&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Contact form&lt;/td&gt;
&lt;td&gt;Custom app or integration&lt;/td&gt;
&lt;td&gt;Collection + &lt;code&gt;{entry for}&lt;/code&gt; + playbooks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agent instructions&lt;/td&gt;
&lt;td&gt;Schema in MCP&lt;/td&gt;
&lt;td&gt;Schema + playbooks + project sandbox&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If your frontend is already a separate framework repo, &lt;strong&gt;Sanity&lt;/strong&gt; or &lt;strong&gt;Contentful&lt;/strong&gt; are natural fits. If the agent should own &lt;strong&gt;content + templates + forms&lt;/strong&gt; in one place, &lt;strong&gt;Birkly&lt;/strong&gt; is the straightforward match.&lt;/p&gt;




&lt;h2&gt;
  
  
  Simple scorecard
&lt;/h2&gt;

&lt;p&gt;Ratings are blunt: &lt;strong&gt;Strong&lt;/strong&gt; / &lt;strong&gt;Good&lt;/strong&gt; / &lt;strong&gt;Weak&lt;/strong&gt; for the job described in the row—not a count of MCP tool names.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Job&lt;/th&gt;
&lt;th&gt;Sanity&lt;/th&gt;
&lt;th&gt;Contentful&lt;/th&gt;
&lt;th&gt;WordPress + MCP&lt;/th&gt;
&lt;th&gt;Birkly&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;External agent ships a full site&lt;/strong&gt; (model, templates, forms, publish)&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;External MCP to a hosted content API&lt;/strong&gt; (releases, huge spaces, SaaS ops)&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;Marketer no-code AI workflows&lt;/strong&gt; (translate/SEO chains in UI)&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Structured content agents can trust&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Self-host + bring your own model&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;Weak&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;Published machine-readable org truth&lt;/strong&gt; (claims, evidence)&lt;/td&gt;
&lt;td&gt;DIY&lt;/td&gt;
&lt;td&gt;DIY&lt;/td&gt;
&lt;td&gt;DIY&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Strong&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Contentful&lt;/strong&gt; and &lt;strong&gt;Sanity&lt;/strong&gt; win when marketing runs AI inside a big SaaS content operation. &lt;strong&gt;WordPress&lt;/strong&gt; wins when the site is already there. &lt;strong&gt;Birkly&lt;/strong&gt; wins when you connect &lt;strong&gt;Cursor to your CMS&lt;/strong&gt; and expect a &lt;strong&gt;working site&lt;/strong&gt;, not only API patches in another repository.&lt;/p&gt;




&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;MCP is the default wire. The product question is what the agent is allowed to touch.&lt;/p&gt;

&lt;p&gt;Headless SaaS CMSs are excellent &lt;strong&gt;content databases with MCP&lt;/strong&gt;. Birkly is a &lt;strong&gt;site system with MCP&lt;/strong&gt;: collections, &lt;code&gt;project/&lt;/code&gt;, playbooks, Agent Guide, optional WebMCP—self-hosted, any model you plug in.&lt;/p&gt;

&lt;p&gt;If that is the job you are hiring an agent for, the comparison is simple. If you need a global marketing automation suite in a vendor cloud, buy the suite that was built for that job.&lt;/p&gt;




&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.birkly.io/01-admin/ai-overview.html" rel="noopener noreferrer"&gt;Birkly docs — AI overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.birkly.io/01-admin/mcp-connections.html" rel="noopener noreferrer"&gt;MCP connections&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.birkly.io/02-content/agent-guide-workflows.html" rel="noopener noreferrer"&gt;Agent Guide workflows&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.sanity.io/docs/ai/mcp-server" rel="noopener noreferrer"&gt;Sanity MCP&lt;/a&gt; · &lt;a href="https://www.contentful.com/developers/docs/mcp/model-context-protocol-mcp-server/" rel="noopener noreferrer"&gt;Contentful MCP&lt;/a&gt; · &lt;a href="https://developer.wordpress.org/news/2026/02/from-abilities-to-ai-agents-introducing-the-wordpress-mcp-adapter/" rel="noopener noreferrer"&gt;WordPress MCP Adapter&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Disclaimer — snapshot date &lt;strong&gt;16 November 2026&lt;/strong&gt; (Europe/Copenhagen)
&lt;/h2&gt;

&lt;p&gt;CMS AI features change monthly. This article reflects &lt;strong&gt;public documentation and product positioning as of 16 November 2026&lt;/strong&gt;. Names, tiers, MCP tool lists, and GA dates may have shifted by the time you read this. Verify against each vendor’s docs before architectural commitments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Birkly is developed by the team at &lt;a href="https://github.com/Raaakete/Birkly" rel="noopener noreferrer"&gt;github.com/Raaakete/Birkly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>api</category>
      <category>cms</category>
    </item>
    <item>
      <title>We build client sites on the CMS we ship</title>
      <dc:creator>Rakete</dc:creator>
      <pubDate>Sat, 07 Nov 2026 06:00:58 +0000</pubDate>
      <link>https://dev.to/rakete/we-build-client-sites-on-the-cms-we-ship-17gn</link>
      <guid>https://dev.to/rakete/we-build-client-sites-on-the-cms-we-ship-17gn</guid>
      <description>&lt;p&gt;We are &lt;a href="https://birklyandotherthings.com/" rel="noopener noreferrer"&gt;Birkly &amp;amp; Other Things&lt;/a&gt;, a small studio in Denmark. We &lt;a href="https://birklyandotherthings.com/service.html#s-web-dev" rel="noopener noreferrer"&gt;design and build websites&lt;/a&gt;. We also develop &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;Birkly&lt;/a&gt;, the open-source CMS those sites run on.&lt;/p&gt;

&lt;p&gt;That second part sounds like a footnote. For us it is the whole business model. It is why we like the work, why we can move fast without trapping clients in someone else's funnel, and why we can &lt;a href="https://birklyandotherthings.com/#offer" rel="noopener noreferrer"&gt;publish opening prices&lt;/a&gt; that would be hard to defend if we were reselling platforms and padding every quote.&lt;/p&gt;

&lt;p&gt;To celebrate opening the studio, every project we start in our first six months gets a heavily discounted price. The craft does not change. The stack does not change. What changes is that we are hungry for case studies, feedback, and proof that the way we build scales beyond our own sites. The product site at &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;birkly.io&lt;/a&gt; is one example. &lt;a href="https://birklyandotherthings.com/" rel="noopener noreferrer"&gt;Our own studio site&lt;/a&gt; is another. &lt;a href="https://birklyandotherthings.com/cases.html" rel="noopener noreferrer"&gt;Kekaba&lt;/a&gt; shows the same stack on a portfolio and journal.&lt;/p&gt;

&lt;p&gt;This post is not a sales page. It is how we think, written for developers and technical founders who wonder whether "studio plus CMS plus AI" is hype or a coherent workflow.&lt;/p&gt;

&lt;p&gt;What clients actually buy from us is not a generated layout. It is &lt;a href="https://birklyandotherthings.com/service.html#s-digital-design" rel="noopener noreferrer"&gt;custom design&lt;/a&gt;, a plan for content and structure, and a site architecture that fits how their business works. The opening offer on our site still says &lt;a href="https://birklyandotherthings.com/#offer" rel="noopener noreferrer"&gt;custom design, no templates&lt;/a&gt;. That is the line we mean.&lt;/p&gt;

&lt;h2&gt;
  
  
  The studio advantage is architectural, not magical
&lt;/h2&gt;

&lt;p&gt;Most client projects die in the gap between what the business needs and what the product allows.&lt;/p&gt;

&lt;p&gt;Page builders give you speed until you need a content model that does not exist. Enterprise CMSs give you power until you need hosting in a specific country, an exportable backup, or a template that does not fight your brand. SaaS stacks give you convenience until the monthly bill and the feature gate become the project manager.&lt;/p&gt;

&lt;p&gt;We picked a different default. &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;Birkly&lt;/a&gt; is file-based PHP with no mandatory database, self-hosted where you want it. The product pages spell out the &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;no runtime dependencies&lt;/a&gt; angle plainly: no npm or composer chain to babysit. Collections and entries live in plain project files. The public site is HTML and CSS you can read. The admin is decoupled from the core so we can redesign UI without rewiring business logic.&lt;/p&gt;

&lt;p&gt;For the studio, that means we choose hosting (&lt;a href="https://birklyandotherthings.com/service.html#s-hosting-care" rel="noopener noreferrer"&gt;our VPS, the client's infra, EU-only if that matters&lt;/a&gt;). We choose how data is stored and backed up: Git-friendly content, portable exports, no opaque vendor vault. We build to the client's shape through &lt;a href="https://birklyandotherthings.com/service.html#s-digital-design" rel="noopener noreferrer"&gt;digital design&lt;/a&gt;, not a theme marketplace's idea of "industry."&lt;/p&gt;

&lt;p&gt;Flexibility is not "we can do anything." It is "we are not forced through a single funnel of pages, fields, and integrations."&lt;/p&gt;

&lt;h2&gt;
  
  
  Design and structure before templates
&lt;/h2&gt;

&lt;p&gt;Every project starts with a conversation: what the business does, who visits the site, what they should do next. From that we sketch structure (pages, sections, repeating content) and an information architecture that matches the client, not a vertical SaaS preset.&lt;/p&gt;

&lt;p&gt;An experienced designer directs that work. You see &lt;a href="https://birklyandotherthings.com/service.html#s-digital-design" rel="noopener noreferrer"&gt;clickable design&lt;/a&gt; before heavy build work. Typography, spacing, rhythm, and how the brand should feel are human decisions. We are not shipping a template pack with your logo on top. We are not asking a model to "make me a modern website" and calling it done.&lt;/p&gt;

&lt;p&gt;AI can help with drafts: placeholder copy, rough markup, filling repetitive fields. It does not choose the concept. When something looks like generic AI layout or template churn, we throw it out and redraw. The site should look like one business, not like every other landing page from the same month.&lt;/p&gt;

&lt;p&gt;Only after the plan and design are agreed do we lock the Birkly content model and build. That order is why &lt;a href="https://birklyandotherthings.com/service.html" rel="noopener noreferrer"&gt;our process&lt;/a&gt; has a clear design phase before launch. The CMS stays flexible. The design intent does not get lost inside a theme setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI speeds us up. It does not run the show.
&lt;/h2&gt;

&lt;p&gt;We use AI heavily in the CMS, in our agents, and when drafting content or scaffolding projects. We are not ashamed of that. We are careful about where it is allowed to touch production.&lt;/p&gt;

&lt;p&gt;Our rule is simple: people with taste and context act as directors. AI proposes. Humans approve, edit, or throw away. On the product side, &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;Birkly is built for humans and agents in the same instance&lt;/a&gt;: structured APIs, Agent Guide, connections your team can approve. Suggestions can stay drafts, approvals exist, and nothing has to go live because a model was confident.&lt;/p&gt;

&lt;p&gt;What that looks like in practice:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Plan and design first (see above). Then content model. What repeats? What is shared chrome? What do visitors submit? We define collections and fields to match the agreed structure, not the other way around. &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;Birkly's own explainer&lt;/a&gt; walks through collections, entries, and templates in three steps if you want the parallel product view.&lt;/li&gt;
&lt;li&gt;Templates second. List pages, detail pages, static marketing sections, wired with Birkly's client templating and &lt;code&gt;birkly-client.js&lt;/code&gt;, not a proprietary shortcode dialect.&lt;/li&gt;
&lt;li&gt;AI as accelerant. First drafts of copy, starter HTML, bulk entries, repetitive refactors. All inspectable in Git.&lt;/li&gt;
&lt;li&gt;Human override everywhere. If a template is wrong, we edit the file. If the schema is wrong, we migrate the collection. If a plugin boundary is wrong, we patch the extension or build a small one.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That last point is rarer than it should be in "AI website" shops. We can step into every layer of the build: admin, API behaviour, &lt;code&gt;project/&lt;/code&gt; templates, plugins, deployment. We are not locked into a no-code surface that hides the system.&lt;/p&gt;

&lt;p&gt;Connected agents (for example via MCP) can create collections, write project files, and seed content. The same paths are open to a developer with a text editor. No parallel universe.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dogfooding is an economic advantage, not just a slogan
&lt;/h2&gt;

&lt;p&gt;We do not license a CMS per client seat. We do not pay a platform tax on every project and pass it through as agency markup. We maintain the runtime we ship.&lt;/p&gt;

&lt;p&gt;Reuse matters. Starter patterns, templates, and plugin combinations are already battle-tested from &lt;a href="https://birklyandotherthings.com/cases.html" rel="noopener noreferrer"&gt;previous work&lt;/a&gt;. The person who answers mail knows the CMS kernel, not a helpdesk script. When something hurts in a client project, it often becomes a product fix, and everyone's sites benefit. Ops stay lean: no database cluster for a brochure site, &lt;a href="https://birklyandotherthings.com/service.html#s-hosting-care" rel="noopener noreferrer"&gt;sensible hosting without enterprise bloat&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;So when we &lt;a href="https://birklyandotherthings.com/#offer" rel="noopener noreferrer"&gt;publish reference pricing&lt;/a&gt; (websites from 15,000 DKK, hosting and support from 190 DKK per month), that is not loss-leading mystery meat. It is a reference point for a custom-designed Birkly build with clear scope. Every project still gets a quote before we start. Content volume, &lt;a href="https://birklyandotherthings.com/products.html" rel="noopener noreferrer"&gt;integrations&lt;/a&gt; like Commerce, Events, Members, or Automation, and timelines move the number.&lt;/p&gt;

&lt;p&gt;The opening discount is honest too: limited window, same deliverables, we gain portfolio and product feedback. We say that out loud on the &lt;a href="https://birklyandotherthings.com/#offer" rel="noopener noreferrer"&gt;offer section of the studio site&lt;/a&gt;. Dev.to readers can smell hidden upsells. We would rather be boring and precise.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "built on Birkly" actually means for a client
&lt;/h2&gt;

&lt;p&gt;Non-technical owners hear "CMS" and think WordPress clutter or Squarespace limits. We pitch three promises, and we try to say them the same way on &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;birkly.io&lt;/a&gt; and on &lt;a href="https://birklyandotherthings.com/service.html" rel="noopener noreferrer"&gt;our services page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;First, shape it around the business. Products, team, events, journal posts: fields match how they talk, not how a template vendor talks.&lt;/p&gt;

&lt;p&gt;Second, they can run day-to-day content. If you can write email, you can publish. No developer for every text tweak.&lt;/p&gt;

&lt;p&gt;Third, they own the result. Design, content, and deployment are portable. "Yours to keep" is not legal fine print. It is the architecture.&lt;/p&gt;

&lt;p&gt;When the business outgrows the launch scope, we add plugins, not a platform migration. &lt;a href="https://birklyandotherthings.com/products.html" rel="noopener noreferrer"&gt;The studio lists what we ship and extend&lt;/a&gt;. &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;The product site describes the Hub catalog&lt;/a&gt; for Commerce, Events, Automation, Studio, and the rest. Each plugin is self-contained. We do not fork the core for one client's whim.&lt;/p&gt;

&lt;p&gt;For developers reading this: Birkly is &lt;a href="https://github.com/Raaakete/Birkly" rel="noopener noreferrer"&gt;open source&lt;/a&gt; and still in early alpha. &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;birkly.io&lt;/a&gt; does not hide that tone. We build production sites on it because we control the risk, not because we pretend semver serenity. If you self-host, you get the same separation of concerns we rely on: core, admin presentation, client delivery, extensions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this is for
&lt;/h2&gt;

&lt;p&gt;We work with people who want a site that looks and works like their business, planned and designed for them, not scraped from a template catalog or a one-shot AI prompt.&lt;/p&gt;

&lt;p&gt;That includes anyone who wants a designer in the loop from the first conversation through launch: structure, visual direction, and build in one studio. It includes regular company sites, portfolios, journals, and case-driven work like &lt;a href="https://birklyandotherthings.com/cases.html" rel="noopener noreferrer"&gt;what we have already shipped&lt;/a&gt;. It includes shops, events, sign-ups, and member areas when &lt;a href="https://birklyandotherthings.com/products.html" rel="noopener noreferrer"&gt;Commerce, Events, or User plugins&lt;/a&gt; fit the model you already agreed in design.&lt;/p&gt;

&lt;p&gt;It includes owners who will update content themselves and founders who care about hosting and data. It includes teams that want &lt;a href="https://birklyandotherthings.com/service.html#s-digital-design" rel="noopener noreferrer"&gt;digital design&lt;/a&gt; and &lt;a href="https://birklyandotherthings.com/service.html#s-web-dev" rel="noopener noreferrer"&gt;development&lt;/a&gt; together, plus optional &lt;a href="https://birklyandotherthings.com/service.html#s-hosting-care" rel="noopener noreferrer"&gt;hosting and care&lt;/a&gt;. It includes odd workflows, custom plugins, redesigns, and migrations onto Birkly when the old site never matched how you work.&lt;/p&gt;

&lt;p&gt;Most projects mix those things. If you want custom architecture and a directed design process, that is the default for us, not an upgrade tier. Say hej on &lt;a href="https://birklyandotherthings.com/" rel="noopener noreferrer"&gt;the studio site&lt;/a&gt; and we figure out scope from there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we wrote this on DEV
&lt;/h2&gt;

&lt;p&gt;We hang out here because the argument matters to this audience. You can use modern AI without giving up the repo. You can run a studio without becoming a reseller. You can open-source the middle layer and still make a living on design, implementation, and care.&lt;/p&gt;

&lt;p&gt;If you are building your own stack, read &lt;a href="https://birkly.io/" rel="noopener noreferrer"&gt;birkly.io&lt;/a&gt;, download the CMS, or ignore us and steal the workflow: content model first, decoupled UI, human gates on AI.&lt;/p&gt;

&lt;p&gt;If you need a studio hand for the first build, the &lt;a href="https://birklyandotherthings.com/#offer" rel="noopener noreferrer"&gt;opening offer on birklyandotherthings.com&lt;/a&gt; is live for our first six months. Bring a weird content model. We like those.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>startup</category>
      <category>design</category>
    </item>
    <item>
      <title>birkly.io is a normal site with a few special needs. Here is what it takes to build it.</title>
      <dc:creator>Rakete</dc:creator>
      <pubDate>Fri, 25 Sep 2026 06:52:46 +0000</pubDate>
      <link>https://dev.to/rakete/birklyio-is-a-normal-site-with-a-few-special-needs-here-is-what-it-takes-to-build-it-5985</link>
      <guid>https://dev.to/rakete/birklyio-is-a-normal-site-with-a-few-special-needs-here-is-what-it-takes-to-build-it-5985</guid>
      <description>&lt;p&gt;birkly.io is not an overcomplicated website. It has a contact form, a waitlist, donations, sponsor slots, and a club for members. What it does have, like most real projects, is its own special needs. Someone can donate any amount between €1 and €5,000, once or every month, appear on a public supporter list, and join the club with the same email. If they cancel a monthly donation, they keep their account. Only the supporter label on their profile changes.&lt;/p&gt;

&lt;p&gt;This post is about why Birkly was built. birkly.io was the first real website made with it, and it proved the point: those special needs can stay part of one normal site.&lt;/p&gt;

&lt;p&gt;On Birkly, that is what happened. The contact messages, waitlist entries, sponsor texts, and club posts are normal content. An automation sends the “you are on the waitlist” email, and another email later invites that group. A second automation updates the supporter label when a payment starts or a monthly donation ends. The club itself can be free, or people can join by donating. Free signup is turned off right now, so joining goes through the donation. Turning it back on does not remove the donation.&lt;/p&gt;

&lt;p&gt;The only paid plugin is Commerce. During early access it costs €29.90 a month, or €24.90 a month if you pay yearly. The listed price next to that offer is €39.90 a month. You also need your own server. Card fees are Stripe’s usual fees.&lt;/p&gt;

&lt;p&gt;An AI assistant can set this up with you. It can create the content, the forms, the emails, the donation, and the club, because those are the same buttons a person uses in the admin. Birkly does not charge extra for the AI. You can connect a free model from OpenRouter, or a paid one if you prefer.&lt;/p&gt;

&lt;p&gt;On other systems, the same special needs are often the part that gets difficult, or impossible, without extra products or custom software. You can still launch something. It is usually a smaller version of the idea, because the tool only sells part of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;p&gt;Prices below are public prices from September 2026. Yearly prices are used when the company offers them. Dollar prices and euro prices are not the same currency. Card fees are extra.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Birkly.&lt;/strong&gt; &lt;br&gt;
Could you build birkly.io with it? &lt;br&gt;
&lt;code&gt;Yes. This is how it is built.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost? &lt;br&gt;
&lt;code&gt;€24.90 a month + hosting.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Shopify.&lt;/strong&gt;&lt;br&gt;
Could you build birkly.io with it?&lt;br&gt;
&lt;code&gt;No. Donation options are limited, and it has no community.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost?&lt;br&gt;
&lt;code&gt;About $123 a month, hosting included.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WordPress.&lt;/strong&gt;&lt;br&gt;
Could you build birkly.io with it?&lt;br&gt;
&lt;code&gt;Partly. Needs custom development to connect the plugins.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost?&lt;br&gt;
&lt;code&gt;About $44 a month + custom development + hosting.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strapi.&lt;/strong&gt;&lt;br&gt;
Could you build birkly.io with it?&lt;br&gt;
&lt;code&gt;No. Needs a complete custom build.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost?&lt;br&gt;
&lt;code&gt;Custom development + hosting.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Webflow.&lt;/strong&gt;&lt;br&gt;
Could you build birkly.io with it?&lt;br&gt;
&lt;code&gt;No. It cannot do this donation, and it has no community.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost?&lt;br&gt;
&lt;code&gt;About $139 a month, hosting included.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Squarespace.&lt;/strong&gt;&lt;br&gt;
Could you build birkly.io with it?&lt;br&gt;
&lt;code&gt;No. No supporter list, and no community.&lt;/code&gt;&lt;br&gt;
What would the closest possible solution cost?&lt;br&gt;
&lt;code&gt;About $113 a month, hosting included.&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Shopify
&lt;/h2&gt;

&lt;p&gt;Shopify can publish the pages, the contact form, and a waitlist. The Basic plan is $29 a month and includes hosting, automatic emails, and 10,000 emails a month.&lt;/p&gt;

&lt;p&gt;It cannot take the donation the way birkly.io does. A small app, about $5 a month, lets someone type a one-time amount. A monthly donation has to be a fixed price, such as €5 or €15, not “any amount between €1 and €5,000.” Shopify also has no club with posts, comments, and a supporter label. For that you add another product, such as Circle, at $89 a month. Members then have a second login, separate from the shop.&lt;/p&gt;

&lt;p&gt;You can launch a shop, a one-time donation, a few fixed monthly amounts, and a club on another site. That is a real website. It is not the same idea. The total is about $123 a month, hosting included. If you use Stripe instead of Shopify’s own payments, Basic adds an extra 2% fee.&lt;/p&gt;

&lt;p&gt;Shopify’s own assistant, Sidekick, is included. It can help you set up the shop. It cannot add a donation or a club that Shopify does not offer.&lt;/p&gt;

&lt;h2&gt;
  
  
  WordPress
&lt;/h2&gt;

&lt;p&gt;WordPress can end up doing the same things for visitors. It does not do them as one product. You install separate plugins, and someone has to connect them.&lt;/p&gt;

&lt;p&gt;A free form plugin can take contact messages and sponsor enquiries. FluentCRM Pro, at $129 a year, can send the waitlist confirmation and the later invite. GiveWP Pro, at $399 a year, can take a custom donation amount every month through Stripe. BuddyBoss is free and can give members a profile, a feed, and a free registration.&lt;/p&gt;

&lt;p&gt;These plugins do not automatically know about each other. A donation does not, by itself, create a club account, add the supporter label, or keep the account when the monthly donation stops. Someone has to build that link. The public list of supporters, with names and logos, is also something you add. The plugins are about $44 a month, plus the custom development that connects them, plus a server.&lt;/p&gt;

&lt;p&gt;So the site is possible. The hard part is the link between “this person paid” and “this person is a member,” and you have to look after that link when the plugins update.&lt;/p&gt;

&lt;h2&gt;
  
  
  Strapi
&lt;/h2&gt;

&lt;p&gt;Strapi is a content system. It can store pages, sponsor texts, and form entries. It does not include donations, waitlist emails, supporter labels, or a club.&lt;/p&gt;

&lt;p&gt;To get the same website, a developer has to build those parts: the payment page, the emails, the rule that updates a member’s label, and the club with posts and comments. The Strapi license can be free. What you are paying for, in time or in money, is that custom development, plus hosting. A smaller version is Strapi for the pages, plus Circle at $89 a month for the community. Donors and members are still in two different places.&lt;/p&gt;

&lt;h2&gt;
  
  
  Webflow
&lt;/h2&gt;

&lt;p&gt;Webflow can design the pages and the sponsor section. The Premium plan is $25 a month and includes hosting. It cannot take the birkly.io donation: any amount, once or every month, together with a public supporter list. It also has no club. Built-in member accounts, and this kind of monthly payment, have been removed.&lt;/p&gt;

&lt;p&gt;A login tool such as Memberstack, about $25 a month, can hide pages until someone logs in. That is a locked page, not a club with posts and a supporter label. The waitlist emails need another tool, such as Zapier or Make.&lt;/p&gt;

&lt;p&gt;The closest setup is about $139 a month, hosting included. That pays for the site, a login tool, and a separate club. The donation of any amount every month, and the supporter list, are still missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Squarespace
&lt;/h2&gt;

&lt;p&gt;Squarespace includes hosting, the forms, and a donation block on the Basic plan at $16 a month. What it cannot do is the public supporter list with names and logos, or a community. Memberships can be free or paid, and they open pages, courses, and videos. They do not give members a feed, comments, or a supporter label that updates when a donation starts or stops.&lt;/p&gt;

&lt;p&gt;The waitlist needs Squarespace Email, about $8 a month. A real club means a separate product such as Circle, at $89 a month, with its own login. Together that is about $113 a month, hosting included. The donation and the club still do not share one account.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you still want the full idea
&lt;/h2&gt;

&lt;p&gt;On the other systems, you can almost always build the missing parts yourself, inside the CMS or as a separate tool next to it. That work is expensive and slow, and it does not stop when the site goes live. Someone has to keep it working after release.&lt;/p&gt;

&lt;p&gt;An AI that controls the screen can operate those systems too, because it can use the same admin a person sees. That ability costs money, and it also raises the chance of mistakes, opens more security gaps, and can expose private information to the AI provider. What it builds is still custom software, so the cost and the upkeep remain.&lt;/p&gt;

&lt;p&gt;Birkly is the way through this without those compromises. The donation, the emails, and the club are already part of the product, and an assistant uses those same parts instead of building them, or taking over the whole screen to reach them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this example exists
&lt;/h2&gt;

&lt;p&gt;This is not a post against Shopify, WordPress, Strapi, Webflow, or Squarespace. They are capable products, and each one fits the people it was made for.&lt;/p&gt;

&lt;p&gt;birkly.io is not a specially complicated site. It is a normal project with a few advanced needs, which is what most projects turn out to have. It was also the first real website built with Birkly, and building it showed why Birkly exists: so those needs can be met in the product itself.&lt;/p&gt;

&lt;p&gt;Birkly was not made to copy birkly.io. It is meant to stay flexible, simple, and powerful, so a project with its own requirements can be built natively, without giving up part of the idea to match the tool.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>wordpress</category>
      <category>opensource</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Bring your own AI: the three ways to connect an assistant to a Birkly site</title>
      <dc:creator>Rakete</dc:creator>
      <pubDate>Tue, 15 Sep 2026 09:28:00 +0000</pubDate>
      <link>https://dev.to/rakete/bring-your-own-ai-the-three-ways-to-connect-an-assistant-to-a-birkly-site-41h2</link>
      <guid>https://dev.to/rakete/bring-your-own-ai-the-three-ways-to-connect-an-assistant-to-a-birkly-site-41h2</guid>
      <description>&lt;p&gt;&lt;strong&gt;Quick bit of context first, since this is a small project and there's a decent chance you're reading this without knowing what Birkly even is. Birkly is an open, AI-native content management platform that enables everyone to build, manage and operate digital experiences without vendor lock-in, unnecessary software complexity or dependency-heavy technology stacks. You can read more about it on &lt;a href="https://birkly.io" rel="noopener noreferrer"&gt;https://birkly.io&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Here's something I like about how Birkly handles AI: it treats an AI connection the same way it treats a person. You give it a role, and that role decides what it can and can't do. There's no looser, separate rulebook for "what an AI is allowed to touch." It goes through the exact same role and permission system a human user does.&lt;/p&gt;

&lt;p&gt;That one choice shapes everything else. There are three different ways to connect an AI to a site: a personal connector, a service agent, and a built in assistant. Each one answers the same underlying question a bit differently, namely which role the AI is actually operating under. But no matter which of the three you use, admins still keep the final say. A site wide switch and a hard denylist sit above all three, all the time, and neither can be talked around.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three ways to assign that role
&lt;/h2&gt;

&lt;p&gt;Which role an AI connection ends up with, and where that role comes from, depends on which method you pick.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Personal connector: the AI acts as whoever's logged in&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is the default option. Under Settings → AI there's a single MCP URL for the whole site. You paste that into whatever AI client you're using, Claude, ChatGPT, Cursor, anything that speaks MCP, sign in with your Birkly account, and approve a consent screen that spells out exactly which role you're handing over.&lt;/p&gt;

&lt;p&gt;From then on the AI simply has that account's permissions. If you're an Editor, it acts as an Editor. If you're an Admin, it acts as an Admin, full access to content, media, settings, plugins, the whole site. There's no separate "AI role" to think about, because there's no separate identity at all. It's just you, working through a different interface. One set of permissions to keep track of instead of two.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Service agent: a fixed role, not tied to a person&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sometimes "acts as whoever's logged in" isn't what you want. Maybe it's an automation, an integration, or a teammate who really doesn't need full account access just so their AI client can help with content. That's what a service agent is for. An admin creates it, gives it a fixed role that never changes (always Editor, say, no matter who's actually behind it), decides which people can even see it, and hands out its own dedicated MCP URL.&lt;/p&gt;

&lt;p&gt;Under the hood it's the same tool registry and the same permission checks as the personal connector. The only real difference is where the role comes from. A personal connector's role follows the account. A service agent's role is pinned in place by an admin and stays put.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Built in assistant: bring your own model&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The third option skips MCP entirely and lives right inside the admin panel as a chat window. You connect it with an API key from whatever provider you already use, OpenAI, Anthropic, Google, OpenRouter, a local Ollama setup, even a custom endpoint. You set its role the same way you would for a connector, and there's an optional "Require approval" setting that holds every write it proposes in an Approvals tab until a human actually clicks confirm.&lt;/p&gt;

&lt;p&gt;This one's for people who just want a chat box in their CMS, backed by whichever model they already have access to, without setting up a separate AI app. Birkly genuinely doesn't care which company made the model. It only cares that it can call the same tool registry the other two methods use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Same registry, three doors
&lt;/h2&gt;

&lt;p&gt;What ties all three together is that they're not really three different feature sets. They're three different doors into the same room. Whether an AI is working through a person's own login, acting as a fixed role service bot, or chatting away in the admin panel on someone's own API key, it's reaching the exact same catalog of actions: content, media, the site's files, plugin admin tools, settings, all of it. The thing that changes between them is whose identity it's borrowing, and how a write actually gets confirmed. OAuth consent up front for the two MCP methods, an optional approval queue for the built in one.&lt;/p&gt;

&lt;p&gt;"Bring your own AI" usually just means "point any model at our API." Here it stretches a bit further than that. You bring your own client, your own model provider, and your own identity story, personal, service, or built in, and the underlying permission model never has to bend to accommodate any of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  A ceiling above all three
&lt;/h2&gt;

&lt;p&gt;Borrowing a role, whether it's a person's own or a service agent's fixed one, is the identity layer. But it's not the only thing standing between an AI connection and something going wrong. Two site wide settings sit above all three methods, and they apply no matter which role is in play.&lt;/p&gt;

&lt;p&gt;The first is the AI &amp;amp; MCP tools switch. It has three states. Normal, where tools simply follow role permissions and this is the default. Read only chat, where the built in assistant still works but no MCP tools get exposed or executed at all. And Disabled, where all tool execution is blocked outright and MCP's tools list comes back empty. This overrides whatever a connection's own approval setting says. If the site is set to Read only or Disabled, nothing gets more access than that, no matter how privileged its role is.&lt;/p&gt;

&lt;p&gt;The second is the Plugin Security Denylist. Specific collections can be marked as protected, and specific plugin admin spaces can be denied entirely, which blocks that plugin's sidebar injection and any space scoped hooks it would otherwise get. Anything on this list is simply off limits to every plugin, regardless of what capabilities it's been granted elsewhere. The settings page describes it plainly as a hard barrier that can't be overridden.&lt;/p&gt;

&lt;p&gt;So the role based model answers one question: whose permissions does this AI have. These two settings answer a different one entirely: what's the absolute ceiling, no matter whose permissions those are. Same doors as before, just with a breaker switch sitting above all of them that doesn't care which one an AI happened to walk through.&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>webdev</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
