What Is the MCP Server?
MCP stands for Model Context Protocol, an open standard that lets AI models and agents talk to external systems in a structured, safe way. In Sitecore, the Marketer MCP acts as the bridge between AI clients (like Claude Desktop, Copilot Studio, or IDEs) and Sitecore’s internal APIs. It exposes a set of “tools” that an agent can call to do real work: create pages, add components all from your IDE. (Sitecore Documentation)
Developing with MCP: A Quick Overview
- Connect an AI client to the MCP server
- Register the remote MCP endpoint (e.g., Sitecore’s Marketer MCP) in tools like Claude Desktop, Copilot Studio, or your IDE.
- Complete the OAuth authentication flow with Sitecore Identity to grant scoped access. (Sitecore Documentation)
- Choose or build your agent
- Natural-language agents (e.g., Copilot Studio agents) use MCP tools to do marketing-centric tasks.
- Custom agents or workflows can be built using the MCP + Agent API combination for deeper integration.
- Invoke Tools Instead of UIs (the big benefit)
Imagine you just created a new component (or generated it because you are already an LLM master) and you want to test it. Usually you would have to go to the page editor create a page add the components create the data etc.
Using the Sitecore MCP we can just do something like this:
“Create a new landing page called Spring Promotion under /Campaigns. Use the Landing Page template, add a hero component with the headline ‘Spring Sale Is Live’, and publish the page.”
You can probably imagine how useful this is during development and testing.
Final Thoughts
The combination of MCP and the Agent API isn’t just for marketers. Leveraging these tools can also accelerate and improve the development experience as well.