# Kontent.ai MCP for AI Agents AI Agent Connect

> Kontent.ai (Enterprise Headless CMS) lets you manage your entire content lifecycle through natural conversation. You can create items, update language variants, audit schemas, and publish content to your delivery APIs without leaving your AI client. It puts your enterprise CMS under your agent's control, making it way easier to handle complex content structures and multi-language workflows.

## Overview
- **Category:** collaboration
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_ooA5rzXFtX2VlU5zvxQglzTdCam5cEL0LSqso5sU/ai-agent-connect
- **Tags:** content-orchestration, enterprise-cms, content-lifecycle, language-variants, content-delivery

## Description

This Connector connects your Kontent.ai project to your AI client so you can handle enterprise content orchestration without jumping between tabs. Instead of clicking through a complex UI to find a specific content container, you just tell your agent what needs to happen. You can build out top-level item shells, update specific fields for different languages, and move things into draft status for review. It handles the heavy lifting of navigating nested taxonomies and inspecting content type definitions so you don't have to memorize every field name. If you're looking for a way to make your content lifecycle more fluid, this is how you do it. By using the Vinkius catalog to host this connection, you get a reliable way to bridge your CMS and your AI agent. You can audit your media assets to get exact cloud URLs or transition variants to a published status to go live instantly. It turns a manual, multi-step process into a direct conversation.

## Tools

### upsert_item
Create or update a top-level content item container. This sets up the shell for your content.

### get_item
Get metadata for a specific Kontent.ai item using its codename. This helps you quickly check what's inside a container.

### get_taxonomy
Fetch details and nested terms for a specific Taxonomy group. Use this to understand how your tags are organized.

### get_content_type
Pull the exact structural fields of a specific Content Type. This is perfect for verifying your schema.

### list_assets
See a list of all uploaded Media Assets and Document files. It's the fastest way to grab cloud URLs.

### list_items
View every content item currently in your Kontent.ai environment. Use this to get a bird's-eye view of your project.

### list_taxonomies
Browse all hierarchical Taxonomies like tags or categories. This helps you see your full organizational structure.

### list_content_types
See all Content Type schemas registered in your environment. It lets you audit your available content structures.

### publish_variant
Move a specific language variant to the Published status. This makes your content live on your delivery APIs immediately.

### upsert_language_variant
Update the actual content fields for a specific language. This is how you change the text people actually read.

## Prompt Examples

**Prompt:** 
```
What are the fields for our 'Product' content type?
```

**Response:** 
```
The 'Product' content type (codename: product) includes the following structural fields:

| Field Name | Type | Description |
| :--- | :--- | :--- |
| **title** | Text | The main product name |
| **description** | Rich Text | Detailed product specs |
| **price** | Number | Current MSRP |
| **sku** | URL Slug | Unique identifier |
| **hero_image** | Asset | Main product photo |

Would you like me to create a new item using this schema?
```

**Prompt:** 
```
Update the Portuguese text for the 'homepage' item.
```

**Response:** 
```
I've updated the content fields for the Portuguese variant of the 'homepage' item. The changes are now saved in **Draft** status. Would you like me to publish this variant now?
```

**Prompt:** 
```
List all my media assets.
```

**Response:** 
```
I've retrieved your uploaded media assets:

*   **banner_01.jpg** (ID: img_992) - [Cloud URL]
*   **product_demo.mp4** (ID: vid_441) - [Cloud URL]
*   **logo_final.png** (ID: img_102) - [Cloud URL]

Let me know if you need the specific identifier for any of these.
```

## Capabilities

### Create content shells
Generate new top-level items with specific codenames and types.

### Update language variants
Change content fields for specific regions like English or Portuguese.

### Publish live content
Move variants from draft to published status for immediate delivery.

### Audit content schemas
Inspect Content Type definitions to see all available fields and blocks.

### Manage taxonomy groups
Organize and filter assets using hierarchical tags and categories.

### Retrieve media URLs
Get precise cloud identifiers for uploaded documents and images.

## Use Cases

### Updating localized landing pages
A content editor needs to update the Portuguese version of a landing page. They ask the agent to update the Portuguese variant of the 'homepage' item using upsert_language_variant.

### Verifying content schemas
A developer needs to check the fields for a new blog post type. They ask the agent to list the fields for the 'Article' content type using get_content_type.

### Auditing taxonomy trees
An architect needs to see all available tags. They ask the agent to list all taxonomies to audit the current organizational structure.

### Gathering media assets
A marketer wants to see all images in the project. They ask the agent to list assets to gather cloud URLs for a new campaign.

## Benefits

- Skip the CMS UI login. You can update content and publish variants directly through your AI client, saving time on navigation.
- Faster localization workflows. Use upsert_language_variant to update specific regions without hunting for the right fields.
- Instant schema verification. Use get_content_type to check fields and blocks, ensuring your data always matches your requirements.
- Easy media auditing. Quickly grab cloud URLs and identifiers with list_assets to keep your frontend team happy.
- Better taxonomy management. Organize and filter assets using list_taxonomies to keep your content structure clean.
- Automated publishing. Transition variants to Published status using publish_variant to go live without manual clicks.

## How It Works

The bottom line is you get a direct conversational bridge to manage your entire headless CMS lifecycle.

1. Connect your Kontent.ai Environment ID and Management API Key to the Connector.
2. Open your preferred AI client and describe the content change you need.
3. Receive the updated status or the specific metadata you requested.

## Frequently Asked Questions

**Can the Kontent.ai MCP update multiple languages at once?**
Yes, it can update specific fields for different languages one by one or in sequence, making it easy to manage multi-region content.

**Does the Kontent.ai MCP help with publishing content?**
Yes, you can move variants from Draft to Published status to make them live on your delivery APIs immediately.

**Can I use the Kontent.ai MCP to check my content schema?**
Yes, it lets you inspect Content Type definitions to see exactly which fields and blocks are available in your project.

**How does the Kontent.ai MCP handle media?**
It can list all your uploaded media assets and documents so you can get their cloud URLs quickly without browsing the dashboard.

**Is the Kontent.ai MCP good for large enterprise CMS projects?**
Yes, it's designed for enterprise-grade headless CMS environments with complex taxonomy and content orchestration needs.

**Can I use the Kontent.ai MCP to organize my tags?**
Yes, it lets you manage and list all your hierarchical taxonomy groups to keep your assets organized and easy to filter.

**Can I update the actual text of an item using my agent?**
Yes. Use the `upsert_language_variant` tool. While `upsert_item` creates the container, the variant tool allows you to populate the specific content fields (`elements`) for a given language, placing the item into Draft status.

**How do I make my draft content live on the website?**
The `publish_variant` tool transitions a specific language variant from Draft to Published. This makes the content immediately accessible to your frontend applications via the public Delivery APIs.

**Can my agent help me understand which fields are in a content model?**
Absolutely. Use the `get_content_type` tool by providing the type codename. Your agent will perform a schema introspection and list all available elements, allowing you to understand the exact structure you need to populate.