Setting Up Sitecore Marketer MCP in Claude: A Step-by-Step Guide for beginners

If you work with Sitecore, you may already use AI. If not, now is a good time to start. This guide shows you how to connect Claude to Sitecore, so you can ask it to do tasks for you. Try it and see what it can do.

Connecting Claude to Sitecore takes about five minutes and turns your content platform into something you can talk to. Instead of clicking through the Pages editor to find a page, check its components or draft a new variant, you can ask Claude in plain English and let it do the lookups and edits for you.

This post walks through the full setup of the Sitecore Marketer MCP connector in Claude, screen by screen. It also covers the one error that tends to trip people up on the way, and how to get past it.

What the connector is, and what you need first

The Sitecore connector uses the Model Context Protocol (MCP), an open standard that lets Claude call tools in other systems. Sitecore's Marketer MCP server lives at https://marketer.sitecorecloud.io/mcp/marketer-mcp-prod. Once connected, Claude can read and update sites, pages, components and content items in your Sitecore environment, acting as you.

Before you start, check three things:

•         A Sitecore Cloud Portal account. You should be able to sign in at portal.sitecorecloud.io with your work email or company SSO.

•         Access to the right organization and environment. Your account must be a member of the Sitecore organization that owns the site, with the relevant app (XM Cloud / SitecoreAI) assigned.

•         The connector added in Claude. On Team and Enterprise plans, an admin usually adds Sitecore as a custom connector. It then appears in your connector list, ready to connect.

Core integration components

Working with Claude and Sitecore revolves around three pieces: the Marketer MCP server, the Agent API beneath it, and the Claude client you connect from (claude.ai, Claude Desktop or Claude Code).

•         Sitecore Marketer MCP. Sitecore's implementation of the open MCP standard, bridging AI assistants such as Claude, Copilot Studio and Cursor to its marketing and content engine through natural language. It is included with SitecoreAI at no extra cost and needs no separate license; Sitecore charges only for the underlying API calls a workflow makes.

•         Agent API. The developer-facing engine. It wraps low-level Sitecore endpoints into business-level actions such as adding a component to a page, running an experiment or finding assets. It supports OAuth2 authentication, structured logging and distributed tracing, and has built-in rollback, so developers building on it can offer users an “Undo” for automated changes.

•         Claude clients. In claude.ai and Claude Desktop, the Marketer MCP is added as a custom connector. In Claude Code, it's added from the command line as an HTTP MCP server, which suits scripted and developer workflows.

The Marketer MCP and Agent API are part of Sitecore Studio, alongside the Blok design system and the Marketplace SDK, for teams building their own agentic extensions to SitecoreAI.

Setting it up, step by step

Step 1: Find Sitecore in your connectors

In Claude, open Settings → Connectors and stay on the Yours tab. Scroll to Sitecore (marked Custom) and click Connect.


You may see two Sitecore entries. Sitecore is the Marketer MCP server this guide covers. Sitecore Authoring API is a separate connector for authoring operations, and it connects the same way.

Step 2: Start the connection

Claude shows the connector's server address and a Connect button. If you see the message "You started connecting to Sitecore but didn't finish", an earlier attempt was interrupted. That's harmless; just click Connect again to start fresh.


Step 3: Sign in and choose your organization

A new tab opens on Sitecore Cloud's login page. Sign in with your work email or company SSO. If your account belongs to more than one Sitecore organization, you'll be asked to pick one.


Step 4: Pick the environment

Next comes Continue to Marketer MCP Server, a list of every project and environment you can reach in that organization, shown as project / environment (for example, training or dev).


Click the environment that holds your site. If the list looks wrong, use Switch organization at the top rather than cancelling. To work in a different environment later, disconnect the connector in Claude and connect again.

Step 5: Allow access

Finally, Sitecore asks you to authorize Claude. The request covers four standard scopes: openid, email, profile and offline_access. The last one lets the connection stay signed in, so you don't have to log in every session.


Check that the request names https://claude.ai/api/mcp/auth_callback as its source, then click Allow Access. The tab closes or hands you back to Claude, and Sitecore now shows as Connected in your connector list.

Sitecore's setup guide for Claude Desktop follows the same flow

If Claude reports an authentication error instead, the login didn't fully complete. Reconnect from Settings → Connectors and run through the steps again.

If you hit “Oops!, something went wrong”

The most common snag is a Sitecore Cloud page titled one-sc-production with the message “Oops!, something went wrong.” Despite the name, one-sc-production is Sitecore's login service, not your environment, and nothing in your site is broken.





The page is a dead end: the login handoff has already failed. Here's how to recover:

1.       Click “See details for this error” and note the error code. It tells you why the login failed.

2.       Close the tab. Don't refresh or press Back. The link carries a one-time token that has already been used, so reloading gives the same error.

3.       Start again from Claude by clicking Connect on the connector, ideally in a private (InPrivate or Incognito) window.

4.       Sign in with the account and organization that has Sitecore access for your project.

If it keeps happening, these are the usual causes:

Symptom

