Draftbase
Your agents can edit content now, over MCP

A headless CMS that doesn't fight your stack.

Draftbase is an MDX-based headless CMS for React developers. No YAML swamp, no deploy to fix a typo. Rich text is plain MDX, and your components render it.

npx @draftbase/create my-site

Scaffold an example site in one command. CLI source

Works with the frameworks you already ship

React
Next.js
Vue
Astro
Remix
Svelte
React Native
React
Next.js
Vue
Astro
Remix
Svelte
React Native
Scroll
The problem

Why does changing a paragraph need a deploy?

A typo goes in a ticket. The ticket waits for a deploy. Somewhere a config goblin adds a forty-field content modeling workshop, and your afternoon is gone. Draftbase gives writers an editor and leaves the components yours.

Authoring

How does an MDX-based CMS fit a React app?

Rich text is stored as plain MDX and served over the delivery API. Your components render it directly. No export step, no custom renderer you inherit and quietly fear.

  • MDX rich text, every save recorded as a revision you can roll back to
  • Writers get a drop-in editor — no separate CMS to host
  • Renders with the exact components your app uses
post.mdx
---
title: Ship weekly changelog
author: mira
---

# What shipped this week

<Callout tone="info">
  New MCP tool: agents can now open a PR.
</Callout>

Full width media, structured fields, zero glue code.
blogPost · schema
Titlestring · required
Slugstring · auto
Authorreference → Authors
Published atdatetime
Bodyrichtext (MDX)
Structure

Schema-driven collections, typed end to end

Define the fields once. Every entry follows that shape. Your components stop guessing, and nobody does schema archaeology at 3am.

  • 8 field types: text, rich text, number, boolean, date, media, reference, JSON
  • Swap in your own components and fields when the defaults aren’t enough
  • Same schema powers the editor UI and the API
Automation

Can an AI agent edit content in your CMS?

Yes, over MCP, through the same schema. Every agent write is validated before it lands. Your model gets the tools, not the raw files.

  • Agents call 26 MCP tools, validated against the same schema the editor UI writes through
  • Every automated change fires your existing webhooks
  • Every change is a revision — roll back to any of them
  • Semantic search over entries, powered by built-in embeddings
mcp · tool call
> agent: create a draft blog post

create_entry({
  templateId: "blogPost",
  locale: "en-US",
  fields: {
    title: "Shipping with MDX",
    body: "# Shipping with MDX\n..."
  }
})

✓ Entry created — schema validated, draft only
The numbers, no demo call required
8
field types, one schema
26
MCP tools agents can call
0
separate CMS to host
FAQ

Questions about the MDX-based headless CMS

What is Draftbase?

Draftbase is a lightweight, MDX-based headless CMS for React developers. Entries are typed fields, and rich text is stored as plain MDX, served over a delivery API so your existing React components render it directly. There is no separate CMS to host and no proprietary rich-text format to write a renderer for.

How is this different from a traditional headless CMS?

Most headless CMSs store rich text as proprietary JSON that you map to components yourself. Draftbase stores raw MDX and ships @draftbase/renderer, a React package that renders it with your components. Because the content is plain MDX, reading it back out over the API needs no conversion step.

Can an AI agent edit my content safely?

Yes. Agents connect over MCP and call 26 tools, each validated against your template schema the same way the editor UI is. Each change is recorded as a revision you can roll back, and automated edits fire the same webhooks a human edit does.

What does Draftbase cost?

Hobby is free and needs no credit card. Startup is $49/mo, Growth is $299/mo, and Scale is $499/mo. Enterprise pricing is custom. Every price is listed on the pricing page — no sales call required to see a number.

Ready to ship content like code, in MDX?

Hobby is free, no card. Startup is $49/mo when you outgrow it. That is less than one hour of the consultant who set up your last CMS.

All jokes aside: we are a CMS, we know. We just think you should spend the afternoon shipping, not fighting one.