Introducing Squilla
An AI-native CMS for the agentic era.
Squilla is a CMS designed around an idea that wasn't possible until very recently: that an AI agent should be able to build, populate, and operate an entire website with no human in the loop. That sounds like marketing copy, so here's what we mean by it concretely.
What an agent can do today
Out of the box, an MCP-connected agent can register custom node types, seed pages and posts, activate themes and extensions, render previews, manage menus, upload media, and iterate on content blocks — all through structured tool calls. There are roughly 50 of those tools across 15 domains, every one of them with a typed schema and a capability scope. The whole CMS is, deliberately, a structured surface.
Why now
Two trends collided. First, AI coding assistants and content agents got good enough at structured tasks that the bottleneck became tool quality — not model capability. Second, the Model Context Protocol gave us a portable, standard way to expose those tools. Most existing CMSes offer either a JSON REST API or a tangle of admin URLs; neither is a great surface for an agent. MCP is.
Why kernel + extensions
If we're going to build a CMS specifically for agentic workflows, we want the smallest possible kernel and the most aggressive separation of concerns. So Squilla is built like Linux + Debian: a tiny kernel that handles content nodes, rendering, auth, the CoreAPI, and the event bus; and sovereign extensions that own their full stack — their own tables, their own admin micro-frontend, their own migrations, their own scripts. Disable any extension and the kernel keeps serving content.
What's in v0.1.0
The first public preview ships the kernel, the MCP server, the VDUS admin shell, seven reference extensions (media-manager, forms, email-manager, sitemap-generator, content-blocks, resend-provider, smtp-provider), and the Squilla theme rendering this site. The full source is on GitHub at github.com/erikkubica/squilla. GPL-3.0. No telemetry. No CLA.
What's next
More extensions, more themes, page-level content versioning, richer i18n primitives, and a public extension marketplace. The roadmap is in the repo — contributions welcome.