Content

Available Tools

Content Type Management

• get-type-mapi – Get a specific content type by codename
• list-content-types-mapi – List all content types in the environment
• add-content-type-mapi – Create a new content type with elements

Content Type Snippet Management

• get-type-snippet-mapi – Get a specific content type snippet by codename
• list-content-type-snippets-mapi – List all content type snippets
• add-content-type-snippet-mapi – Create a new content type snippet

Taxonomy Management

• get-taxonomy-group-mapi – Get a specific taxonomy group by codename
• list-taxonomy-groups-mapi – List all taxonomy groups
• add-taxonomy-group-mapi – Create a new taxonomy group with terms

Content Item Management

• get-item-mapi – Get a specific content item by codename
• get-item-dapi – Get a content item by codename from Delivery API
• get-variant-mapi – Get a language variant of a content item
• add-content-item-mapi – Create a new content item (structure only)
• update-content-item-mapi – Update an existing content item by codename (name, collection)
• delete-content-item-mapi – Delete a content item by codename
• upsert-language-variant-mapi – Create or update a language variant with content
• delete-language-variant-mapi – Delete a language variant of a content item

Asset Management

• get-asset-mapi – Get a specific asset by codename
• list-assets-mapi – List all assets in the environment

Language Management

• list-languages-mapi – List all languages configured in the environment

Configuration

The server requires the following 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>"
      }
    }
}

SSE Transport

For SSE transport, first start the server:

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

With environment variables in a .env file, or otherwise accessible to the process:

KONTENT_API_KEY=<management-api-key>
KONTENT_ENVIRONMENT_ID=<environment-id>
PORT=3001  # optional, defaults to 3001

Then configure your MCP client:

{
  "kontent-ai-sse": {
    "url": "http://localhost:3001/sse"
  }
}

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:sse  # For SSE transport
npm run start:stdio  # For STDIO transport

# Start the server with automatic reloading (no need to build first)
npm run dev:sse  # For SSE transport
npm run dev:stdio  # For STDIO 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 sse server:

npx @modelcontextprotocol/inspector

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

License

MIT