Contentstack MCP. Read live CMS data, assets, and schemas instantly
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Contentstack MCP Server lets your AI agent read and structure data directly from your headless CMS. Use it to fetch published blog posts, get specific asset URLs, or audit content schemas in real-time.
You can query live content entries, discover media assets, and inspect content type structures without leaving your IDE.
What your AI agents can do
Get asset details
Retrieves specific metadata and details for a known media asset.
Get content type details
Gets the field schema and structure for a specific content type.
Get entry
Pulls the complete, detailed content payload for one specific entry.
The agent queries the CMS and returns the full body and metadata for a specific article or page.
The agent finds media files (images, PDFs) by listing assets or retrieving a specific asset's CDN URL.
The agent reads the schema of any content type, showing you exactly what fields (e.g., 'author', 'date', 'heading') are available.
The agent searches for entries across your stack using flexible JSON query filters.
The agent pulls high-level summaries about your entire Contentstack instance.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Contentstack MCP Server: 9 Tools for CMS Data Access
Use these tools to let your AI agent read, search, and audit all content, assets, and types within your Contentstack headless CMS.
019d757bget asset details
Retrieves specific metadata and details for a known media asset.
019d757bget content type details
Gets the field schema and structure for a specific content type.
019d757bget entry
Pulls the complete, detailed content payload for one specific entry.
019d757bget stack summary
Retrieves high-level metadata and status information about the entire Contentstack instance.
019d757blist assets
Lists all published media assets available in the CMS library.
019d757blist content types
Lists every content type defined within the stack.
019d757blist entries
Lists the titles and IDs of all published entries for a given content type.
019d757bsearch entries
Finds and retrieves content entries using a flexible JSON query against the whole stack.
019d757bsync content
Retrieves only the changes in content since the last successful synchronization time.
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 every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Contentstack, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Contentstack MCP Server lets your AI client read and structure data directly from your headless CMS. You can use it to pull published blog posts, get specific asset URLs, or audit content schemas in real-time. Your agent queries live content entries, discovers media assets, and inspects content type structures right where you're working.
list_content_types lists every content type defined in the stack. list_entries shows you the titles and IDs of all published entries for a specific content type. get_entry pulls the complete, detailed content payload for one specific entry. search_entries finds and retrieves content entries across your stack using a flexible JSON query against the whole stack. sync_content gets only the content changes since the last successful sync time. get_stack_summary pulls high-level metadata and status info about the entire Contentstack instance. list_assets lists every published media asset available in the CMS library. get_asset_details retrieves specific metadata and details for a known media asset. get_content_type_details reads the field schema and structure for a specific content type.
How Contentstack MCP Works
- 1 Enable the MCP integration and secure the connection using your Contentstack read-only Delivery Token and Environment Name.
- 2 Your AI client sends a natural language prompt (e.g., 'Get the asset for the product logo').
- 3 The server invokes the correct tool, pulling the requested data (e.g.,
get_asset_details) and feeding the structured result back to your agent.
The bottom line is: you talk to your agent, and it talks to Contentstack for you.
Who Is Contentstack MCP For?
This is for the developer who needs to verify live data payloads without leaving their IDE. It’s for the content manager who needs to audit content variants across 'production' or 'staging' environments. It’s for the marketing integrator who needs quick, public URLs for cross-platform campaigns.
Checks live payload structures instantly. Needs to verify if the front-end rendering code matches the actual data model in the CMS.
Audits content variants and checks what content is available in specific environments (staging vs. production) without manually logging into the CMS.
Locates public URLs for campaign assets (like banners or logos) and copy text snippets quickly for distribution across multiple platforms.
What Changes When You Connect
- Verify live payloads without context switching. Tools like
get_entryandget_content_type_detailslet you check the actual data structure right where you're coding. - Manage assets across environments. Use
list_assetsandget_asset_detailsto find and validate the exact CDN URL for any image or PDF. - Quickly audit content availability.
list_entrieslets you see what content is published for a type, andsearch_entriesfinds specific items across the whole stack. - Understand your data model. Running
list_content_typesorget_content_type_detailsimmediately tells you what fields are available to build against. - Stay current with changes.
sync_contentpulls only the delta, so you don't have to re-read massive payloads if content has changed slightly.
Real-World Use Cases
Validating a new blog post template
The dev needs to know if the 'author bio' field exists and what its type is. They run get_content_type_details on 'Author Profile'. The agent confirms the field exists and shows the required format, letting the dev continue coding without guessing.
Finding a specific campaign image URL
The marketing team needs the direct URL for 'Q3 Banner'. They ask the agent to list assets and filter by name. The agent uses list_assets and get_asset_details to return the precise CDN link, which they plug into the cross-platform campaign.
Checking content in staging vs. production
The content manager wants to confirm if the 'About Us' page copy was updated in the staging environment. They use search_entries and specify the target environment, confirming the copy is live before the production push.
Debugging missing data points
A feature fails because a required field is null. The agent runs get_entry for the failing record. The developer reviews the full payload returned by the tool to see exactly which field is missing or improperly formatted.
The Tradeoffs
Guessing schemas
Assuming a new content type has a 'featuredImage' field because it did last month. You build code that fails at runtime because the field name changed or was deprecated.
→
Don't assume. Run get_content_type_details first. This immediately shows the current, required schema for the type you are working with.
Over-fetching assets
Listing all assets using list_assets when you only need one specific file. You get a massive list, making it hard to find the single URL you need.
→
Use get_asset_details or list_assets with specific filters to target only the assets you need. Pinpoint the exact URL you're looking for.
Ignoring updates
Assuming the content on a page is the latest version because you haven't checked. You deploy a feature that reads old, cached content.
→
Always run sync_content before building. This ensures your agent pulls the latest changes and metadata since your last check.
When It Fits, When It Doesn't
Use this server if your job requires reading live data from Contentstack—specifically, if you need to validate data structures (schemas), find concrete URLs, or pull the actual copy text. You MUST use this if you are writing code that depends on the CMS content. Don't use this if you just need to manage the CMS itself (that's the Contentstack UI). Also, if you only need a simple list of titles and nothing else, list_entries is faster than a full search_entries query. If you only need to know if a content type exists, run list_content_types first, then drill down with get_content_type_details.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Contentstack. 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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking CMS data is a nightmare of clicks and tabs.
Today, checking a piece of content means logging into the CMS, finding the right content type, clicking through to the specific entry, and then manually copying the copy text, the asset URL, and checking the schema structure against your local component files. It's a three-system dance that loses time and requires constant context switching.
With the Contentstack MCP Server, you just ask your agent. It handles the login, the navigation, and the data retrieval. You get the validated content body, the specific asset URL, and the schema breakdown—all in one chat response. It's instant.
Contentstack MCP Server: Get the full content and asset details.
You no longer have to switch between your IDE, your CMS dashboard, and your terminal just to verify one data point. The agent pulls the exact payload you need, whether it's a list of assets via `list_assets` or the full text via `get_entry`. The data is always current.
It's a direct read access pipeline. You don't just see the content; you see the structured, live data that your application will actually consume.
Common Questions About Contentstack MCP
How do I use the `get_content_type_details` tool with Contentstack MCP Server? +
You ask your agent to get the schema for a specific content type (e.g., 'Product Page'). The agent runs get_content_type_details and returns the full JSON schema, showing all available fields and their required types.
Can I use `search_entries` to find a specific article title? +
Yes. You simply ask the agent to search for content using the title or a keyword. The agent executes search_entries with your query parameters, returning matching entries.
What is the difference between `list_assets` and `get_asset_details`? +
list_assets gives you a list of all available assets. get_asset_details requires a specific asset ID and gives you the full metadata and CDN URL for just that one asset.
How does `sync_content` help me with content changes? +
sync_content checks for changes. It only pulls the delta of content—the updates that happened since your last sync—so you don't waste time processing old data.
How do I use the `list_entries` tool to check published content types? +
The list_entries tool retrieves published content entries for a specific Content Type. You must know the Content Type ID to use it. This tool is useful for seeing all live articles or records of a defined type.
What is the difference between `list_content_types` and `get_content_type_details`? +
The list_content_types tool returns a list of all available content types in your stack. Use get_content_type_details when you know the specific Content Type ID and need the full structural schema for it.
Does the `search_entries` tool support advanced filtering or complex queries? +
Yes, the search_entries tool accepts a JSON query object. This lets you filter entries using specific field values, date ranges, or complex boolean logic.
When should I use `get_stack_summary` instead of other tools? +
Use get_stack_summary to get a high-level overview of your entire Contentstack environment. It provides metadata about the stack itself, which is useful for initial setup checks.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Civo (Cloud-native Kubernetes Cloud Provider API)
Manage Civo cloud infrastructure — provision Kubernetes clusters, control compute instances, and monitor usage directly via AI.
Prismic
Query and manage your Prismic headless CMS content — search documents, list custom types, and retrieve specific content directly from any AI agent.
Strapi
Connect your AI to Strapi. Fully orchestrate your headless CMS — create entries, manage content types, and upload media assets naturally.
You might also like
Moz (SEO Metrics & Link Research)
Manage SEO metrics via Moz — audit Domain Authority (DA), analyze backlinks, and track site rankings.
Workable Alternative
Streamline recruitment via Workable — list job openings, manage candidate profiles, and track hiring stages directly from your AI agent.
Harness
Automate CI/CD and DevOps workflows via Harness — manage pipelines, executions, and secrets directly from any AI agent.