From Prompt to Production: Agentic Sitecore Workflows with MCP
Two practical paths: Option A (Marketer MCP, no code) and Option B (Community MCP server, extensible). We’ll go from a natural‑language prompt to a published landing page. Previously on the blog This article continues my earlier post, MCP‑Powered AI Development Workflow in Sitecore XM Cloud — a quick conceptual primer. Why MCP (in one paragraph) MCP → Safe, typed tools Model Context Protocol (MCP) turns natural language into governed, typed tool calls. In Sitecore, Marketer MCP exposes tools like create page , add component , and upload asset that map to the Agent API so agents can take real actions with guardrails and auditing. The agentic workflow: how it works When you chat with Claude (which is already connected to your Marketer MCP), Claude acts as an AI agent — it calls the Sitecore APIs on your behalf, fetches IDs, makes decisions, and creates items without you needing to open Sitecore at all. Architecture Overview Prer...