Sitecore Community MCP: operate Sitecore from an agent
Sitecore Community MCP
A community MCP server with 121 tools for Sitecore XM, XP and SitecoreAI: items, templates, media, presentation and PowerShell
- 52 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The server creates, changes and deletes CM items and accounts, and run-powershell-script executes arbitrary PowerShell
- Sitecore passwords and keys sit in the client's environment variables
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/sitecore-community-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The server creates, changes and deletes CM items and accounts, and run-powershell-script executes arbitrary PowerShell
- Sitecore passwords and keys sit in the client's environment variables
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to Sitecore so you stop copying data between chat and the Content Editor. It covers four APIs: Authoring and Management GraphQL, Item Service, GraphQL Edge and Sitecore PowerShell Extensions. In total there are 121 tools for searching, reading, creating, updating and deleting items, and for media, security, logs, indexing, publishing and presentation. It works with SitecoreAI and with Sitecore XM and XP of any version, including a local Docker CM instance. Three guide resources, guide://compose-page, guide://bulk-update and guide://diagnose-connection, can be read mid-task: building a page, bulk updates and connection self-diagnosis. When no ready tool exists, run-powershell-script and raw GraphQL remain. add-rendering-to-placeholder refuses a component that the placeholder settings forbid and names the allowed list. TOOL_PROFILE, TOOL_GROUPS and DISABLED_TOOLS trim the tool set so the schema takes less of the context.
Who it is for. Sitecore developers and administrators who build, migrate and audit solutions on XM, XP or SitecoreAI and want an agent to take over the routine.
Good fit when
- Update fields across hundreds of items in bulk and verify the result before publishing
- A page is assembled from components by a design, and the agent must place them in placeholders with rule checks
- Audit access rights and roles on a CM before a release
- You cannot connect to an instance and need self-diagnosis across GraphQL, Item Service and SPE
- Migrating templates and content between environments
Not a fit when
- You need cloud marketing features: briefs, brand kits, personalization and A/B tests. Sitecore has its own Marketer MCP for those
- The instance is unreachable from where the server runs: GraphQL and PowerShell Remoting both need access
- The agent must not touch accounts: enable no-account-management or pick another tool
- You need vendor-backed support: this is a community project that Sitecore does not support
Example request
Find all items of the Article template with an empty Summary field, show the list, and after I confirm fill the field from the title.MCP
- Transport
- stdio, http
- Authentication
- key is optional
Environment variables
GRAPHQL_ENDPOINTrequired- Sitecore GraphQL endpoint URL
GRAPHQL_API_KEYsecret- GraphQL Edge API key
ITEM_SERVICE_PASSWORDsecret- Item Service user password
POWERSHELL_PASSWORDsecret- SPE Remoting user password
TOOL_PROFILE- Comma-separated profiles that hide tools
Limitations
This is a community project that Sitecore does not support. Which tools work depends on how the instance is set up: the authoring groups need only the Authoring and Management API and a token, while Item Service and SPE Remoting are off by default and need a config patch. Without SPE roughly three quarters of the tools cannot run.
121 tools weigh on the agent context, so narrow the set with TOOL_PROFILE before real work. Passwords and keys are passed through the client's environment variables.
How to disable. Remove the sitecore-mcp entry from mcpServers in the client config. If the server ran in Docker, stop the container. It is wise to revoke the Sitecore credentials it was given.
FAQ
How does it differ from Sitecore Marketer MCP?
Marketer MCP is hosted by Sitecore and aimed at SitecoreAI marketers: pages, briefs, brand kits, personalization. This server runs on your side, covers XM, XP and SitecoreAI, and gives 121 developer tools. A client can connect both.
What must be configured in Sitecore before starting?
The authoring groups need only the Authoring and Management API and a token. Item Service and SPE Remoting are off by default and are enabled with the config patch described in docs/sitecore-setup.md.
How do I reduce the number of tools?
Set TOOL_PROFILE: no-spe, no-item-service, no-edge-graphql, no-authoring-api or no-account-management. TOOL_GROUPS and DISABLED_TOOLS select more precisely. Profiles can be listed with commas.
How do I run the server?
Three ways: through npm with npx @antonytm/mcp-sitecore-server@latest, in a Docker image for Linux or Windows, or from source. Transports are stdio and HTTP.
Can the server delete items?
Yes. Among the 121 tools are creating, updating and deleting items, and editing accounts. The no-account-management profile switches off the twelve account tools.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for AEM Content Manager: the agent validates and runs Groovy scripts on Adobe Experience Manager and reads run history
Sanity's official agent kit: a remote MCP with project access, skills on content modeling, SEO and migrations, and plugins
Kirby MCP gives an agent a Kirby CMS project: structure, live content, debugging and a bundled Kirby knowledge base
FireCMS Cloud MCP server: an agent reads Firestore data, infers collection schemas and manages the project's users.
PubNub MCP: PubNub docs and apps in an agent
PubNub MCP Server
PubNub's official MCP server: SDK docs in 20 languages and management of apps, keysets, channels and analytics from an agent
An MCP server that loads a Swagger or OpenAPI spec and turns every API endpoint into a tool the agent can call.
README in short
The docs describe preparing an instance, three ways to run, a tool reference grouped by API surface, configuration and tool selection, three guides and the Docker images. A table compares the project with Sitecore's own Marketer MCP. The author quotes a case study claiming Figma-to-Sitecore work is five times faster.