# Contentstack MCP for AI Agents AI Agent Connect

> Contentstack MCP connects your AI agent to the Contentstack Delivery API. It lets your agent pull live content entries, grab media URLs, and inspect content type schemas in real-time. No more manual copy-pasting from your CMS to your chat window.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_khaljPQidGuOMSZME2SG4LzAdg5hrWHTA6RFTIow/ai-agent-connect
- **Tags:** api-delivery, content-retrieval, omnichannel, schema-management, content-delivery-network

## Description

This Connector gives your AI agent a direct line to your Contentstack environment. Instead of switching tabs to dig through your CMS dashboard, you can just ask your agent to pull live content, find specific images, or check your content type schemas. It's a huge win for keeping your team in sync because it puts your production data right into your conversation. You can use it to find specific blog posts by title, grab direct URLs for campaign assets, or get a structural breakdown of any content type before you start building a frontend. When you add this to your Vinkius setup, your agent gains the context it needs to provide accurate answers based on your actual data. You get to stop hunting for links and start actually building. It's about making sure your agent knows exactly what's live in your headless CMS without you having to do the heavy lifting of manual data retrieval.

## Tools

### get_asset_details
Get the specific details for an individual media asset. This is useful for finding specific file metadata.

### get_content_type_details
Fetch the full schema for a specific content type. Use this to see all fields and requirements for a model.

### search_entries
Search for specific entries using a JSON query. This allows for precise filtering of your content.

### sync_content
Get the delta of changes since you last synced your content. This keeps your agent's knowledge current.

### get_entry
Pull the detailed content for a specific entry. This lets your agent read the full body of a published item.

### get_stack_summary
Get high-level metadata about your current Contentstack stack. It helps the agent understand your environment.

### list_assets
List every published asset currently in your media library. Use this to browse your available media.

### list_content_types
See a list of all content types defined in your stack. This helps with mapping out your entire content model.

### list_entries
List all published entries for a specific content type. This is great for auditing what is live in an environment.

## Prompt Examples

**Prompt:** 
```
What does the 'Hero Banner' content type look like?
```

**Response:** 
```
The **Hero Banner** content type includes the following fields:

| Field Name | Type | Requirement |
| :--- | :--- | :--- |
| **heading** | Short Text | Mandatory |
| **subText** | Long Text | Optional |
| **backgroundAsset** | File Reference | Mandatory |

This ensures all deployed hero sections have enough styling definitions to render without errors.
```

**Prompt:** 
```
Find the URL for the 'Spring 2024' banner.
```

**Response:** 
```
I've found the asset in your library:

*   **Name:** Banner-Spring-2024.png
*   **Status:** Published
*   **CDN URL:** `https://cdn.contentstack.io/assets/blt77d44a06c81b1730/68a6c7effd4281a5fb31e2a5/Cs_Opengraph_1.webp`
```

**Prompt:** 
```
List the last 5 blog posts.
```

**Response:** 
```
Here are the most recent published blog entries:

1.  **Future Trends in AI**
2.  **Mastering Headless CMS**
3.  **The Rise of MCP**
4.  **Content Strategy 101**
5.  **Developer Tips**
```

## Capabilities

### Pull live content entries
Get live content from your CMS by searching for specific titles or using query filters.

### Grab media URLs
Instantly find the direct CDN links for images, PDFs, and other files in your library.

### Inspect content type schemas
Get a detailed structural breakdown of any content type to see required fields and types.

### Get stack metadata
Retrieve high-level information about your current stack to understand your environment.

### List all published assets
See every published asset in your media library at once.

### Retrieve content changes
Get the delta of changes since your last sync to stay up to date.

## Use Cases

### Schema Verification
A developer needs to know the 'Hero Banner' fields. They ask the agent to check get_content_type_details to avoid frontend errors.

### Asset Hunting
A marketer needs the URL for a spring banner. The agent uses list_assets and get_asset_details to provide the link.

### Content Audit
A manager wants to see all blog posts in staging. The agent uses list_entries to show the titles in a simple list.

### Rapid Prototyping
A designer needs to see the 'Product' content structure. The agent uses get_stack_summary and list_content_types to map it out.

## Benefits

- Stop manual copy-pasting by using get_entry to pull live content directly into your chat window.
- Build frontend components faster by using get_content_type_details to see schemas before you write code.
- Find media links instantly with list_assets and get_asset_details for your marketing campaigns.
- Audit environments quickly using list_entries to see what's actually live in production or staging.
- Keep your data fresh by using sync_content to fetch only the latest updates without re-fetching everything.
- Verify content requirements instantly to ensure your frontend rendering code matches the CMS payload.

## How It Works

The bottom line is your AI agent gets instant, read-only access to your live headless CMS data.

1. Get your read-only Delivery Token, Stack API Key, and Environment Name from your Contentstack settings.
2. Connect the Connector through your preferred client using the Vinkius integration.
3. Ask your agent to find specific content, list assets, or describe a schema in plain English.

## Frequently Asked Questions

**Can Contentstack MCP help me build my frontend?**
Yes, it lets your agent fetch the exact schema for any content type. You can see which fields are mandatory and what data types they use before you write a single line of frontend code.

**How do I get image URLs from my CMS?**
Your agent can use this Connector to browse your media library and provide direct CDN URLs for any published images, PDFs, or other files instantly.

**Can I use Contentstack MCP to edit my content?**
No, this Connector is designed for the Delivery API, which is read-only. You can retrieve and view content, but you'll need a different tool to create or edit entries.

**Does Contentstack MCP work with my staging environment?**
Yes, you can connect it to your staging environment by providing the correct Environment Name and a read-only Delivery Token during setup.

**How do I see my content schemas?**
Just ask your agent to describe a specific content type. It will pull the structural breakdown from your stack and show it to you in the chat.

**Is Contentstack MCP secure for my data?**
It uses your existing Contentstack Delivery Token. Because it's read-only, it provides a secure way for your agent to access content without the ability to modify your data.

**How do I correctly generate a Contentstack Delivery Token?**
Log into your core Contentstack account dashboard securely. Access the specific Stack you wish to query and navigate toward the technical 'Settings' header before clicking on 'Tokens'. Within this specific submenu, specifically select 'Delivery Tokens'. Generate a new one with an identifying name, assigning it distinctly to your intended 'Environment'. Note down the produced Token safely to input along with the matching Stack API key below.

**Can the agent update entries or publish content directly to the CMS?**
No. The integration exclusively relies upon Contentstack's globally distributed 'Delivery API' rather than their 'Management API', deliberately restricting operations to a secure read-only modality focused on retrieving already published entries, preventing accidental automated or unauthorized payload mutations from impacting live production data stores.

**Do I need to type the exact environment name as it appears in Contentstack?**
Yes, accuracy is strictly required. Providing the exact environment name (e.g., 'production' or 'staging') matching the internal naming correctly ensures the endpoint filters accurately out published iterations of records belonging only to those targeted distribution layers you are aiming specifically at querying reliably during chat prompts.