Bird CMS

Roadmap

Where Bird CMS is going: recently shipped, planned, and exploratory work. An open, undated roadmap you can shape by opening an issue on GitHub.

Bird CMS is developed in the open. This page is a rough map of where it is going, grouped by how close each item is. Nothing here is a dated promise: priorities shift with real usage, and the fastest way to move something up the list is to open an issue on GitHub.

Recently shipped

  • Public REST API v1 (stable since 3.2): bearer-token auth, read and write scopes, content CRUD across five types, asset uploads, and per-URL sitemap controls.
  • MCP server v0.2: 11 tools covering article and page CRUD, a publish toggle, and content search, so an AI agent edits a site directly.
  • Origami runtime: versioned, symlink-swapped releases with checksum-gated, one-command rollback.
  • Routing and sitemap correctness hardened across the 3.3.x line.

Planned

These are agreed in direction and waiting on implementation.

  • More MCP tools: delete_page, read_resource for the generated llms.txt and sitemap.xml, and binary image upload over MCP.
  • Git-push webhook: resource subscriptions so an external system can react when content changes.
  • Per-endpoint rate limiting on the public API.
  • A single standardized error shape across all public endpoints.

Exploring

Earlier-stage ideas under consideration, not yet committed.

  • Remote MCP (SSE): an optional hosted transport for editing several sites from one place, alongside the local stdio server.
  • A multi-tenant content service for teams running many Bird CMS sites.

How to shape it

Bird CMS is open source under the MIT license. If something here matters to you, or something you need is missing, open an issue or a discussion on GitHub. Shipped work lands in the changelog.