Inhalt - MCP-native CMS

Inhalt The CMS your AI tools can run.

Community: Submitted by a user or imported; check the owner before granting accessDegradedNo sign-inGlobalFreeCan modify data

What it can do

  • Schema.Read: List the project's content types and their typed field definitions.
  • Schema.Create: Define a new content type. `fields` is an array of typed field definitions (string, richtext, reference, enum, list). A richtext field takes an optional `format`: html (default), markdo
  • Schema.Update: Update a content type's name and/or fields. The key is immutable. Editing fields does not migrate existing entries.

What data it sees

Do you need an account

No: the server works without sign-in

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 to connect

How to connect Inhalt - MCP-native CMS to Claude

The server address to paste into Claude settings:

https://inhalt--meduard-krasniqi.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Inhalt - MCP-native CMS to ChatGPT

The server address to paste into ChatGPT settings:

https://inhalt--meduard-krasniqi.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Inhalt - MCP-native CMS to Cursor

The server address to paste into Cursor settings:

https://inhalt--meduard-krasniqi.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (11)

Raw names from tools/list. Only developers need these.

schema.readList the project's content types and their typed field definitions.
schema.createDefine a new content type. `fields` is an array of typed field definitions (string, richtext, reference, enum, list). A richtext field takes an optional `format`: html (default), markdown, or plaintext.
schema.updateUpdate a content type's name and/or fields. The key is immutable. Editing fields does not migrate existing entries.
schema.deleteDelete a content type. This permanently removes the type and every entry it holds.
entries.listList entries of a content type. Optionally filter by status and paginate.
entries.queryFind entries whose typed fields match the given values (matched against the working draft).
entries.getFetch one entry by slug. `view` selects the draft (default) or published copy.
entries.createCreate a new draft entry. `data` is validated against the content type's fields.
entries.patchApply a typed patch to an entry's working draft. Only the given fields change.
entries.publishPublish an entry: copy its working draft to the published copy served by the read API.
entries.deleteDelete an entry permanently.