Sitecore AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SITECORE_SCOPE | No | OAuth scope, if your identity server requires one | |
| SITECORE_API_URL | Yes | Content Management GraphQL endpoint, e.g. https://<cm-host>/sitecore/api/authoring/graphql/v1 | |
| SITECORE_AUDIENCE | No | OAuth audience, if your identity server requires one | |
| SITECORE_CLIENT_ID | Yes | OAuth client id | |
| SITECORE_TOKEN_URL | Yes | OAuth token endpoint (identity server), e.g. https://auth.sitecorecloud.io/oauth/token | |
| SITECORE_ALLOW_PATHS | No | Readable path prefixes. Anything not matched is denied. | /sitecore/content,/sitecore/media library |
| SITECORE_CLIENT_SECRET | Yes | OAuth client secret | |
| SITECORE_DEVELOPER_MODE | No | When true/1/yes/on, lifts the block on the protected areas. | false |
| SITECORE_PROTECTED_PATHS | No | Blocked outright unless developer mode is on. | /sitecore/system,/sitecore/templates,/sitecore/layout |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_item_detailA | Fetch a single Sitecore / XM Cloud item's full details: id, name, path, template name, display name, all field names/values, and children count. |
| list_itemsA | List the immediate children of a Sitecore / XM Cloud item. Optionally filter by template id. Returns id, name, path, template name and display name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches detailed information about a single item, while the other lists children of an item. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: 'get_item_detail' and 'list_items'. The naming is predictable and conventional.
With only 2 tools, the server feels minimal but not unreasonable for a focused read-only item browsing scenario. The count is borderline per the calibration.
The tools only support reading item details and listing children. Missing write operations (create, update, delete), search, or other content management features leave significant gaps for a Sitecore server.