Contentstack MCP. Manage content entries and schemas from chat.
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. Manage your headless CMS directly from any AI client. You can list, create, and update content entries, inspect schemas, and trigger live publications to development or production environments, all without leaving the chat window.
What your AI agents can do
Create cms entry
Creates new Contentstack drafts using a structured JSON payload.
Get media asset
Retrieves detailed information verifying a specific media ID.
Get schema details
Extracts the properties that define an active content field.
Identifies all content rows for a given type and drafts new entries using structured JSON payloads.
Triggers the CMS publication sequence, pushing data to specific environments like development, staging, or production.
Retrieves global schema definitions, decodes field validation rules, and lists media assets with their full metadata.
Updates existing content entries by overwriting blocks or safely deleting entire content nodes.
Gets a single entry by its UUID, or retrieves detailed metadata for a specific media asset ID.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Contentstack MCP Server: 10 Tools for Content Management
These tools let your AI client manage the entire content lifecycle—from listing schemas to publishing live data—all from within a single conversation.
019d757bcreate cms entry
Creates new Contentstack drafts using a structured JSON payload.
019d757bget media asset
Retrieves detailed information verifying a specific media ID.
019d757bget schema details
Extracts the properties that define an active content field.
019d757bget single entry
Gets the content data for one specific entry UUID.
019d757blist global schemas
Lists all available content types and their structured rules.
019d757blist media assets
Inspects deep lists of media files, mitigating picture limits.
019d757blist type entries
Identifies and lists content rows within a specific CMS schema.
019d757bpublish to environment
Sends content data live to a specified environment (dev, staging, production).
019d757bupdate cms entry
Changes existing content data by overwriting blocks or substituting draft values.
019d757bwipe cms entry
Permanently removes content nodes and live document rows.
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
You're gonna manage your headless CMS straight from your AI client. This server lets you list, create, and update content entries, inspect schemas, and push data live to development, staging, or production environments—all without writing a single API call. You just talk to your agent.
Listing and Drafting Content
Use list_type_entries to see every content row for a specific schema. To draft new content, run create_cms_entry with a structured JSON payload. You can grab the data for one specific entry using get_single_entry with its UUID. To change what's already there, update_cms_entry lets you overwrite schema blocks or swap out draft values.
If you gotta clear things out, wipe_cms_entry permanently removes the content nodes and live document rows.
Inspecting Models and Assets
Need to know how your data is structured? list_global_schemas lists every content type available. get_schema_details pulls the properties and validation rules for any content field. You can check out all the media files and their metadata by running list_media_assets. To get details on one specific picture, get_media_asset verifies a media ID.
How Contentstack MCP Works
- 1 Subscribe to the server and provide your Contentstack API Key and Management Token.
- 2 Your AI client uses natural language to determine which tools are needed (e.g., 'Publish entry X to production').
- 3 The server executes the tools, and your AI client reads the results to complete the task.
The bottom line is that you control the entire content lifecycle—from schema inspection to live publishing—using only conversation.
Who Is Contentstack MCP For?
Content Managers who need to push content live without leaving their chat. Front-end Developers who must inspect content models and asset URLs during development. Product Teams monitoring content structures for new features. Digital Ops engineers who need to audit and verify publication statuses.
Creates, updates, and publishes content entries across environments using natural language prompts.
Inspects content type schemas and retrieves asset URLs directly in the chat while building a feature.
Manages stack environments and verifies publication statuses by asking the AI client for status reports.
What Changes When You Connect
- Manage content changes without switching tabs. You can use
update_cms_entryto modify an entry, and thenpublish_to_environmentto push those changes live, all within the chat window. - Avoid manual asset scraping.
list_media_assetsgives you full metadata for every media file, including original Contentstack URLs, so you don't have to guess or manually link assets. - Understand your content structure instantly. Before you write a single line of code, run
list_global_schemasto enumerate every available content type and see its field rules. - Run content operations on demand. Need to find all draft blog posts? Use
list_type_entriesto identify all bounded content rows for a specific schema. - Control your data lifecycle. Need to remove old test data?
wipe_cms_entryirreversibly deletes content nodes and document rows, keeping your stack clean. - Retrieve data on demand. Use
get_single_entryto pull the full data for one entry just by its UUID, perfect for debugging.
Real-World Use Cases
The content editor needs to stage a new homepage.
The editor asks the agent: 'Find all entries for the 'homepage' type, draft the new version, and publish it to staging.' The agent runs list_type_entries to find candidates, create_cms_entry to build the draft, and publish_to_environment to make it live for review. The problem is solved in three steps.
The developer needs to validate a field reference.
A front-end developer needs to know if the 'product_sku' field exists and what data type it expects. They run get_schema_details on the 'product_schema' model. The agent returns the specific field properties and validation rules, letting the developer code with confidence.
The ops team needs to clean up old test data.
The ops engineer needs to ensure old, unneeded test content is removed from the database. They use wipe_cms_entry to irreversibly vaporize the app nodes and drop the document rows, clearing out internal allocations.
The marketer needs to update a section across 10 pages.
Instead of logging into the CMS and clicking 10 times, the marketer asks the agent to update the 'call-to-action' field across all relevant entries. The agent uses update_cms_entry and then publish_to_environment to push the change everywhere.
The Tradeoffs
Manually inspecting every asset URL
The developer manually copies URLs from the CMS admin panel, hoping they are the correct, live, final versions for the build, wasting time on broken or partial links.
→
Run list_media_assets to inspect deep internal arrays and retrieve the explicit media metadata. This gives you the correct, full URLs you need to build your components.
Overwriting content by accident
A content manager tries to fix a field by manually editing the source, but accidentally overwrites a critical schema block or a linked draft value, breaking the page.
→
Use update_cms_entry to safely mutate existing entries. You can overwrite schema blocks and substitute draft values through the Management API, ensuring you only change what you intend to change.
Testing content on the wrong environment
A developer publishes a feature to 'development' but forgets to check the 'staging' environment first, causing bad content to go live prematurely.
→
Always use publish_to_environment and specify the exact environment (e.g., 'staging'). This tool ensures the publication sequence hits the target environment only.
When It Fits, When It Doesn't
Use this if your job requires managing structured content across multiple environments. You need to read schemas, list entries, and perform controlled writes (create, update, delete). Don't use this if you just need to store unstructured text files or images; those require a file storage service. If your core problem is figuring out how content is related (e.g., 'show me all articles linked to this media asset'), you'll need a graph database approach, not just a CRUD API. This server focuses on the content lifecycle itself.
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 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually managing content means endless clicks and stale links.
Today, updating a piece of content is a multi-step nightmare. You have to log into the CMS, find the specific content type, navigate to the entry, manually change the text, and then find the separate 'Publish' button, praying you hit the right environment. If you skip a step, the content never goes live.
With this MCP server, you talk to your agent. You say, 'Update the 'About Us' page with the new text and publish it to staging.' The agent runs `update_cms_entry`, then `publish_to_environment`. You get the confirmation back in the chat, and the content is ready.
Contentstack MCP Server: Full control over content publishing.
The manual steps that vanish are: logging in, navigating schemas, manually triggering drafts, and clicking through multiple environments. You don't have to leave your IDE or chat window.
You get programmatic control over the entire content lifecycle. You can write, update, and publish content to any environment—all from a single, structured tool call.
Common Questions About Contentstack MCP
How do I use the `list_global_schemas` tool with Contentstack MCP Server? +
You ask your agent to run list_global_schemas when you need to know what content types exist. This tool returns a list of all available schemas, so you know what content models you can work with.
Can `publish_to_environment` publish multiple entries at once? +
Yes. You can instruct your agent to identify multiple entries (e.g., using list_type_entries) and then run publish_to_environment on the entire set, targeting a specific environment.
Is `wipe_cms_entry` safe? +
Be careful. wipe_cms_entry permanently removes content nodes and live document rows. It's an irreversible action, so confirm exactly what you are deleting before running it.
How do I get the data for a specific entry using `get_single_entry`? +
You provide the specific Entry UUID to the agent. The tool then retrieves the full, explicit data payload for that single entry, letting you inspect its contents.
What details does `list_type_entries` provide about content schemas? +
It lists all bounded routing spaces within your Headless Contentstack CMS schemas. This helps you identify exactly which content types exist and what kind of entries they manage.
How do I handle media asset metadata using `get_media_asset`? +
The tool retrieves precise, structural matching for explicit Media IDs. You get the original Contentstack URLs and metadata, which prevents you from having to scrape the CDN manually.
Is there a way to update content safely using `update_cms_entry`? +
Yes, the tool safely mutates global Web CRM boundaries. You can overwrite schema blocks and substitute draft values when updating existing entries.
Does `create_cms_entry` support generating entries with specific JSON attributes? +
Yes, it provisions highly-available JSON Payloads. You can generate new Contentstack Drafts and ensure they include the exact, structured attributes you need.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ThePDFMaker
Transform HTML templates into pixel-perfect PDF documents with an API designed for invoices, reports, and branded output.
Umbraco
Automate content workflows via Umbraco — retrieve delivery content, execute backoffice CRUD, and browse media assets directly from your AI agent.
WordPress
Build and manage websites with the CMS that powers over 40 percent of the web through posts, pages, plugins, and themes.
You might also like
Avochato
Text your customers on the channels they prefer with two-way business messaging that integrates into your existing workflows.
Open WebUI
Manage your Open WebUI instance — list models, handle chat completions, and manage RAG collections directly from any AI agent.
ACRCloud Music Recognition
Identify and explore music via ACRCloud — recognize songs from audio files and retrieve rich metadata.