Hosted first. MCP at the center.

A publishing platform
at your command.

Create a site from a kit. Connect your AI app. Manage content, design and workflows through MCP, with people in control.

Explore the pilotExplore the kits →

Pilot sites require operator approval. Paid self-service is coming.

From a request to your own siteExample
site_create {
  "name": "My publication",
  "subdomain": "my-publication",
  "kit": "ai-publication",
  "hostingPlan": "your-offer-id",
  "expectedPlanVersion": 2,
  "requestKey": "launch-2026-001"
}
Request→Approval→Your site + MCP

Use the offer ID and version returned by hosting_offers_list.
Content starts empty. The newsroom starts paused.

Hosted infrastructureVersion-checked editsDraft isolationYour own site MCP

Start with the structure
that fits your work.

Kits configure the platform’s native modules. They bring a starting structure; your team supplies the content, identity and editorial rules.

Advocacy & Campaign

An issue or campaign site with a newsroom: petitions, polls, actions, campaign pages, public references and member community, on top of the AI Publication modules. Starts empty, with indexing disabled and its newsroom paused.

advocacy-campaign
  • Editorial Desk
  • Media Desk
  • People
  • People Footage
  • Motion Engine
  • Reader Hub
  • Submission Desk
  • Contributor Desk
  • Briefing Editions
  • Action Center
  • Campaign Pages
  • Petitions
  • Participation
  • Public References
  • Engagement
  • Community

AI Publication

A news publication run by an AI newsroom (Steinbeck) with human editors: stories, people, motion headers, reader accounts, tips and briefings. Starts empty, with indexing disabled and its newsroom paused.

ai-publication
  • Editorial Desk
  • Media Desk
  • People
  • People Footage
  • Motion Engine
  • Reader Hub
  • Submission Desk
  • Contributor Desk
  • Briefing Editions

A site you can shape.
A workflow you can trust.

The website and the AI connection work together. Each publication keeps its own content, accounts and settings.

Manage through MCP

Use content and settings tools from your connected AI app. Validation and permissions stay in the CMS service.

Review before publishing

Draft content stays separate from public pages, search and feeds. Content edits require current versions and record revisions.

Grow with native modules

Choose a publication or campaign kit, then configure the modules your site uses through its own MCP.

Next: the creator ecosystem

Themes and modules.
Made to be shared.

We’re building toward a showcase for independently packaged themes and extensions, with compatibility details and a clear install path.

Creator submissions, live theme previews, checkout and seller payouts are planned. This pilot catalog lists native kit modules; it does not sell third-party packages.

See the launch sequence →

Connect. Configure. Publish.

  1. Connect your AI app

    Add the control plane’s MCP address and authenticate. The control plane manages your sites.

  2. Request a site from a kit

    Choose an address, kit and available hosting offer. A valid paid or pilot entitlement and operator approval are required.

  3. Connect to your site’s MCP

    Once it’s live, connect to the site, configure staff and settings, and create your first content. Publishing remains a deliberate step.

Read the connection guide