Kontent.ai MCP. Control content publishing from your chat client.
Kontent.ai (Enterprise Headless CMS) MCP lets you manage complex enterprise content workflows directly through your AI client. You can audit schemas, create new content containers, update specific language texts for items, and push variants live—all without logging into the Kontent UI.
Give Claude and any AI agent real-world access
Inspect available fields and structural requirements for any registered content type.
List existing content items or create/update the top-level containers that hold all your content.
Change specific text fields for a single language (like Portuguese) within an item, moving it to Draft status automatically.
Transition specific content variants from Draft into Published status, making them instantly available on the front end.
List all organizational tags or audit uploaded media files to get their precise identifiers and cloud URLs.
Ask an AI about this
Waiting for input…
What AI agents can do with Kontent.ai (Enterprise Headless CMS) 10 Tools
Use these tools to read the structure of your content types, list assets, manage taxonomies, or perform full content writes and publications via your AI agent.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Kontent.ai (Enterprise Headless CMS) MCPGet Item
Retrieves the metadata for a single piece of content using its unique codename.
Get Taxonomy
Fetches detailed information, including all nested terms, for a specific...
Get Content Type
Retrieves the precise structural definition and required fields for any content type...
List Assets
Lists all uploaded media files and documents, providing their identifiers and cloud...
List Items
Retrieves a list of every top-level content container present in the Kontent.ai...
List Taxonomies
Lists all available hierarchical taxonomy groups, similar to site tags or categories.
List Content Types
Retrieves a list of every content type schema defined and registered in the environment.
Publish Variant
Changes a specific language variant's status from Draft to Published, making the...
Upsert Item
Creates or updates the top-level container for a piece of content without changing...
Upsert Language Variant
Updates the actual body copy and structured data elements for an item, placing the...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Kontent.ai (Enterprise Headless CMS), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kontent.ai. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Managing content across different languages and versions used to be an administrative nightmare.
Today's process involves logging into a CMS, navigating deep menu structures, manually switching between tabs for English, German, Spanish, and Japanese. You copy the item codename from one screen, paste it into another form, update the text block, then repeat the whole tedious cycle for every single language variant.
With this MCP, your agent handles the complexity. You simply tell your client to 'Update the body copy for German' on a specific article. The system finds the right item, targets the correct language variant, updates the content, and leaves it in Draft status—all without you clicking anything.
Kontent.ai MCP gives your agent granular control over every piece of metadata.
You no longer have to guess what data fields are available or where an asset lives. You can ask the system to run `get_content_type` to map out every required field, or use `list_assets` to get a definitive list of all media IDs needed for your site build.
This shift means you move from being limited by the UI's flow to having total conversational control. You define the process—from schema discovery to final publication—and it executes.
What Kontent.ai MCP does for your AI
This MCP gives your agent full control over your Kontent.ai CMS. Instead of clicking through menus to manage content, you talk to it. You can discover exactly what fields a piece of content needs by inspecting content type definitions. Need to update text for one language? Your agent handles the upsert_language_variant call and places that version into Draft status immediately.
When everything is ready, running the publish workflow transitions those specific variants to Published, making them live via your delivery APIs—all in a conversation. Connecting this MCP through Vinkius means you connect once from Claude, Cursor, or any compatible client and get access to this entire content lifecycle management system.
019d75c3-18b2-70e9-9c9d-02c1ab53a724 How to set up Kontent.ai MCP
The bottom line is that you manage your entire content lifecycle through natural conversation, never needing to touch the Kontent UI again.
Subscribe to this MCP, providing your Kontent.ai Environment ID and Management API Key.
Your agent connects using these credentials, granting it full programmatic access to the CMS backend.
You issue a command—for example, 'Update the article body for English'—and the system executes the necessary content writes or publishes.
Who uses Kontent.ai MCP
Content Architects and Digital Editors need this. They're tired of juggling multiple browser tabs, manually copying asset IDs, and waiting for a developer to make small content updates. This MCP lets them manage the entire publishing workflow right where they work.
Needs to update localized body copy or change metadata across dozens of articles quickly, ensuring each language variant is correctly drafted before review.
Must audit the entire content type schema and taxonomy tree across multiple projects to ensure consistency before a new feature launches.
Requires listing uploaded media assets or inspecting content types to verify field names and asset identifiers for accurate mapping in their downstream applications.
Benefits of connecting Kontent.ai MCP
Go beyond simple content updates. You can audit the full schema using get_content_type and verify exactly what fields are available before writing any code.
Never worry about stale links again. Use list_assets to get precise identifiers and cloud URLs for all media, ensuring your frontend always points to the right source.
Manage content status changes instantly. Instead of manually updating a variant in the UI, calling publish_variant moves the item live with one command.
Maintain multilingual integrity easily. You can run upsert_language_variant to update text for Portuguese or French without affecting the English copy or leaving the record un-drafted.
Audit your entire site structure by using list_taxonomies and list_content_types. This helps content architects verify that all necessary organizational tags exist across environments.
Kontent.ai MCP use cases
Preparing a Global Launch Campaign
The marketing team needs to launch an article in five languages. They first use list_items to find the main container, then call upsert_language_variant for each language's copy, and finally run publish_variant sequentially for all versions to ensure a perfect, simultaneous global rollout.
Debugging a Broken Homepage Feature
The developer realizes the homepage hero image is using an outdated asset. They use list_assets to get the current identifier and then pass that ID into the content type schema check using get_content_type before updating the item container via upsert_item.
Auditing Content Schema Drift
The content architect needs to verify if a new department has added mandatory fields to the 'Article' type. They call get_content_type and compare the returned structure against known schemas, ensuring no required element is missing.
Mass Content Migration
The team needs to update five different content items (using get_item first) and change their associated category tags. They use upsert_language_variant for the text changes, followed by calls to ensure the correct taxonomy groups are assigned.
Kontent.ai MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming content is live
A developer updates a language variant using upsert_language_variant and assumes it's ready for production, but forgets to run the publishing step.
Always follow up any text update with a call to publish_variant. The upsert_language_variant function only places content into Draft status; you must explicitly transition it using publish_variant.
Updating without knowing the structure
A user tries to add a custom field (e.g., 'Product SKU') to an article because they think it should be there, but doesn't know if the content type supports it.
First, run get_content_type on the specific schema. This call provides the definitive list of available fields and parameters, preventing data errors.
Updating everything at once
Trying to update an item container (upsert_item) but also changing its text content in the same command, which can lead to overwrites or failure.
Keep your actions separate. Use upsert_item only when modifying the shell/metadata, and use upsert_language_variant only for touching the actual body copy.
When to use Kontent.ai MCP
Use this MCP if your core problem involves managing complex content lifecycles across multiple languages or environments. Specifically, you need to audit structured data (like field schemas via get_content_type), manage versioning, and programmatically publish content status (Draft to Published). Don't use this if all you need is a simple key-value store connection; for that, an object database connector would be better. Also, don't use it if your only goal is retrieving a list of items—while list_items works, remember that the real power comes from the subsequent actions like updating variants or publishing.
Frequently asked questions about Kontent.ai MCP
How do I publish an item using Kontent.ai MCP? +
You use the publish_variant tool. This function takes a specific content container and language variant, changing its status from Draft to Published so it's live on your delivery APIs.
What is the difference between list_items and list_content_types in Kontent.ai MCP? +
list_items gives you a roster of actual content pieces (e.g., 'About Us'). list_content_types tells you about the structure of content, like defining that every article must have a 'title' and 'body'.
Can I update text for only one language using Kontent.ai MCP? +
Yes, absolutely. You use upsert_language_variant. This tool lets you target the actual content fields of an item while specifying exactly which language (e.g., Portuguese) needs updating.
Does Kontent.ai MCP help me find asset IDs? +
Yes, running list_assets will retrieve a list of all uploaded media and document files, providing you with the necessary cloud URLs and identifiers needed for your frontend applications.
What should I do if I need to create a new piece of content? +
First, run upsert_item to create the top-level container. Then, use upsert_language_variant for each language's text, and finally publish it.