# Sitecore MCP connector

Connect Sitecore to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can search, create and update Sitecore content items, assets, briefs, brandkits and components, each person working inside their own Sitecore access.

Source: https://elaichi.ai/connectors/sitecore/

## Facts

| | |
| --- | --- |
| Application | Sitecore |
| Category | Knowledge Management |
| AI tools | 353 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Sitecore is connected

- Find the brief for the spring campaign landing page
- List our brandkits and summarize the tone rules for retail
- Update the pricing page content with the new plan names

## Connect Sitecore in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Sitecore.
2. Optionally set Share with, then press Connect.
3. Paste your Sitecore app credentials. Sitecore authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Sitecore tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Sitecore MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Sitecore MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Sitecore MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Sitecore MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Sitecore MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Sitecore to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Sitecore tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Sitecore through Elaichi

### Draft a page from an approved brief

Content. Pull up the brief, read its requirements, and have the draft content item created in Sitecore ready for review. No copying between tabs.

### Find the right asset before launch

Marketing. Search Sitecore assets by what you remember about them, confirm it is the approved version, and get the details you need for the campaign.

### Check copy against the brandkit

Brand. Ask for the brandkit and brand context behind a campaign, then compare a draft with the tone and rules before it goes live.

### Fix a stale page by its path

Web. Point at a page by its Sitecore path, see what it currently says, and update the content item in place after a product or pricing change.

### Reuse the right component and datasource

Design. List the components already in Sitecore, find the one that fits, and create the datasource for a new section without starting from scratch.

### Keep announcements current after a change

Communications. Look up the announcement content, update the wording after a policy or leadership change, and retire the content item that no longer applies.

## Elaichi vs Zapier MCP vs Composio for Sitecore

All three can connect Sitecore to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Sitecore tools | Allow or restrict single Sitecore tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Sitecore call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Sitecore to Claude?

Connect Sitecore in Elaichi first, which asks for your Sitecore app credentials, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Sitecore is ready in Claude. Short, concrete asks about Sitecore content tend to work better than long sentences.

### Does Sitecore work with ChatGPT and Cursor as well as Claude?

Yes. Once Sitecore is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Sitecore once and every client picks it up.

### What can an AI agent actually do with my Sitecore data?

It can search Sitecore content items, assets, briefs, brandkits, brand contexts and components, look up a page by its path, and read the details of any one of them. It can also create and update content items, assets, briefs and component datasources, and delete a content item when asked. In practice that means drafting a page from a brief, checking copy against the brandkit, or fixing a stale page, all from a chat window.

### Does connecting Sitecore give the AI access to all of my Sitecore content?

No. Every call runs as the person who signed in, so the agent sees only the Sitecore content items, assets and briefs that person can already see in Sitecore. Elaichi can narrow that further with roles and restrictions, but it never widens what Sitecore itself allows.

### Can my team share one Sitecore connection?

Yes. One person connects Sitecore with the app credentials and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every Sitecore change in the audit log names the actual person.

### Can I stop an agent from deleting or changing things in Sitecore?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting or updating Sitecore content items for a role or for one person while leaving search and reading open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Sitecore connection when someone leaves?

Offboarding that person in Elaichi ends their access to Sitecore through every client at once. A shared Sitecore connection keeps working for everyone else on the team. If you want to remove Sitecore entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Sitecore MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Sitecore is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Sitecore?

Yes. Both let Claude, ChatGPT or Cursor use Sitecore. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Sitecore call.

### How is Elaichi different from Composio for Sitecore?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Sitecore: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 353 Sitecore tools

