Sitecore MCP. Manage content items and workflows 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.
Sitecore MCP Server lets your AI agent manage all aspects of your enterprise CMS. You can create, search, update content items, templates, and workflows directly from chat—no need to open the complex Sitecore Content Editor.
It handles deep content searches, item creation via `create_content_item`, layout retrieval using `get_item_layout`, and even monitors workflow states with `get_workflow_state`.
What your AI agents can do
Create content item
Builds a new item in the Sitecore content tree, requiring parent ID, item name, and template ID.
Delete content item
Permanently removes an existing Sitecore item. This action is irreversible.
Get item details
Retrieves all stored data and details for a specific, known Sitecore content item.
The agent can build new pages using create_content_item or permanently remove old content with delete_content_item.
Run deep, keyword-based searches across all available content items using search_content.
Retrieve specific presentation or layout data for an item's page view using get_item_layout.
Change text, images, or structured data on a page by providing field name/value pairs to update_content_item.
Get the current status of any content item (e.g., Draft, Published) using get_workflow_state.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Sitecore: 9 Tools for CMS Management
These tools let you manage everything in Sitecore—from creating content items to tracking workflow states—all through your AI client.
019d7608create content item
Builds a new item in the Sitecore content tree, requiring parent ID, item name, and template ID.
019d7608delete content item
Permanently removes an existing Sitecore item. This action is irreversible.
019d7608get item details
Retrieves all stored data and details for a specific, known Sitecore content item.
019d7608get item layout
Pulls the layout or presentation structure (including placeholders) used by a specific site page.
019d7608get workflow state
Checks and reports the current lifecycle status of an item, such as Draft or Published.
019d7608list content templates
Lists all available content templates that can be used when creating new items.
019d7608list item children
Traverses the site structure by listing only the immediate sub-items under a specified parent node.
019d7608search content
Performs broad, deep searches across the entire CMS content repository using keywords and filters.
019d7608update content item
Changes the field values of an existing Sitecore item by accepting a JSON object of name/value pairs.
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 Sitecore, 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
Sitecore MCP Server: Manage your entire CMS from chat.
You don't need to mess with that complicated Sitecore Content Editor anymore. We hook up your AI agent so it can run complex commands on your whole enterprise CMS just by talking to it. Your agent handles everything—you can build content, check workflows, and modify pages without ever opening the dashboard.
Building and Deleting Content Items.
Need a new page? You tell your agent where it goes, what it’s called, and what template it should use; it builds it for you using create_content_item. If something's outdated or wrong, the agent can permanently wipe out the content item with delete_content_item. Just remember, that action is irreversible.
Searching and Navigating the Content Tree.
The whole site content repository? Your agent runs deep searches across it using search_content, letting you filter by keywords or specific dates. You can map out the content hierarchy by listing only the immediate sub-items under a parent node with list_item_children. To get all the stored data and details for any single, known item, your agent uses get_item_details.
Designing and Updating Pages.
When you need to know how a page looks or what structure it's supposed to have, your agent pulls that layout information using get_item_layout. If the site needs new content—maybe updating an image or changing some text block—your agent modifies the existing item fields by accepting a JSON object of name/value pairs into update_content_item.
Before creating anything, you can check out all available structure types with list_content_templates.
Checking Status and Workflows.
Your agent keeps tabs on content progress. It reports the current lifecycle status—like whether an item is in Draft, Review, or Published—using get_workflow_state. You can check if any page needs attention by getting its full details with get_item_details.
It’s simple: you ask your AI agent to do something complex on Sitecore, and it executes the exact function needed using these tools.
How Sitecore MCP Works
- 1 First, you subscribe to this server and provide your Sitecore Base URL along with a Service Client API Key.
- 2 Next, you ask your AI client (like Claude or Cursor) to perform an action: 'What is the workflow state for /Home/AboutUs?'
- 3 The agent uses
get_workflow_state, gets the result (e.g., Draft), and reports it back to you immediately.
The bottom line is, your AI client handles all the Sitecore backend calls so you never have to leave your chat window.
Who Is Sitecore MCP For?
This is for content authors who are tired of clicking through multiple tabs and navigating complex UIs. It’s for developers needing to query deep trees quickly, and marketers who need rapid search capabilities without opening the CMS editor.
Updates field values across multiple pages or checks item workflow states without manually logging into the Sitecore client.
Automates test content creation using create_content_item and queries complex content trees while coding headless applications.
Performs rapid, targeted searches across old or legacy content items to verify component placement or find specific archived data.
What Changes When You Connect
- Stop switching between editors and the backend. You can manage everything—from creating content using
create_content_itemto updating fields withupdate_content_item—all within your AI client's conversation window. - Find niche, old content fast. Instead of manual browsing, use
search_contentto run deep searches across the whole CMS based on keywords or date ranges. - See exactly what a page looks like before coding it. Running
get_item_layoutshows you the presentation details and placeholders for any given item. - Keep tabs on content approval. Use
get_workflow_stateto instantly confirm if an article is still in Draft or if it's already Published—no need to guess. - Map out your entire site structure easily.
list_item_childrenshows you the immediate nodes under any parent, helping developers understand the content hierarchy quickly.
Real-World Use Cases
Need to verify a component's placement on an old page.
A marketer needs to check if every product listing page uses the 'v2-card' component. They ask their agent to run get_item_layout against 15 different item IDs, getting instant confirmation of the presentation structure for each one.
Need to launch a test campaign site quickly.
A developer asks the agent to use list_content_templates first. Then, they ask it to create three new items named 'Q3-Test', 'Q4-Test', and 'Internal' using create_content_item, saving time compared to manual setup.
Need to find a specific piece of archived content.
A user needs an article from 2019 about compliance. They use search_content with 'compliance' and the date range filter, finding the exact item ID that was buried deep in the tree.
Need to update text across multiple landing pages.
The team needs to change the hero headline on 10 different product pages. They use update_content_item repeatedly, passing a JSON payload with the new headline and the target item ID each time.
The Tradeoffs
Trying to list all content.
Opening the Sitecore Content Editor and clicking through every single node in the tree until they find what they need. It's slow, tedious, and easy to get lost.
→
Just run search_content with keywords or use list_item_children on the parent node you know exists. Don't browse.
Forgetting item IDs when updating content.
Trying to update a field value but forgetting which specific item ID needs the change, resulting in an error or worse, updating the wrong page.
→
Always run get_item_details first to confirm the exact path and unique ID. Then pass that confirmed ID to update_content_item.
Assuming content is ready for live use.
Publishing a page right after updating it without checking its status, only to find out later it's stuck in the Review queue.
→
Run get_workflow_state immediately after making changes. Only proceed if the tool confirms the state is 'Ready for Publish'.
When It Fits, When It Doesn't
Use this MCP Server when your primary bottleneck is managing content items or workflows without leaving your agent chat window. It's ideal for read-heavy tasks like running search_content, checking layouts with get_item_layout, and tracking status via get_workflow_state. Don't use it if you need to interact with non-Sitecore services (like Salesforce or Jira); those require different servers. Also, don’t rely on the agent to fix complex content logic; it only executes commands. If your task is 'How do I write copy?', this won't help. If your task is 'Change the headline on /Home/AboutUs', this is exactly what you need.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sitecore. 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
Finding a specific page element shouldn't require five clicks and a deep knowledge of content paths.
Today, if you need to know the exact structure of a product card on ten different pages, you have to open each page in the editor. You click 'View Layout,' then scroll through fields like 'Hero Image' and 'Product Specs.' It takes fifteen minutes just to gather that information.
With this MCP server, you ask your agent for the layout details using `get_item_layout`. It pulls the presentation data directly into the chat. Boom. You get the full structural breakdown for all ten pages in seconds.
Using Sitecore’s tools: The power of `update_content_item`.
Before, updating content meant logging into the CMS, navigating to the specific item path, clicking on the field you wanted to change (e.g., 'CTA Button Text'), typing in the new copy, and hitting save. It was a multi-step, high-friction process.
Now, just tell your agent: 'Update /Home/AboutUs with the following JSON object.' The `update_content_item` tool executes the change directly from chat. Done.
Common Questions About Sitecore MCP
How do I use get_workflow_state to check if an item is ready? +
Run get_workflow_state and look for 'Published' or a green status indicator. If it says 'Draft,' you know the content needs human review before going live.
Is search_content better than listing item children? +
search_content is for finding content based on keywords, templates, or dates across the whole CMS. list_item_children only shows you what lives directly under one specific parent node.
Can I use create_content_item to build a whole campaign? +
Yes, you can automate it. You provide the required parent ID and template ID, and create_content_item builds the initial structure for your new content piece.
What does get_item_layout show me exactly? +
It shows the presentation details—the rendering instructions and placeholders. This is critical for developers who need to know how a page is structured, not just what text it contains.
What happens if I use delete_content_item on a live item? +
The deletion is permanent and cannot be undone. Your agent sends the request, and Sitecore executes it immediately, removing the content from the tree entirely.
How does update_content_item handle incorrect field names or types? +
If a field name in your JSON doesn't exist on the item, the API call will reject it. You must ensure the key/value pairs match the item's schema exactly.
Do I need to run list_content_templates before using create_content_item? +
It’s highly recommended you check with list_content_templates first. This confirms which templates are available for use, preventing creation errors.
Is there a way to prevent rate limits when running search_content repeatedly? +
The Vinkius platform handles basic rate limiting on the server side. For high-volume queries, consider batching your requests or implementing an exponential backoff in your calling script.
Can my AI agent create new pages from specific templates? +
Yes. Ask the agent to list your content templates to find the ID of the template you want (e.g., 'Article' or 'Landing Page'). Then, provide the parent path where you want the new items to exist. Your agent will call the Sitecore API to instantly generate the new items based on those schemas without requiring you to open the Content Editor.
How can I bulk update metadata for outdated pages? +
First, ask your agent to search for the specific path or keyword to get all related page IDs. Then, command the agent to update each item by passing a JSON with the new fields (like updating SEO descriptions or valid dates). The AI parses your instruction and dynamically executes the updates directly into Sitecore.
Is it possible to check whether an item is published or still in Draft mode? +
Absolutely. You can request the agent to get the workflow state of any given item path. The agent will respond with the current state (e.g., Draft, Awaiting Approval, or Published), making it easy to track content pipelines.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
QuickBooks Online
Connect QuickBooks to AI — query invoices, manage customers, run financial reports, and automate accounting workflows.
UKG Ready
Manage employee lifecycle, HCM, payroll, and time via UKG Ready.
Amazon S3
Cloud object storage orchestration — manage buckets, objects, and metadata via AI.
You might also like
Zentitle2
Manage software licenses and entitlements with a cloud platform that handles activation, metering, and feature gating for ISVs.
Quotable API
Access thousands of quotes — audit authors and tags via AI.
GivingFuel
Retrieve donation orders, track registrants, and oversee fundraising pages via AI agents with GivingFuel.