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.
- App credentials
- Free 14-day trial
- No credit card
Find the brief for the spring campaign landing page
Working in Sitecore with Elaichi
-
Sitecore agent assets search
-
Get single Sitecore agent asset by ID
-
List all Sitecore agent brand context items
How to connect Sitecore to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Sitecore MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Sitecore MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Sitecore through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Sitecore is logged.
-
Content
Draft a page from an approved brief
Pull up the brief, read its requirements, and have the draft content item created in Sitecore ready for review. No copying between tabs.
-
Marketing
Find the right asset before launch
Search Sitecore assets by what you remember about them, confirm it is the approved version, and get the details you need for the campaign.
-
Brand
Check copy against the brandkit
Ask for the brandkit and brand context behind a campaign, then compare a draft with the tone and rules before it goes live.
-
Web
Fix a stale page by its path
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.
-
Design
Reuse the right component and datasource
List the components already in Sitecore, find the one that fits, and create the datasource for a new section without starting from scratch.
-
Communications
Keep announcements current after a change
Look up the announcement content, update the wording after a policy or leadership change, and retire the content item that no longer applies.
Try asking
- “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”
What connecting Sitecore gets you
6 screens from Elaichi, each doing one job for your Sitecore account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Sitecore questions in plain language.
Get answers from live content items, briefs and assets, not from a stale export.
Copy the endpoint
AI apps
One Sitecore endpoint, every MCP client.
Claude, ChatGPT and Cursor connect to one org endpoint, with no SDK and no shared API key.
Tool catalog
353 Sitecore tools, ready without writing code.
Content items, assets, briefs, brandkits and components, all covered without custom code.
Toolboxes
Every team gets its own Sitecore toolbox.
Content, brand and web teams each see the Sitecore tools their work needs.
Shared connections
Share Sitecore access without sharing a credential.
One person connects Sitecore, teammates work through it and never see the app credentials.
Audit log
Every Sitecore change has a name on it.
See who created, updated or deleted which content item, and when.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Sitecore digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch content items
Sitecore
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Sitecore
Queued
Workflows
A schedule starts Sitecore work, not a question.
New briefs are fetched, grouped and drafted into a digest, approved, then posted to Sitecore.
Sitecore health
Refreshed 4 minutes ago · every 15 minutes · from the content items collection
Content items
1,284 ↓ 12%
Assets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Content items created
Last 14 days
By team
Share of activity
Marketing 34%
Content EMEA 27%
Brand 21%
Web team 18%
Collections and dashboards
Sitecore health numbers, computed with no model.
Content items created over 14 days, broken down by team, refreshed on a schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Sitecore tools for your AI agents
353 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sitecore, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 206 of 353 Sitecore tools here. Connect Sitecore and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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 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.
Put Sitecore in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot