Skip to content
Headless CMSAPI-firstMCP-firstPilot build

The headless content workspace for pages that need to be managed by people, websites and AI agents.

Create it in Bobby CMS. Publish the data. Use it anywhere.

What Bobby CMS is not

Bobby CMS never hosts finished customer pages, blogs, landing pages or customer domains. External websites and applications perform all rendering and hosting.

The content model

Bobby CMS manages source content and publication state. Nothing else.

01

Collections

Collections organise related pages — documentation sets, product entries, articles. Custom collection types are available to every workspace during the pilot.

02

Pages

A page is structured content, not a rendered document. It holds ordered blocks and fields that any consumer can interpret.

03

Versions

Every change produces a version. Versions move through draft, review, approval and publication, and published versions stay immutable.

04

Publication

Publishing means making a content version available through API and MCP. It does not create, host or serve a webpage.

Three kinds of consumer, one permission model

API and MCP share a single permission service. No interface can exceed the scopes of the identity behind it.

People

Teams manage content in /console with workspace roles, review steps and an auditable history.

Websites and applications

Your own site or app reads the published data over the API and performs all rendering, routing and hosting.

AI agents

MCP clients can later read and manage authorized content through exactly the same permission scopes as the API — never more.

Pilot status

Not connected yet

Accounts, workspaces, the content API, MCP, payments and external metadata previews are not active in this build. Every screen you can reach today is presentation-only.

Brand not selected

Three wordmark directions, three text-logo directions and three palettes are rendered on /brand for review. None is approved.