MCP Server

Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol server for Sitecore. The mcp mcp server is what makes that connection.

What the server does

An open-source Model Context Protocol server that gives AI agents (Claude, ChatGPT, Cursor, and others) direct read/write access to Sitecore. It bridges the gap between modern AI-driven workflows and Sitecore CMS, eliminating manual copy-paste between tools.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: TRANSPORT, GRAPHQL_ENDPOINT, GRAPHQL_SCHEMAS, GRAPHQL_API_KEY, GRAPHQL_HEADERS, ITEM_SERVICE_DOMAIN, ITEM_SERVICE_USERNAME, ITEM_SERVICE_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by Antonytm; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.