# Contentstack MCP for AI Agents AI Agent Connect > Contentstack MCP lets you manage your headless CMS directly through your AI agent. List and create content entries, audit schemas, handle media assets, and push updates to production or staging environments without switching tabs. It connects your content repository to your daily workflow, making it easier to update products, manage blog posts, and verify schema rules in real time. ## Overview - **Category:** content-management - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_LHpjNg6KYihBgS2kLX19DNVRW2vIuyS9J01Esg29/ai-agent-connect - **Tags:** digital-experience, content-orchestration, asset-management, workflow-automation, headless-cms ## Description This Contentstack MCP brings your headless CMS content directly into your AI chat. Instead of jumping between your CMS dashboard and your code editor, you can now ask your agent to find specific blog posts, draft new product pages using your existing schema, or grab URLs for images you need in your frontend. It handles the heavy lifting of interacting with the backend so you don't have to worry about manual data entry or navigating complex menus. Whether you're auditing global schemas to see what fields are available or cleaning up old app nodes to save on storage, this connection makes the CMS feel like a native part of your workspace. It's one of the many tools you can find in the Vinkius catalog to bridge the gap between your content repository and your development workflow. You get to move faster because your agent understands the boundaries of your data and the specific requirements of your environments. You can quickly verify publication statuses or check content models for new digital experiences without ever leaving your primary workspace. This setup removes the friction of context switching and lets you focus on the actual content strategy rather than the mechanics of the database. ## Tools ### create_cms_entry Generate new Contentstack drafts using a JSON payload. This makes it easy to build content at scale. ### get_schema_details Extract the properties and validation rules for active fields. This helps you understand the database requirements. ### get_single_entry Retrieve specific cloud logs and data for a unique Entry UUID. Use this to pull detailed information for a single item. ### list_media_assets Browse internal arrays to find media files and metadata. It helps you find assets without manual searching. ### list_global_schemas List all structured rules and active content types. Use this to audit your content models across the stack. ### list_type_entries Find all entries within specific bounded routing spaces. This helps you see what content is available in specific categories. ### update_cms_entry Safely overwrite draft values and schema blocks for existing entries. Use this to make quick updates to your content. ### wipe_cms_entry Permanently delete live document rows and app nodes. Use this to clear out old data and manage your quota. ### get_media_asset Fetch specific structural data for a given Media ID. It helps you get the exact file details you need. ### publish_to_environment Route CMS data to production, staging, or development environments. This automates the move from draft to live. ## Prompt Examples **Prompt:** ``` List all entries for content type 'homepage' ``` **Response:** ``` I found 3 entries for 'homepage'. The latest is **Main Homepage v2** (UID: entry_123). Would you like to see the draft values for this entry or move it to a different environment? ``` **Prompt:** ``` Publish entry 'entry_456' of type 'blog_post' to production ``` **Response:** ``` Publishing request sent! **'entry_456'** is now being pushed to the **production** environment. I will notify you once the sequence is complete. ``` **Prompt:** ``` Show me the details for content model 'product_schema' ``` **Response:** ``` Retrieving schema for **'product_schema'**... This model includes the following fields: - **product_name**: Text - **sku**: Symbol - **price**: Number - **gallery**: File Reference I can decode the specific validation rules for any of these if you need them. ``` ## Capabilities ### Create new content drafts Generate new content entries using JSON payloads directly through your agent. ### Update existing CMS entries Modify draft values and schema blocks for content that is already in your system. ### Publish content to specific environments Move your content from drafts to production, staging, or development environments. ### Inspect global content schemas View the fields and validation rules that define your content models. ### Retrieve media asset metadata Pull URLs and specific metadata for images and files stored in your CMS. ### Delete old app nodes and rows Remove legacy data and app nodes to manage your storage and clear your quota. ## Use Cases ### Updating multiple product descriptions A content manager needs to update 50 product descriptions. They ask the agent to use update_cms_entry to batch the changes across the stack. ### Verifying schema fields during dev A developer is stuck on a field type. They use get_schema_details to see the validation rules and data types without leaving their IDE. ### Moving a blog post to production A team lead needs to move a blog post to live. They ask the agent to use publish_to_environment to trigger the sequence to the production environment. ### Cleaning up legacy stack data A digital ops person needs to clear out old data to save on storage. They use wipe_cms_entry to remove old nodes and live rows. ## Benefits - Move from drafting to production faster by using publish_to_environment to push data without manual clicks. - Stop guessing content structures by using get_schema_details to see exactly what fields your agent needs to fill. - Reduce manual asset hunting by using list_media_assets to pull URLs and metadata directly into your project. - Keep your CMS clean and within quota by using wipe_cms_entry to remove old nodes and live rows. - Create content at scale by using create_cms_entry to generate drafts based on specific JSON attributes. - Simplify cross-team communication by using list_global_schemas to audit the content model for everyone. ## How It Works The bottom line is you get a direct line to your headless CMS data without the manual overhead of switching tabs. 1. Subscribe to this Connector through the Vinkius marketplace. 2. Provide your Contentstack Stack API Key and Management Token. 3. Start asking your AI client to manage content, fetch schemas, or publish updates. ## Frequently Asked Questions **Can I use Contentstack MCP to update my live website?** Yes. You can use the Connector to update content entries and then use the publish tool to move those changes to your live production environment. **How does Contentstack CMS help my dev team?** It allows developers to pull schema details and media assets directly into their workflow, ensuring that the frontend code always matches the CMS data structure. **Can Contentstack MCP manage my images?** Yes, it can list your media assets and retrieve specific metadata and URLs for individual files, making it easier to manage your library. **Is Contentstack CMS safe for production?** Yes. The Connector allows you to target specific environments, so you can safely manage staging and production data without mixing them up. **How do I use Contentstack MCP to find content?** You can simply ask your AI agent to list entries for a specific content type or find a single entry by its unique ID. **Can I use Contentstack MCP to audit my schemas?** Yes. You can ask the agent to enumerate all global schemas to see the rules and field types currently in your stack. **Can my agent create new entries in Contentstack?** Yes. Use the 'create_cms_entry' tool. Provide the content type UID and a JSON object containing the entry fields. The agent will orchestrate the absolute explicit bindings to generate a new draft in your stack. **How do I publish an entry to multiple environments via chat?** Use the 'publish_to_environment' tool. Provide the content type UID, the entry UID, and a comma-separated list of environments (e.g., 'production,staging'). The agent will trigger the exact sequence to push your data live. **Can I inspect the fields and validation rules of a content type?** Absolutely. The 'get_schema_details' tool retrieves the structural extraction of properties for a specific content type UID, showing you exactly which fields are required and what data the database expects.