Sitecore MCP. Manage your CMS content without leaving the chat.
Sitecore MCP manages your enterprise CMS directly from any chat window. Use this connector to create, update, delete content items, check item layouts, search deep across templates, or verify workflow status without ever opening the Sitecore Content Editor.
Give Claude and any AI agent real-world access
Generate a brand-new item in the Sitecore structure using a specified template and parent location.
Modify field values on any current item, specifying which data points need to change.
Search broadly across the entire CMS content tree using keywords, templates, or date ranges.
Verify an item's current workflow state (like Draft or Published) or pull its specific layout details.
List the immediate child items under any given parent node to understand the site structure.
Ask an AI about this
Waiting for input…
What AI agents can do with Sitecore: 9 Content Management Tools
These nine tools let you create, modify, find, and audit every aspect of content in a Sitecore instance directly through your agent.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Sitecore MCPCreate Content Item
Creates a brand new item within the content tree, requiring you to specify its parent ID, name, and template type.
Delete Content Item
Permanently deletes an entire Sitecore item. Note that this action cannot be undone.
Get Item Details
Pulls all current details for a specific Sitecore item using its unique path or ID.
Get Item Layout
Retrieves the presentation and layout rules that dictate how an item should appear...
Get Workflow State
Checks and reports the current status of any item's workflow, such as Draft or...
List Item Children
Generates a list of all immediate child items residing under a specified parent node.
List Content Templates
Provides a list of every available content template that can be used to build new pages or assets.
Search Content
Performs broad, deep searches for content items across the entire Sitecore...
Update Content Item
Changes field values on an existing item by passing in a JSON object detailing the...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 each 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 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The friction points in managing enterprise CMS content.
Today, updating content often means logging into the specialized Content Editor. You click through nested folders to find the right item, check its current layout rules, manually adjust field values across multiple pages, and then finally hit 'Submit.' This process is slow, requires dozens of tabs open, and makes it easy to accidentally modify the wrong thing.
With this MCP, you keep everything in your chat window. You tell your agent exactly what needs fixing or updating. The tool handles the complex pathing and data structure behind the scenes. You simply get confirmation that the item was updated or created successfully—no more clicking through a dozen menus.
Sitecore MCP for Content Management Tools
The biggest time sink is context switching. Having to jump from your writing flow into the CMS editor, then back out again, breaks focus and wastes minutes on every single change. You lose momentum just navigating the system.
Now, you keep the workflow in chat. Your agent becomes an invisible copilot that speaks Sitecore’s language directly into your conversation. It's instant.
What Sitecore MCP does for your AI
Connect your Sitecore instance to your AI agent and take full control of your complex CMS environment through natural conversation. You can perform core headless operations—like creating new pages or updating field values—without navigating the demanding Sitecore Content Editor GUI. Instead, you simply tell your agent what needs changing. Need to find old content? Your agent searches across templates using keywords and dates.
Want to see if a page is ready for publishing? It checks the item's workflow status instantly. When everything else feels like it requires context-switching between your code editor and the CMS backend, this MCP centralizes all that power. Because Vinkius hosts this catalog, you connect once from any compatible client and get instant access to full content lifecycle management.
019d7608-ab5a-7116-a0f3-98fb420bc6c8 How to set up Sitecore MCP
The bottom line is you manage complex digital experiences using simple chat commands instead of multiple logins and GUIs.
First, subscribe to this MCP and provide your Sitecore Base URL along with your Services Client API Key.
Next, trigger an action request—for example, asking your agent to check the workflow state for a specific page path.
Your agent sends the necessary calls to Sitecore and returns structured data about item details or content status directly into the chat.
Who uses Sitecore MCP
This MCP serves Content Authors who hate context switching, Marketers needing to verify legacy content quickly, and Developers automating test item creation. It’s for anyone whose job involves making changes or validating structure within a large-scale enterprise CMS.
Uses the MCP to update field values across dozens of pages quickly, and checks workflow states without having to open the main Sitecore client.
Runs rapid content searches to locate old campaign assets or verifies if a personalized component is correctly configured in an item’s layout.
Automates the creation of test items and queries complex Sitecore trees when building headless applications that need mock data.
Benefits of connecting Sitecore MCP
Avoid context switching. Instead of jumping between your AI client and the complex Sitecore editor, you manage item creation, updates, and status checks all in one conversation flow.
Accelerate content discovery. Use search_content to find specific legacy assets or templates by keywords and dates instantly, even if you don't know the exact path.
Control the content lifecycle. You can check an item’s current status using get_workflow_state, verifying whether a page is in Draft or ready for publication before making changes.
Build structured data quickly. Instead of manually entering details, use update_content_item to push field value changes across multiple pages at once via a JSON object.
Map the site structure easily. Running list_item_children lets you see exactly what content nodes exist under any parent page, helping developers understand the hierarchy quickly.
Sitecore MCP use cases
A marketing team needs to verify a campaign's status.
The marketer asks their agent: 'Check the workflow state for the /campaign/SpringSale item.' The agent uses get_workflow_state and reports that it is still in Review. This prevents them from wasting time trying to edit content that isn't ready.
A developer needs mock data for testing.
The dev prompts: 'Create a new test article using the Article template under the /content/testing path.' The agent executes create_content_item and provides the item's new ID, allowing the developer to continue coding immediately.
A content author must update 50 product descriptions.
Instead of logging in repeatedly, the author uses update_content_item, providing a list of item IDs and a JSON payload with new field values. This saves hours compared to manual bulk editing.
A user needs to know which templates are available.
The user asks the agent to list all content templates. The agent uses list_content_templates and provides a clean, categorized list, saving them from having to browse multiple CMS menus.
Sitecore MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to manually navigate paths.
A user tries to figure out if the 'About Us' page needs a new component by clicking through the Sitecore Content Editor, opening five different child folders, and comparing layout settings in multiple tabs.
Ask your agent to use get_item_layout directly. This tool pulls all necessary presentation details for that item into one response, giving you immediate answers without clicks.
Guessing which content templates exist.
A user assumes a new 'Video Gallery' template exists and tries to create an item using it, only to fail because they don't know the exact template ID or name.
Always start by running list_content_templates. This confirms what templates are actually available in your site instance before you try to build anything.
Overwriting data without confirmation.
A user tells the agent to 'change this field' but doesn't specify which item or parent node they mean, risking accidental modification of live production content.
Be precise. Specify the exact path and use get_item_details first to confirm you are looking at the correct record before attempting any write operations like update_content_item.
When to use Sitecore MCP
Use this MCP if your primary job function involves managing content items, verifying CMS structure, or performing CRUD operations within an existing Sitecore environment. This connector is perfect for authors and developers who need to automate routine tasks—like checking workflow status via get_workflow_state or creating test nodes using create_content_item. Don't use it if you just need to write a simple blog post; that’s better handled natively in the CMS. However, don't use it for anything requiring deep knowledge of your site's codebase structure, like debugging C# code—you'd want a dedicated coding assistant tool for that. This MCP is strictly about content and data management within Sitecore.
Frequently asked questions about Sitecore MCP
How do I check the status of a page using the Sitecore MCP? +
You use get_workflow_state. Simply give your agent the item’s path, and it returns whether that content piece is in Draft, Review, or Published. This saves you from having to navigate the workflow tabs manually.
Can I create a brand new page using the Sitecore MCP? +
Yes, you use create_content_item. You just need to provide the parent ID, the desired name for the new item, and which template it should use.
Is there a way to search old content with Sitecore MCP? +
Absolutely. The search_content tool lets you perform deep searches across your entire CMS using keywords or specific date ranges, even if the item is buried many folders deep.
What if I need to update field values on multiple pages? +
You use update_content_item. You provide a JSON string detailing the changes and list of items. The MCP handles applying those updates across all specified records in one go.
Does Sitecore MCP help with site structure planning? +
Yes, you can use list_item_children to see exactly what nodes are nested under a parent item. This is great for understanding the site's hierarchy before making changes.