Capa
Contact SalesGet Started

The content layer for everything you ship.

A headless CMS with a visual editor on top. Your team edits the live page, your agents work over MCP, and every publish is live in under three seconds.

Start FreeRead the Docs
The Capa editor: an entry with its fields on the left and status, version, and tags on the right.The Capa editor: an entry with its fields on the left and status, version, and tags on the right.
PublishedYour page is live
At a glance
  • < 3sPublish to live, no rebuild
  • 20–50 msA typical read, served close to each visitor
  • MCPFor Claude, Cursor, and Codex
  • $0To start, no card needed
At a glance
  • < 3sPublish to live, no rebuild
  • 20–50 msA typical read, served close to each visitor
  • MCPFor Claude, Cursor, and Codex
  • $0To start, no card needed
Publishing

Press Publish. Count to three.

Capa saves a version, clears only the cache that changed, and your page is live in under three seconds. No rebuild. No CI queue.

  1. Every save is a version

    Drafts never touch the live site. Open any earlier version and keep working from there.

  2. Publish one entry or a batch

    Changes from across models wait in one queue. Review them and publish together.

  3. Or schedule it

    Pick a date and time, then walk away. Capa publishes the latest draft right on schedule.

Visual editing

Click anything on your site to edit it.

Focus on a field and its spot on your site lights up. Click on your site and the editor jumps to the field. Save, and the draft re-renders in place. Try it.

Draft
Click anything on the page
osterialumen.com/menu

Osteria Lumen

Autumn menu, now serving

Wild mushroom risotto, brown butter squash, and the last of the figs.

  • Mushroom risotto$26
  • Squash agnolotti$24
  • Fig and ricotta tart$12

Ask about tonight’s wine pairing.

Your page is live
Product

Headless where it counts. Visual where it helps.

Developers get a clean, typed API. Editors and clients get the page itself. One project, as many sites as you ship.

Content your whole team can find.

Filter by model, folder, category, tag, and status. Switch to cards when the work is visual.

The Content list filtered to one tag, with filters for model, category, tag, and status.The Content list filtered to one tag, with filters for model, category, tag, and status.
Members · Capa Demo
Maya LindqvistOwner
Jonah BrandtDeveloper · all models
Ana RuizEditor · Articles, Menus
Client reviewViewer · read only
The Publishing log in Settings, listing scheduled publishes with who, when, and state.The Publishing log in Settings, listing scheduled publishes with who, when, and state.
The API Explorer with the Article model selected and a generated fetch request.The API Explorer with the Article model selected and a generated fetch request.
The workspace menu: switch between team workspaces, each with its own rail of models.The workspace menu: switch between team workspaces, each with its own rail of models.
Assistant

Ask for a model.
See it before it exists.

Capa’s Assistant works inside the admin. Ask for a model, a field, or a round of edits, and it shows you the plan, every field, and every connection before anything changes.

1Ask in plain words.

See Everything the Assistant Does
Developers

Wire it in minutes.
Read it in milliseconds.

An MCP server and a CLI for your agents. REST or GraphQL from one typed schema. Dated versions you upgrade on your schedule. Published content is served close to each visitor.

Made for your agents

Claude, Claude Code, Codex, and Cursor connect over MCP. They read your schema, check your content, and hand you a query that already ran.

About the MCP server
Claude Code

Write the query for the blog index: the 10 newest featured articles with their author’s name. Give me the SDK code for a Next.js server component.

  1. capa_graphql_schemaRunning
  2. capa_explore_dataRunning
  3. capa_graphql_buildRunning
$ claude mcp add capa -e CAPA_API_URL=https://cdn.capacms.com -e CAPA_KEY="$CAPA_KEY" -- npx -y @capacms/mcp

Always in cache

Published content is served from the nearest of Fastly's edge locations, typically in 20 to 50 ms. Publish to live in under three seconds. No ISR, no rebuilds.

About the edge cache

A request log: reads answered from the edge cache, typically in 20 to 50 ms, and a publish that purges only the keys it changed.

Upgrades on your schedule

Our releases never change a live site. Yours stays on the API version it was built on until you move it.

About the Content API
Capa-Version: 2026-10-01
  1. 2026-10-01Your site runs on this version.
  2. Next versionMove when you are ready.

REST or GraphQL

Both run on one planner, with the same keys, limits, and cache. Same entries back. Pick per page, not per project.

About the Content API
# GET /api/entries/articles
select = "title,author(name)"
limit  = 2
  1. Winter Field Guide 2026Brin Cole
  2. Merino or Synthetic?Cody Marsh
See Everything for DevelopersRead the API Docs

Your team will actually use it.

Free plan, no card. Pay per project when it goes live.

Start FreeSee Pricing