Every tool below is callable through https://api.elaichi.ai/mcp once Sitecore is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Sitecore agent asset** (Create). Upload an asset. Uploads a new digital asset to the system and stores it with the provided metadata. [Agent API (environment automation client)] Required: file, upload_request.
- **Sitecore agent assets search** (Search). Search for assets. Searches for digital assets such as videos, images, and documents using query terms, file types, or tags. Limitations - Asset search results are limited to a maximum of 10 items per request. - This endpoint doesn't support pagination. [Agent API (environment automation client)]
- **Get single Sitecore agent asset by ID** (Get). Retrieve the asset details. Retrieves the details of a specific digital asset by specifying its ID. [Agent API (environment automation client)] The id is the assetId. Required: id.
- **Update a Sitecore agent asset by ID** (Update). Update an asset. Updates the metadata and properties of an existing digital asset, such as alt text, description, and tags. [Agent API (environment automation client)] The id is the assetId. Required: id, fields, language.
- **List all Sitecore agent brand context items** (List). Batch retrieve brand context items. Retrieves specific files or folders from a brand context in a single batched call. File responses include Markdown content. Between 1 and 50 unique IDs per call. [Agent API (environment automation client)] Required: brand_context_id, ids.
- **List all Sitecore agent brand contexts** (List). List brand contexts. Retrieves all brand contexts available within an organization. Returns metadata only; document content is not included. [Agent API (environment automation client)]
- **Get single Sitecore agent brand context by ID** (Get). Retrieve a brand context by ID. Retrieves a brand context's metadata and its complete nested folder or file tree index. No document content is included. [Agent API (environment automation client)] The id is the brandContextId. Required: id.
- **List all Sitecore agent brandkits** (List). List brand kits. Retrieves all brand kits available within an organization. [Agent API (environment automation client)]
- **Get single Sitecore agent brandkit by ID** (Get). Retrieve a brand kit by ID. Retrieves a brand kit by ID, including its sections and associated fields (subsections). [Agent API (environment automation client)] The id is the brandkitId. Required: id.
- **List all Sitecore agent brief types** (List). List brief types. Retrieves a list of available brief types, including their metadata and field definitions such as field types, labels, validation rules, and other information used by AI when generating briefs. [Agent API (environment automation client)]
- **Get single Sitecore agent brief type by ID** (Get). Retrieve a brief type by ID. Retrieves a specific brief type by its ID, including its field definitions and metadata. [Agent API (environment automation client)] The id is the brief_type_id. Required: id.
- **List all Sitecore agent briefs** (List). List briefs. Retrieves a list of briefs in your organization. [Agent API (environment automation client)]
- **Create a Sitecore agent brief** (Create). Create a brief. Creates a brief using the specified brief type ID, locale, and provided data fields. The new brief is saved as a draft in the Brief management tool. [Agent API (environment automation client)] Required: name, locale, briefTypeId.
- **Get single Sitecore agent brief by ID** (Get). Retrieve a brief by ID. Retrieves a specific brief by its ID, including its fields, type reference, and metadata. [Agent API (environment automation client)] The id is the brief_id. Required: id.
- **Update a Sitecore agent brief by ID** (Update). Update a brief. Partially updates an existing brief using the provided fields. Only the fields included in the request body will be updated; all other existing fields will remain unchanged. [Agent API (environment automation client)] The id is the brief_id. Required: id.
- **Create a Sitecore agent component datasource** (Create). Create a component datasource. Creates a new datasource item for a specific component using the provided data field values. The datasource will be created in the appropriate location based on the component's configuration. [Agent API (environment automation client)] Required: component_id, siteName, dataFields.
- **Sitecore agent component datasources search** (Search). Search for component datasources. Searches for available datasources that can be used with a specific component. This helps you find existing content to use as datasources. [Agent API (environment automation client)] Required: component_id, term.
- **List all Sitecore agent components** (List). List components. Retrieves a list of components available for a specific site, including both built-in components and custom components that can be used on pages. [Agent API (environment automation client)] Required: site_name.
- **Get single Sitecore agent component by ID** (Get). Retrieve the component details. Retrieves the details of a specific component, including its ID, name, and datasource options. [Agent API (environment automation client)] The id is the componentId. Required: id.
- **Create a Sitecore agent content** (Create). Create content item. Creates a new content item using the specified template and field values. [Agent API (environment automation client)] Required: templateId, name, parentId.
- **Get single Sitecore agent content by ID** (Get). Retrieve a content item by ID. Retrieves the details of a specific content item by specifying its ID. [Agent API (environment automation client)] The id is the itemId. Required: id.
- **Update a Sitecore agent content by ID** (Update). Update a content item. Updates an existing content item, including its fields and language. [Agent API (environment automation client)] The id is the itemId. Required: id.
- **Delete a Sitecore agent content by ID** (Delete). Delete a content item. Deletes a content item and all its child items across all languages by moving them to the recycle bin, where they can be restored. If remove_references=true, all page components that use the item as a datasource are also removed. [Agent API (environment automation client)] The id is the itemId. Required: id.
- **Sitecore agent content lookup by path** (Action). Retrieve a content item by path. Retrieves the details of a content item by specifying its path in the content tree. [Agent API (environment automation client)] Required: item_path.
- **List all Sitecore agent content insert options** (List). List insert options. Retrieves a list of content templates that can be inserted as child items under the specified parent item. [Agent API (environment automation client)] Required: item_id.
- **List all Sitecore agent content referrers** (List). List items that reference a content item. Retrieves the items that reference the specified content item, so you can identify what may be affected before changing it. [Agent API (environment automation client)] Required: item_id, site.
- **Create a Sitecore agent experiment** (Create). Create an A/B/n test on a component. Creates a new A/B/n test for a specific component on a page. This allows you to compare two or more variants of the component and determine which one performs better. [Agent API (environment automation client)] Required: site_id, page_id, component_id, name, goal_type, variants.
- **Update a Sitecore agent experiment by ID** (Update). Update an A/B/n test on a component. Updates an existing A/B/n test for a specific component on a page. This allows you to modify the variants, targeting rules, or other settings of the test. [Agent API (environment automation client)] The id is the flowId. Required: id.
- **Sitecore agent flow variants reset** (Action). Reset component variant. Removes any applied personalization or A/B/n test variant set up, such as copy, hide, or swap, from a component and restores it to its original state. [Agent API (environment automation client)] Required: flow_id, page_id, component_id.
- **Create a Sitecore agent flow variant** (Create). Set up a component variant. Sets up a variant for a specific A/B/n test or personalization by copying, hiding, or swapping the original component. [Agent API (environment automation client)] Required: flow_id, variant_id, page_id, component_id, variant_strategy.
- **Get single Sitecore agent flow variant by ID** (Get). Get flow definition variant details. Retrieves the details of a specific A/B/n test or personalization variant, including its datasource and components. [Agent API (environment automation client)] The id is the variantId. Required: id, flow_id.
- **List all Sitecore agent flows** (List). List flow definitions for a page. Retrieves all flow definitions (both A/B/n tests and personalizations) for a specific page, including the structure, variants, and configuration details. [Agent API (environment automation client)] Required: page_id.
- **Get single Sitecore agent flow by ID** (Get). Retrieve a flow definition. Retrieves a specific flow definition (A/B/n test or personalization) on a page, including the structure, variants, and configuration details. [Agent API (environment automation client)] The id is the flowId. Required: id.
- **Create a Sitecore agent generated brief** (Create). Generate a brief. Generates a brief draft and the content of its fields, using the specified brief type, brand kit, and prompt. This endpoint does not save the generated draft. [Agent API (environment automation client)] Required: briefTypeId, brandId, prompt.
- **Create a Sitecore agent generated briefs deprecated** (Create). DEPRECATED (Sitecore scheduled removal on September 20, 2026): Generate a brief. Generates a brief and the content of its fields, using the specified brief type, brand kit, and prompt. This endpoint does not save the generated draft. You can copy the response and use the Create a brief endpoint to save it in the Brief management tool. [Agent API (environment automation client)] Required: briefTypeId, brandId, prompt.
- **List all Sitecore agent job operations** (List). List job operations. Retrieves a list of actions associated with a specific job ID, including operation type, status, and timestamps, to support tracing and potential reversion of those actions. [Agent API (environment automation client)] Required: job_id.
- **Sitecore agent jobs revert** (Action). Revert a job. Reverts the operations linked to a specific job ID, restoring the state prior to execution. This is useful for undoing changes made by automated processes. [Agent API (environment automation client)] Required: job_id.
- **Get single Sitecore agent job by ID** (Get). Retrieve job details. Retrieves the details of a specific job. [Agent API (environment automation client)] The id is the jobId. Required: id.
- **List all Sitecore agent languages** (List). List languages. Retrieves all languages available. [Agent API (environment automation client)]
- **Sitecore agent page component datasources assign** (Assign). Set the component datasource. Sets the datasource for a specific component on a page. You can specify a new data source item or clear the existing one. [Agent API (environment automation client)] Required: page_id, component_id, datasourceId.
- **Sitecore agent page component positions bulk update** (Update). Move a component on a page. Moves a component instance before or after another component instance on the base page layout. Components can move between compatible editable placeholders. Use targetPlaceholderPath when moving into an empty placeholder. [Agent API (environment automation client)] Required: page_id, component_instance_id.
- **Create a Sitecore agent page component** (Create). Add a component to a page. Adds a component to a specific placeholder on a page. You can specify the component type, placeholder location, and configure its initial settings. Optionally, you can specify its position relative to an existing component. [Agent API (environment automation client)] Required: page_id, componentRenderingId, placeholderPath, componentItemName.
- **List all Sitecore agent page components** (List). Retrieve components on a page. Retrieves the components on a page. [Agent API (environment automation client)] Required: page_id.
- **Delete a Sitecore agent page component by ID** (Delete). Remove component on page. Removes a specific component from a page. Use this to clean up orphaned component references after deleting a datasource item. [Agent API (environment automation client)] The id is the componentId. Required: id, page_id.
- **List all Sitecore agent page HTML** (List). Retrieve the page HTML. Retrieves the HTML for a specific page. This endpoint returns the raw HTML of the page as it would appear in the browser. [Agent API (environment automation client)] Required: page_id, language.
- **Create a Sitecore agent page language** (Create). Add a language version to a page. Adds a new language version for an existing page. This allows you to have the same page content available in multiple languages. [Agent API (environment automation client)] Required: page_id.
- **List all Sitecore agent page placeholder allowed components** (List). List allowed components for a placeholder. Retrieves the list of components that can be added to a placeholder on a page. This helps ensure that only compatible components are used in each placeholder. [Agent API (environment automation client)] Required: page_id, placeholder_name.
- **List all Sitecore agent page preview URLS** (List). Retrieve the page preview URL. Retrieves the preview URL for a specific page. [Agent API (environment automation client)] Required: page_id.
- **List all Sitecore agent page screenshots** (List). Retrieve the screenshot of a page. Captures and returns a base64-encoded screenshot of a page. [Agent API (environment automation client)] Required: page_id, version.
- **Sitecore agent page templates lookup by ID** (Action). Retrieve the page template by ID. Retrieves the details of a specific page template, including its fields and settings. Use this endpoint to understand the structure and available fields of a template before creating a page. [Agent API (environment automation client)] Required: templateId.
- ...and 303 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
