Create cloud servers with ease, enjoy full control, automated backups, secure networking, and reliable support.
About Boring CMS
Boring CMS is an open-source headless content management system that operates as a single Node.js process with a single SQLite file per project. It provides a REST API and an MCP server for programmatic access, enabling both human editing via an admin UI and AI agent interactions. The system supports scheduled publishing, webhooks, and per-project OpenAPI specifications. Content is structured into collections with custom fields, including text, markdown, number, boolean, date, JSON, image, relation, and counter types. Authentication is handled through passkeys, Google OAuth, or email/password, with API keys for scoped read/write access and rate limiting. Media can be stored locally or on S3-compatible services like R2 or MinIO. Data export and import are supported in JSON and CSV formats, with dry-run previews available.
Key features
- Single Node process and SQLite file per project
- REST API with Bearer key authentication and ETag caching
- MCP server for AI agent integration
- Collections with custom fields and field-level revisions
- Scheduled publishing and webhooks
- JSON and CSV import/export with dry-run preview
- Media storage on local disk or S3-compatible services
- Passkeys, Google OAuth, and email/password authentication
Use cases
- Hosting a static website with dynamic content management
- Managing blog articles, authors, and categories via API
- Enabling AI agents to read and write content programmatically
Pros
- Single Node process and SQLite file per project
- Zero runtime dependencies beyond Node.js
- Supports both REST API and MCP server for AI agents
- Built-in authentication with passkeys, OAuth, and API keys
- Scheduled publishing, webhooks, and OpenAPI spec generation
Cons
- Requires Node.js installation
- No built-in multi-user collaboration features
- Media storage limited to local disk or S3-compatible services
Frequently asked questions about Boring CMS
What is Boring CMS?
Boring CMS is an open-source headless content management system that runs as a single Node.js process with a single SQLite file per project. It allows users to define collections and fields, edit content via an admin UI, and access content through a REST API or an MCP server.
Is Boring CMS free to use?
Yes, Boring CMS is free and MIT licensed. It can be self-hosted and installed via npm using the command 'npx boring-cms' or by cloning the GitHub repository.
What are the system requirements to run Boring CMS?
Boring CMS requires a recent version of Node.js. It uses the built-in node:sqlite module, so no additional database installation is needed. A small VPS with 1 GB of RAM is sufficient for operation.
How do AI agents interact with Boring CMS?
Each project in Boring CMS exposes an MCP endpoint at /mcp/. Users can create an API key, paste the provided MCP configuration into their client, and enable the agent to read or write entries within the key's scope. All agent edits are recorded as revisions that can be reverted.
Who currently uses Boring CMS?
The Tech Basket runs its website on Boring CMS. The articles and content on the site are managed through a Boring CMS project and served via its content API.
Does Boring CMS support media storage options?
Yes, media can be stored either locally on disk or on any S3-compatible storage service such as R2 or MinIO.