Let Your AI Agent Edit Your Website

With Bird CMS you do not log into a dashboard to publish. You tell your AI assistant what you want, and it writes the page. Content is markdown on disk, and the engine ships an MCP server and a REST API so the assistant you already use, like Claude or Cursor, edits the site directly. There is no built-in AI and no plugin: you bring the agent, Bird provides the interface.

Two operators, one site

Bird CMS is built around two operators working together:

• The non-technical person never opens a code editor. They describe what to publish, in plain language.
• The AI agent does the editing through MCP or the API, writing valid markdown and frontmatter to the right place.

How it works

• The engine includes a stdio MCP server with 11 tools: article and page CRUD, a publish toggle, and search. You point Claude Desktop, Cursor or Zed at it once.
• For non-AI integrations there is a REST API v1 with bearer-token auth.
• The agent writes content/articles/<category>/<slug>/index.md plus its meta.yaml, and the page is live instantly. There is no build or deploy step.

A real example

You type this to your assistant:

Write and publish a 700-word how-to about onboarding a new client on my Bird CMS site, in the blog category, with a short FAQ at the end. Publish it once it reads well.

The agent calls write_article, then publish, and the post appears on your site. You never touched a file.

Why it matters

• Speed. Content is live the moment the file exists. No build, no cache to purge, no deploy.
• AEO for free. Because the agent writes to the content contract, every page ships Schema.org, a sitemap and llms.txt automatically. That is what makes a site easy for AI answer engines to cite. See What is AEO?
• No lock-in. It is your agent and plain markdown files. Nothing proprietary sits between you and your content.

Bring your own agent

Bird CMS deliberately ships without a built-in AI: the in-engine content generator was removed in version 3.0. You connect the assistant you already trust, and the engine exposes a clean, native interface for it. If you want the human side of this, the non-coder guide shows the prompts; for the machine side, the agents guide lists every tool.

Frequently asked questions

Does Bird CMS include an AI agent?

No. It ships an MCP server and a REST API. You connect your own assistant, such as Claude or Cursor, which then reads, writes and publishes content directly.

What is MCP?

The Model Context Protocol is an open standard that lets AI clients call tools. Bird CMS ships an MCP server that exposes read, write, publish and search tools for your site, so an agent can edit it without any custom integration.

Do I need to be technical to use it?

No. After a one-time setup, you simply talk to your assistant in plain language. The non-coder guide has copy-paste prompts for publishing, editing and rolling back.

Is letting an agent edit my site secure?

The stdio MCP server is local-only, so file permissions are the security boundary. The REST API uses bearer tokens with read or write scopes, and drafts are never served until you publish them.

How is this different from the WordPress REST API?

On WordPress, agent editing means building an integration on top of the REST API and trusting a plugin. Bird CMS ships the MCP server and API in the engine, so the interface is there from the first request.