Inhalt
The CMS your AI tools can run.
Inhalt is an open-source, MCP-native CMS. Instead of clicking through a traditional admin UI, the content layer is exposed through the Model Context Protocol (MCP). Any MCP client connects to the Inhalt server and you create and edit content just by chatting.
The protocol is the API. The client reads your content schema, finds the right entry, and proposes a clean, typed patch against real fields, never freeform text.
- Website: inhalt.tech
- MCP endpoint:
https://inhalt.tech - License: MIT
- Self-hostable: one container, your database, your keys. A hosted edge is also available.
How it works
Three steps.
- Connect the endpoint. Add one block to your MCP config. Inhalt exposes your whole content tree as typed tools.
- Operate on content. The client reads the schema, finds the right entry, and proposes a clean patch against real, typed fields.
- Save and publish. Every change is checked against your schema, saved, and pushed to your live read API in one step.
See docs/getting-started.md for the MCP config and a full walkthrough.
Features
| Feature | Description |
|---|---|
| MCP-native | The protocol is the API. Read, query, and patch content through tools any client already understands. |
| Typed schemas | Model content once. Clients work strictly inside your fields, validated and never freeform. |
| Drafts and review | Stage edits, preview them, and publish only when they are ready. |
| Headless delivery | Query from anywhere over a clean, fast read API. |
| Scoped access | Grant a client exactly the entries and actions it should touch. |
| Self-host | One container, your database, your keys. MIT licensed, end to end. |
Supported clients
Inhalt works with every MCP client, including Claude, Cursor, VS Code, Zed, Windsurf, and Cline.
Documentation
- Getting started - connect an MCP client and operate on content.
- Concepts - projects, content types, entries, and the draft/publish model.
- API reference - the Read API and MCP API.
- Development - run the repo locally, environment, and scripts.
- Code organization - project layout and where new code goes.
- Copy & tone - writing guidelines for product copy.
- Roadmap - planned work (auth, self-host).
No comments yet
Be the first to share your take.