MCP Sitecore Server

Name: MCP Sitecore Server
Author: Antonytm

by Antonytmversion 1.3.2i★ –iRuns on your computer

Registry nameio.github.Antonytm/mcp-sitecore-server

Install

Overview

Description from the maker (original English)

A Model Context Protocol server for Sitecore

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sitecore": {
      "command": "npx",
      "args": [
        "-y",
        "@antonytm/mcp-sitecore-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add sitecore -- npx -y @antonytm/mcp-sitecore-server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sitecore": {
      "command": "npx",
      "args": [
        "-y",
        "@antonytm/mcp-sitecore-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sitecore": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@antonytm/mcp-sitecore-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Antonytm, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32678 servers in this category
Published to the registry more recently than 0% of the other 32678 servers in this category
Basic checks equal to or better than 100% of the other 32678 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Sitecore Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.2) reached the registry 14 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Starreel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Starreel

by starreel

Turn a script into a finished, downloadable short-drama episode — via MCP or REST.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sitecore Community MCP

This repository contains the source code for the Sitecore Community MCP server — an open-source Model Context Protocol server that gives AI agents direct read/write access to Sitecore, so you stop copy-pasting between your agent and the Content Editor.

121 tools across search, query, create, read, update, delete, media, PowerShell, logging, security and presentation
Three guides — guide://compose-page, guide://bulk-update and guide://diagnose-connection — resources an agent can read mid-task: two common, complex workflows that you'd want to use this MCP for, plus a connection issue self diagnosis helper.
Covers four Sitecore API surfaces: the Authoring and Management GraphQL API, the Item Service, GraphQL Edge and Sitecore PowerShell Extensions
Works with SitecoreAI and Sitecore XM/XP (all versions), from any MCP-compatible client
Implements MCP protocol revision 2026-07-28, and answers the older initialize handshake from the same tool registrations — negotiating down to any revision from 2025-11-25 to 2024-10-07, so a client on either era sees the same tools
Reported impact: 5× faster Figma-to-Sitecore workflows and ~70% less manual scaffolding (case study)
Three ways to run it: npm, Docker, or from source

Getting started with Sitecore Community MCP

To run the Sitecore Community MCP server, you need:

Node — the latest long-term support (LTS) release.
A Sitecore XM, XP or SitecoreAI instance. Which parts you enable decides which tools work: the authoring.* groups need only the Authoring and Management API (normally already on in the cloud) plus a token, while the Item Service and SPE Remoting are off by default and need a config patch. Preparing your Sitecore instance covers all three and how to verify each.

Adding the server to your MCP client

Add the entry below to your client's server map — mcpServers in Cursor, Claude Code and most other clients, servers in VS Code — and fill in your own endpoints and credentials:

"mcpServers": { "sitecore-mcp": { "type": "stdio", "command": "npx", "args": ["@antonytm/mcp-sitecore-server@latest"], "env": { "TRANSPORT": "stdio", "GRAPHQL_ENDPOINT": "https://xmcloudcm.localhost/sitecore/api/graph/", "GRAPHQL_SCHEMAS": "edge", "GRAPHQL_API_KEY": "{6D3F291E-66A5-4703-887A-D549AF83D859}", "GRAPHQL_HEADERS": "", "ITEM_SERVICE_DOMAIN": "sitecore", "ITEM_SERVICE_USERNAME": "admin", "ITEM_SERVICE_PASSWORD": "b", "ITEM_SERVICE_SERVER_URL": "https://xmcloudcm.localhost/", "POWERSHELL_DOMAIN": "sitecore", "POWERSHELL_USERNAME": "admin", "POWERSHELL_PASSWORD": "b", "POWERSHELL_SERVER_URL": "https://xmcloudcm.localhost/", "AUTHORING_CLIENT_ID": "", "AUTHORING_CLIENT_SECRET": "", "TOOL_PROFILE": "" } } } }

TOOL_PROFILE takes a comma-separated list of presets, and unions what each one hides. Every preset names something absent or unwanted rather than a platform. Four name an API surface your instance does not serve — `no-spe`, `no-item-service`, `no-edge-graphql` and `no-authoring-api` — so an instance missing two of them can say so. `no-account-management` is the one that is not about a missing surface: it hides the twelve tools that create or edit an account on the CM, for a deployment that would rather an agent could not do that at all (item security, and reading accounts and roles, are untouched):

TOOL_PROFILE=no-spe,no-item-service

no-spe is the big one: without SPE installed and its remoting service enabled, roughly three quarters of this server's tools cannot run, and hiding them is schema an agent no longer pays for on every turn. An unknown name is reported on stderr and ignored, leaving the rest of the list in force.

Every setting is documented in Configuration. Agents have a limit on how many tools they can hold, so before you get far, read Tool selection and trim the surface with TOOL_PROFILE, TOOL_GROUPS and DISABLED_TOOLS.

To run the server in a container or from source instead, see Running the server.

How this compares to the Sitecore Marketer MCP

Sitecore's own Marketer MCP is a hosted service aimed at marketers on SitecoreAI. This server is the developer-grade counterpart, and on that ground it is the stronger tool:

	Sitecore Community MCP	Sitecore Marketer MCP
Platforms	SitecoreAI and XM/XP, all versions — including your local Docker CM	SitecoreAI only
Hosting	Self-hosted (npm, Docker, source); credentials never leave your infrastructure	Hosted by Sitecore; OAuth through the cloud
Surface	121 tools across the full developer surface: items, templates, presentation, media, security, indexing, logs, publishing, GraphQL, raw PowerShell	Marketer operations: pages, components, briefs, brand kits, personalization, A/B tests
Escape hatch	`run-powershell-script`, raw Edge GraphQL and raw Authoring GraphQL — if a tool doesn't exist, the capability still does	Closed tool set
Layout safety	`add-rendering-to-placeholder` _refuses_ components the placeholder settings forbid, naming the allow-list	Writes are not validated against placeholder settings
Tool gating	`TOOL_GROUPS` / `DISABLED_TOOLS` / `TOOL_PROFILE` trim the schema cost per turn	Fixed tool list

They are complementary rather than exclusive: the Marketer MCP carries the cloud marketing features this server has no API for (briefs, brand kits, personalization variants, A/B tests), and nothing stops a client from connecting both. For building, migrating, auditing and operating Sitecore solutions, this server is the one with the depth.

Documentation and community resources

Preparing your Sitecore instance — SPE Remoting, the Item Service, GraphQL keys, and the config patch that enables them
Running the server — npm, Docker, from source, and the two transports
Tool reference — every tool, grouped by API surface
Configuration — environment variables, transports, timeouts and TLS
Tool selection — TOOL_GROUPS, DISABLED_TOOLS and TOOL_PROFILE
Guides — the guide://compose-page, guide://bulk-update and guide://diagnose-connection resources, and when each is offered
Docker images — the published Linux and Windows images
Changelog — what's new in 2.0 and its breaking changes

Community resources:

Contributions

We are very grateful to the community for contributing bug fixes and improvements. We welcome all efforts to evolve and improve this server; read below to learn how to participate in those efforts.

Contributing Guide

Read our contributing guide to learn about our development process, how to propose bug fixes and improvements, and how to build, debug and test your changes.

License

Sitecore Community MCP is using the Apache 2.0 license.

Support

This is a community project and is not supported by Sitecore.

Issues, bugs and feature requests: open an issue at Antonytm/mcp-sitecore-server/issues.
Questions about Sitecore itself: Sitecore Stack Exchange or the Sitecore Community Slack will serve you better than a GitHub issue.

MCP Sitecore Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Starreel

README from the maker

Sitecore Community MCP

Getting started with Sitecore Community MCP

Adding the server to your MCP client

How this compares to the Sitecore Marketer MCP

Documentation and community resources

Contributions

Contributing Guide

License

Support