Smeldr is a content backend with a native AI interface. In fact, every interface.
Define your content model. Get typed lifecycle enforcement, MCP-native tooling, and a backend your AI agents can operate on directly. The same rules apply to everyone, including the AI. Agent context, state, and coordination are now built in.
Self-hosted. Open source. Zero runtime dependencies. Written in Go.
Why Smeldr
The project started as Forge CMS. The name was honest about what it did at the time.
But the framework grew into something the -cms label could not hold. Smeldr is not a CMS. It is the typed, stateful layer that agents read from, write to, and operate on via MCP. Content is the primary use case. Any typed, persistent state is valid.
The name comes from smelting: transformation under heat and pressure. The forge universe stays. The category label does not.
What has not changed
The vision. Have a conversation with your favorite agent. Smeldr does the rest.
The framework. The architecture. The API. Version numbering continues without a reset. Smeldr is not a new product. It is a sharper name for the product that already exists.
forge-cms.dev redirects to smeldr.dev. Old module paths will continue to resolve. The codebase is the same codebase.
Where to find it
- smeldr.dev - documentation, guides, and a live demo
- github.com/smeldr - all modules, open source under AGPL
- @getsmeldr on X
- @smeldr@mastodon.social on Mastodon