Inhalt

io.github.kozmos-techPublished by GitHub account kozmos-techv0.1.1Updated Oct 27, 2026

An open-source headless CMS for managing content models and entries.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Inhalt is an open-source, MCP-native headless CMS that lets an assistant read, query and patch typed content entries by chatting instead of using an admin UI.

What you can do
  • Read the content schema and content tree exposed as typed tools
  • Find entries and query content through the MCP tools
  • Propose and apply typed patches against real fields, validated against the schema
  • Stage drafts, preview edits and publish changes to the live read API
  • Scope which entries and actions a given client may touch
When to use it
Useful when you run a headless CMS and want an assistant to edit or publish content directly, with schema validation and a draft/publish step, rather than clicking through an admin panel.
Requirements
An MCP client configured with the Inhalt endpoint (the README lists a hosted endpoint and a self-hostable single container with your own database and keys). No authentication is declared in the manifest, and the README roadmap lists auth as planned work.
Before you install
The server writes content: edits are saved and can be pushed to the live read API, so review drafts before publishing. The README roadmap lists auth as planned, so access control may be incomplete; use scoped access and self-hosting with your own keys where content is sensitive.

Installation

In SourceWeft

  1. Open Inhalt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

  1. Connect the endpoint. Add one block to your MCP config. Inhalt exposes your whole content tree as typed tools.
  2. Operate on content. The client reads the schema, finds the right entry, and proposes a clean patch against real, typed fields.
  3. 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

FeatureDescription
MCP-nativeThe protocol is the API. Read, query, and patch content through tools any client already understands.
Typed schemasModel content once. Clients work strictly inside your fields, validated and never freeform.
Drafts and reviewStage edits, preview them, and publish only when they are ready.
Headless deliveryQuery from anywhere over a clean, fast read API.
Scoped accessGrant a client exactly the entries and actions it should touch.
Self-hostOne 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

License

MIT

Source: README.md at commit 2cd2c6e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts