Kontent.ai MCP Server

Transform your content operations with AI-powered tools for Kontent.ai. Create, manage, and explore your structured content through natural language conversations in your favorite AI-enabled editor.

Kontent.ai MCP Server implements the Model Context Protocol to connect your Kontent.ai projects with AI tools like Claude, Cursor, and VS Code. It enables AI models to understand your content structure and perform operations through natural language instructions.

✨ Key Features

• 🚀 Rapid prototyping: Transform your diagrams into live content models in seconds

• 📈 Data Visualisation: Visualise your content model in any format you want

Table of Contents

• ✨ Key Features

• 🔌 Quickstart

• 🛠️ Available Tools

• ⚙️ Configuration

• 🚀 Transport Options

• 💻 Development

  • 🛠 Local Installation

  • 📂 Project Structure

  • 🔍 Debugging

  • 📦 Release Process

• License

🔌 Quickstart

🔑 Prerequisites

Before you can use the MCP server, you need:

1. A Kontent.ai account - Sign up if you don't have an account.

2. A project - Create a project to work with.

3. Management API key - Create a key with appropriate permissions.

4. Environment ID - Get your environment ID.

🛠 Setup Options

You can run the Kontent.ai MCP Server with npx:

STDIO Transport

npx @kontent-ai/mcp-server@latest stdio

Streamable HTTP Transport

npx @kontent-ai/mcp-server@latest shttp

🛠️ Available Tools

Patch Operations Guide

• get-patch-guide – 🚨 REQUIRED before any patch operation. Get patch operations guide for Kontent.ai by entity type

Content Type Management

• get-content-type – Get Kontent.ai content type by ID

• list-content-types – Get all Kontent.ai content types

• create-content-type – Create new Kontent.ai content type

• patch-content-type – Update an existing Kontent.ai content type by codename using patch operations (move, addInto, remove, replace)

• delete-content-type – Delete a Kontent.ai content type by ID

Content Type Snippet Management

• get-content-type-snippet – Get Kontent.ai content type snippet by ID

• list-content-type-snippets – Get all Kontent.ai content type snippets

• create-content-type-snippet – Create new Kontent.ai content type snippet

• patch-content-type-snippet – Update an existing Kontent.ai content type snippet by ID using patch operations (move, addInto, remove, replace)

• delete-content-type-snippet – Delete a Kontent.ai content type snippet by ID

Taxonomy Management

• get-taxonomy-group – Get Kontent.ai taxonomy group by ID

• list-taxonomy-groups – Get all Kontent.ai taxonomy groups

• create-taxonomy-group – Create new Kontent.ai taxonomy group

• patch-taxonomy-group – Update Kontent.ai taxonomy group using patch operations (addInto, move, remove, replace)

• delete-taxonomy-group – Delete Kontent.ai taxonomy group by ID

Content Item Management

• get-content-item – Get Kontent.ai content item by ID

• get-content-item-variant – Retrieve Kontent.ai content item variant (language version/translation). Returns the current version — draft if one exists, otherwise published

• get-published-content-item-variant-version – Retrieve the published version of a Kontent.ai content item variant. Use when a newer draft version exists but you need the currently published (live) content

• get-content-item-translations – Get all Kontent.ai content item translations — every language version (variant) of a specific content item

• list-content-item-variants – List, filter, search Kontent.ai content items with content item variants (language versions/translations)

• create-content-item – Create new Kontent.ai content item (creates the container only, use create-content-item-variant to add language versions/translations)

• update-content-item – Update existing Kontent.ai content item by ID. The content item must already exist - this tool will not create new items

• delete-content-item – Delete Kontent.ai content item by ID

• create-content-item-variant – Create Kontent.ai content item variant assigning current user as contributor. Element values must fulfill limitations and guidelines defined in content type

• update-content-item-variant – Update Kontent.ai content item variant of a content item. Element values must fulfill limitations and guidelines defined in content type. Only provided elements will be modified

• create-new-content-item-variant-version – Create new version of Kontent.ai content item variant. This operation creates a new version of an existing content item variant, useful for content versioning and creating new drafts from published content

• delete-content-item-variant – Delete Kontent.ai content item variant

• bulk-get-content-item-variants – Bulk get Kontent.ai content items with their content item variants by item and language reference pairs. Use after list-content-item-variants to retrieve full content data for specific item+language pairs. Items without a variant in the requested language return the item without the variant property. Returns paginated results with continuation token

• search-content-item-variants – AI-powered semantic search for finding content by meaning and concepts in a specific content item variant. Use for: conceptual searches when you don't know exact keywords. Limited filtering options (variant ID only)

Asset Management

• get-asset – Get a specific Kontent.ai asset by ID

• list-assets – Get all Kontent.ai assets

• update-asset – Update Kontent.ai asset by ID

Asset Folder Management

• list-asset-folders – List all Kontent.ai asset folders

• patch-asset-folders – Modify Kontent.ai asset folders using patch operations (addInto to add new folders, rename to change names, remove to delete folders)

Language Management

• list-languages – Get all Kontent.ai languages (includes both active and inactive - check is_active property)

• create-language – Create new Kontent.ai language (languages are always created as active)

• patch-language – Update Kontent.ai language using replace operations (only active languages can be modified - to activate/deactivate, use the Kontent.ai web UI)

Collection Management

• list-collections – Get all Kontent.ai collections. Collections set boundaries for content items in your environment and help organize content by team, brand, or project

• patch-collections – Update Kontent.ai collections using patch operations (addInto to add new collections, move to reorder, remove to delete empty collections, replace to rename)

Space Management

• list-spaces – Get all Kontent.ai spaces

