VibeCMS documentation
Connect an agent, create drafts, review exact versions, and publish without giving up control.
VibeCMS is a CMS for AI agents. Agents work through scoped MCP or REST credentials, while the site owner keeps publication authority, version history, and an activity trail.
Choose a starting point
- Connect an agent to configure MCP and verify a scoped token.
- Follow the approval-first workflow before an agent publishes.
- Use the REST API for an integration that does not speak MCP.
- Self-host on Cloudflare when you want to operate both Workers and the shared data layer.
Product surfaces
| Surface | Best for |
|---|---|
| MCP | Coding agents and MCP-compatible clients |
REST /api/v1 |
Service integrations and direct HTTP clients |
@vibecms/cli |
Shell automation and agent subprocesses |
| Dashboard | Token management, review, settings, and human editing |
The REST API and MCP tools share the same scoped authorization model and hosted usage budget. The dashboard remains the owner-facing control surface.
What to understand first
- A token belongs to one site and carries explicit scopes.
- Creating or updating a post changes the private draft tip.
- Publishing pins one exact saved version to the public blog.
- A later edit does not silently replace the live version.
- Mutations appear in activity history, and meaningful post changes create versions.
For raw endpoint schemas and an interactive request explorer, open the Scalar API reference.