Likely cause

Fix

Error right after sign-in, every time

Stale login cookies

Clear cookies for sitecorecloud.io, or use a private window

Works in a private window only

Browser tracking prevention or an extension

Set Edge tracking prevention to Balanced, or allow sitecorecloud.io

Error after picking an org

Wrong organization or no access

Pick the right org; ask an org admin to check your membership and app access

Environment you need isn't listed

Not added to that project

Ask your Sitecore admin for access to the environment

Fails for everyone at once

Service issue

Check status.sitecore.com and try again later

Sitecore documents these Marketer MCP-specific issues:

Issue

Cause

Fix

Resource parameter is required during login

The authorization URL is missing the resource query parameter

Append &resource=https%3A%2F%2Fmarketer.sitecorecloud.io%2Fmcp%2Fmarketer-mcp-prod to the URL and open it in a new window

Access denied, or expected tools missing

Wrong organization or tenant selected, or your Sitecore role lacks those actions

Reconnect and pick the right org and tenant; ask an admin to review your role

Repeated sign-in prompts

The short-lived session has expired

Sign in again; reconnect if it persists

Slow responses or timeouts

Rate limit of 50 requests per 10 seconds, VPN, or a proxy blocking the endpoint

Wait and retry; allowlist marketer.sitecorecloud.io on your firewall or proxy

Personalization or A/B tools fail

Personalization not enabled for the tenant

Enable it and configure analytics identifiers for the site

If none of these fit, open a case through the Sitecore Cloud Portal with the error message, the tenant name and the action you were attempting.

What you can do next

With the connector live, Claude becomes a working assistant inside your Sitecore environment. Typical uses include:

•         Content audits. Ask Claude to list every page on a site, flag missing fields or find pages using an old component.

•         Page building. Have Claude create a page from a template, add components to placeholders and fill in their content.

•         Localization. Add a language version to a page and draft the translated copy for review.

•         Personalization and testing. Set up a personalized variant for an audience, or draft a component A/B test for your approval.

•         Briefs and brand. Generate content briefs grounded in your Sitecore brand kits.

Claude acts with your own permissions, so it can only see and change what your account can. Changes that matter, such as A/B tests or moving components, ask for your confirmation first, and it's good practice to review anything Claude creates before you publish.


Comments

Post a Comment

Popular posts from this blog

Migrating from Sitecore JSS SDK to Content SDK – Best Practices and Pitfalls

Image
The Sitecore JSS SDK has been a staple for building modern headless websites with XM Cloud and Sitecore XP. It offers deep integration with the Sitecore Layout Service, letting frontend developers render content directly based on Sitecore-managed components. Now, with the introduction of the Sitecore Content SDK, teams have a lightweight, REST-first way to fetch clean JSON data, leaving rendering entirely to the frontend. For projects focused on performance, composable architectures, or custom rendering logic, the Content SDK can be a compelling choice. If you’re considering a switch from JSS SDK to Content SDK, this guide walks you through how to migrate, best practices, and the pitfalls to avoid. Why Migrate to Content SDK? Lightweight: No dependency on Layout Service rendering. Faster payloads: Returns only the requested fields, reducing over-fetching. Flexible rendering: Total control of frontend presentation. Better for static generation: Idea...
Read more

SUGCON India 2026 – A Journey of Learning and Connections

Image
This year, SUGCON India  was held in Delhi on 4th and 5th June 2026 , bringing together Sitecore professionals, developers, architects, marketers, partners, and community members from across the ecosystem. It was an incredible event filled with learning, networking, community interactions, and valuable insights into the future of digital experiences. Before sharing my experience, I would like to extend a special thanks to the entire organizing team ,  involved in making SUGCON India 2026 a success. The event was exceptionally well-organized, seamless from start to finish, and a reflection of the tremendous effort, dedication, and hard work put in behind the scenes. Every detail, from registrations and sessions to networking opportunities and attendee experience was thoughtfully managed. Kudos to the entire team for delivering such an amazing experience! A Different SUGCON Experience This year's SUGCON was especially meaningful for me because it gave me the opportunity to ...
Read more

Beginner’s Guide: Step-by-Step Local Installation for Sitecore XM Cloud

Image
Many times, we want to accomplish a task but aren’t sure where to start—the same applies to Sitecore XM Cloud local setup and installation. In this guide, I’ll Walk you through the process of setting up a Sitecore XM Cloud environment locally, step by step. Sitecore XM Cloud is the cloud-native, headless version of Sitecore Experience Manager (XM), designed for modern, omnichannel digital experiences. It separates content management (authoring) from content delivery, enabling fast, API-driven, and scalable architectures. Developers can deliver content to web, mobile, and other channels via GraphQL APIs and Experience Edge, while content authors manage items in a cloud-first environment. Even though XM Cloud is cloud-first, a local environment is essential for: Experimenting safely with content, templates, and workflows. Testing headless frontends like Angular, React, or Next.js. Debugging GraphQL queries and APIs efficiently. Validating scheduled tasks...
Read more