• create-space – Create new Kontent.ai space for managing a website or channel

• patch-space – Patch Kontent.ai space using replace operations

• delete-space – Delete Kontent.ai space

Role Management

• list-roles – Get all Kontent.ai roles. Requires Enterprise or Flex plan with "Manage custom roles" permission

Workflow Management

• list-workflows – Get all Kontent.ai workflows. Workflows define the content lifecycle stages and transitions between them

• create-workflow – Create new Kontent.ai workflow with custom steps, transitions, scopes, and role permissions

• update-workflow – Update an existing Kontent.ai workflow by ID. Modify steps, transitions, scopes, and role permissions. Cannot remove steps that are in use

• delete-workflow – Delete a Kontent.ai workflow by ID. The workflow must not be in use by any content items

• change-content-item-variant-workflow-step – Change the workflow step of a content item variant in Kontent.ai. This operation moves a content item variant to a different step in the workflow, enabling content lifecycle management such as moving content from draft to review, review to published, etc.

• publish-content-item-variant – Publish or schedule a content item variant of a content item in Kontent.ai. This operation can either immediately publish the variant or schedule it for publication at a specific future date and time with optional timezone specification

• unpublish-content-item-variant – Unpublish or schedule unpublishing of a content item variant of a content item in Kontent.ai. This operation can either immediately unpublish the variant (making it unavailable through the Delivery API) or schedule it for unpublishing at a specific future date and time with optional timezone specification

⚙️ Configuration

The server supports two modes, each tied to its transport:

Single-Tenant Mode (STDIO)

Configure credentials via environment variables:

Multi-Tenant Mode (Streamable HTTP)

For the Streamable HTTP transport, credentials are provided per request:

• Environment ID as a URL path parameter: /{environmentId}/mcp

• API Key via Bearer token in the Authorization header: Authorization: Bearer <api-key>

This allows a single server instance to handle requests for multiple Kontent.ai environments without requiring credential environment variables.

🚀 Transport Options

📟 STDIO Transport

To run the server with STDIO transport, configure your MCP client with:

{
  "kontent-ai-stdio": {
      "command": "npx",
      "args": ["@kontent-ai/mcp-server@latest", "stdio"],
      "env": {
        "KONTENT_API_KEY": "<management-api-key>",
        "KONTENT_ENVIRONMENT_ID": "<environment-id>"
      }
    }
}

🌊 Streamable HTTP Transport (Multi-Tenant)

Streamable HTTP transport serves multiple Kontent.ai environments from a single server instance. Each request provides credentials via URL path parameters and Bearer authentication.

First start the server:

npx @kontent-ai/mcp-server@latest shttp

Create a .vscode/mcp.json file in your workspace:

{
  "servers": {
    "kontent-ai-multi": {
      "uri": "http://localhost:3001/<environment-id>/mcp",
      "headers": {
        "Authorization": "Bearer <management-api-key>"
      }
    }
  }
}

For secure configuration with input prompts:

{
  "inputs": [
    {
      "id": "apiKey",
      "type": "password",
      "description": "Kontent.ai API Key"
    },
    {
      "id": "environmentId",
      "type": "text",
      "description": "Environment ID"
    }
  ],
  "servers": {
    "kontent-ai-multi": {
      "uri": "http://localhost:3001/${inputs.environmentId}/mcp",
      "headers": {
        "Authorization": "Bearer ${inputs.apiKey}"
      }
    }
  }
}

Update your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

• Linux: ~/.config/Claude/claude_desktop_config.json

Use mcp-remote as a proxy to add authentication headers:

{
  "mcpServers": {
    "kontent-ai-multi": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:3001/<environment-id>/mcp",
        "--header",
        "Authorization: Bearer <management-api-key>"
      ]
    }
  }
}

Add the server using the CLI:

claude mcp add --transport http kontent-ai-multi \
  "http://localhost:3001/<environment-id>/mcp" \
  --header "Authorization: Bearer <management-api-key>"

Note: You can also configure this in your Claude Code settings JSON with the url and headers properties.

💻 Development

🛠 Local Installation

# Clone the repository
git clone https://github.com/kontent-ai/mcp-server.git
cd mcp-server

# Install dependencies
npm ci

# Build the project
npm run build

# Start the server
npm run start:stdio  # For STDIO transport
npm run start:shttp  # For Streamable HTTP transport

# Start the server with automatic reloading (no need to build first)
npm run dev:stdio  # For STDIO transport
npm run dev:shttp  # For Streamable HTTP transport

📂 Project Structure

• src/ - Source code

  • tools/ - MCP tool implementations

  • clients/ - Kontent.ai API client setup

  • schemas/ - Data validation schemas

  • utils/ - Utility functions

    • errorHandler.ts - Standardized error handling for MCP tools

    • throwError.ts - Generic error throwing utility

  • server.ts - Main server setup and tool registration

  • bin.ts - Single entry point that handles both transport types

🔍 Debugging

For debugging, you can use the MCP inspector:

npx @modelcontextprotocol/inspector -e KONTENT_API_KEY=<key> -e KONTENT_ENVIRONMENT_ID=<env-id> node path/to/build/bin.js

Or use the MCP inspector on a running streamable HTTP server:

npx @modelcontextprotocol/inspector

This provides a web interface for inspecting and testing the available tools.

📦 Release Process

To release a new version:

1. Bump the version using npm version [patch|minor|major] - this updates package.json, package-lock.json, and syncs to server.json

2. Push the commit to your branch and create a pull request

3. Merge the pull request

4. Create a new GitHub release with the version number as both name and tag, using auto-generated release notes

5. Publishing the release triggers an automated workflow that publishes to npm and GitHub MCP registry

License

MIT