Contentful MCP connector
The Contentful connector brings entries, assets, content types, releases and locales into Elaichi, so Claude, ChatGPT, Cursor and the Elaichi Agent can read and update your spaces as each signed-in person, with every change logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Contentful to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Contentful once
-
Open Connections, choose Add connection, and pick Contentful.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Contentful. Contentful's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Contentful 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.
Contentful 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 today. The plugin directory lives at chatgpt.com/plugins.
Contentful 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.
Connect Contentful 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.
Use cases
What teams do with Contentful through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Draft the landing page entry before launch
Ask for a new landing page entry in the marketing space with the headline, hero asset and call to action already filled in. Review it in Contentful and publish when the campaign is ready.
-
Content
Find every entry that mentions old pricing
Ask which entries across your spaces still reference last year's plan names, then have each one updated with the new wording. Nothing goes live until an editor publishes it.
-
Localization
See which locales are still missing translations
Ask which entries have a German or Japanese field left empty before a regional launch. Send the list to translators or draft the missing fields for review.
-
Product
Check what is in the next release
Ask what entries sit inside the release scheduled for Thursday and whether any are still in draft. Add the late release notes entry without opening the release yourself.
-
Documentation
Update a help article after a policy change
Ask for every help center entry that describes the refund process, then have the changed paragraph rewritten in each one. Each edit appears in Contentful as a draft under your name.
-
Engineering
Confirm a content type before changing a field
Ask which content types use a given field and how many entries would be affected in the staging environment. Add the new field once the answer is clear.
Try asking
- “Which entries in the marketing space are still in draft?”
- “List assets uploaded this week that have no alt text.”
- “What is in the spring launch release and is it ready?”
Compare
Elaichi vs Zapier MCP vs Composio for Contentful
All three can connect Contentful 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 Contentful tools | Allow or restrict single Contentful 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 Contentful 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 | $15 per user per month. | 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.
See it in Elaichi
What connecting Contentful gets you
5 screens from the product, each doing one job for your Contentful account.
The agent
Ask about your Contentful entries in plain language.
Three starter prompts pull answers from live entries, assets and releases in Contentful.
- entries
- assets
- content types
- releases
Ask Elaichi to work across your apps.
Which entries in the marketing space are still in draft?
List assets uploaded this week that have no alt text.
What is in the spring launch release and is it ready?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Contentful to every MCP client.
Claude, ChatGPT and Cursor reach Contentful through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Contentful toolbox.
Marketing, Localization and Engineering each work from a toolbox scoped to their part of Contentful.
- Marketing
- Content
- Localization
- Product
ElaichiToolboxesShared connections
Share a Contentful connection, never a credential.
One person connects Contentful, teammates work through it, and nobody else sees a token.
- Marketing site
- Help center
- Localization
- Product launches
ElaichiConnectionsAudit log
Every Contentful change answers who did what.
When, who, what happened and which entry, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Contentful work and finishes it.
New Contentful entries are fetched, grouped, drafted into a digest, approved, then posted back.
Contentful digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch entries
Contentful
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 Michael Brennan
Approve Deny -
Post the digest
Contentful
Queued
Collections and dashboards
Contentful health numbers arrive without anyone asking.
Four metrics, 14 days of entries created and a team breakdown, computed with no model involved.
Contentful health
Refreshed 4 minutes ago · every 15 minutes · from the entries collection
Entries
1,284 ↓ 12%
Assets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Entries created
Last 14 days
By team
Share of activity
Marketing site 34%
Help center 27%
Localization 21%
Product launches 18%
FAQ
Frequently asked questions
How do I connect Contentful to Claude?
Open Elaichi, choose Contentful and sign in to Contentful with your own account to authorize it over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Your Contentful spaces are available in Claude from that point.
Does Contentful work with ChatGPT and Cursor as well as Claude?
Yes. Once Contentful is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Contentful once and every client picks it up.
What can an AI agent actually do with my Contentful content?
An agent connected to Contentful through Elaichi can read and write entries, assets, content types, releases and locales across your spaces and environments. In practice that means finding entries still in draft, filling a missing locale field, adding an entry to a release or updating a help article after a policy change. Short, concrete asks such as "list draft entries in the marketing space" work better than long sentences.
Does connecting Contentful give the AI access to every space and environment?
No. Access to Contentful follows the person who signed in, so an agent can only reach the spaces, environments and locales that person can already open in Contentful. Elaichi can narrow that further for a team or a toolbox, but it can never widen it beyond what Contentful itself allows.
Can I stop an agent from deleting or changing things in Contentful?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Contentful entries while blocking publishing, unpublishing or deleting. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Contentful connection when someone leaves?
Offboarding that person in Elaichi ends their access to Contentful through every client at once. If they had shared a Contentful connection with a team, it keeps working for everyone else. Disconnecting Contentful once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Contentful MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Contentful 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, 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 Contentful?
Yes. Both let Claude, ChatGPT or Cursor use Contentful. 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 Contentful call.
How is Elaichi different from Composio for Contentful?
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 Contentful: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Contentful in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.