# Contentful (EU) MCP connector

The Contentful (EU) connector brings entries, assets, content types, releases and locales from Contentful's EU region into Claude, ChatGPT, Cursor and the Elaichi Agent, where each person works inside their own Contentful access.

Source: https://elaichi.ai/connectors/contentful-eu/

## Facts

| | |
| --- | --- |
| Application | Contentful (EU) |
| Category | Application Development |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Contentful (EU) builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.contentful.com/help/getting-started/how-to-get-help |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, 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 Contentful (EU) is connected

- Which blog entries changed this week and who edited them?
- List entries in the spring campaign release that are still drafts.
- Find product pages missing a French locale.

## Connect Contentful (EU) in Elaichi

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

1. Open Connections, choose Add connection, and pick Contentful (EU).
2. Optionally set Share with, then press Connect.
3. Approve it in Contentful (EU). Contentful (EU)'s own window opens. Whoever approves it decides what this connection can reach.

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

## Contentful (EU) 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.

## Contentful (EU) 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 today. The plugin directory lives at chatgpt.com/plugins.

## Contentful (EU) 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.

## Connect Contentful (EU) 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

Only Read is granted by default, which is not enough to call a Contentful (EU) tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Contentful (EU) through Elaichi

### Draft a landing page entry from a brief

Marketing. Paste the campaign brief and have the agent create the draft entry in the right space, with the fields filled in and the hero asset attached, ready for review before anything is published.

### Catch an entry up after a review

Editorial. After a stakeholder review, ask the agent to apply the agreed edits to the article entry and tell you what is still unpublished in that environment.

### Find every entry missing a locale

Localization. Ask which product pages have an English version but no German or French one, then get the list of entries to hand to translators.

### Check what is in the next release

Product. Ask which entries and assets are bundled in the upcoming release and whether any of them are still in draft, without opening each one.

### Audit content types before a schema change

Engineering. List the content types in a space, see which fields are required and which entries would be affected, then make the change in a staging environment first.

### Tidy the asset library

Design. Find assets that no entry references, spot images without titles or descriptions, and update them in bulk from a single conversation.

## Elaichi vs Zapier MCP vs Composio for Contentful (EU)

All three can connect Contentful (EU) 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 Contentful (EU) tools | Allow or restrict single Contentful (EU) 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 (EU) 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](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 Contentful (EU) to Claude?

In Elaichi, choose Contentful (EU) from the catalog and sign in to Contentful in EU with your usual Contentful account over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on your Contentful (EU) spaces are available in the conversation.

### Does Contentful (EU) work with ChatGPT and Cursor as well as Claude?

Yes. Contentful (EU) is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor or any other MCP client. The Elaichi Agent uses it too, so there is nothing separate to set up per client for Contentful in EU.

### What can an AI agent actually do with my Contentful (EU) content?

It can read and write entries, assets, content types, releases and locales across the spaces and environments in your Contentful (EU) account, so you can ask it to draft an entry, find every page missing a German translation, or list what is scheduled in a release. Exactly what is available depends on what your account has set up in Contentful in EU. Short, specific asks such as listing the blog entries changed this week work better than long paragraphs.

### Does connecting Contentful (EU) give the AI every space and environment?

No. The AI works inside the Contentful (EU) access of the person who signed in, so it sees the spaces, environments and roles that person already has in Contentful in EU and nothing more. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Contentful grants.

### Can my team share one Contentful (EU) connection?

Yes. One person connects Contentful (EU) in Elaichi and shares it with a team, and nobody else ever handles a token or password for Contentful in EU. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who drafted or published each entry.

### Can I stop an agent from deleting or changing things in Contentful (EU)?

Yes. Restrictions in Elaichi apply per action, so you can allow reading entries and assets in Contentful (EU) while blocking publishing, deleting or changing content types. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it in your Contentful in EU spaces, no matter how it is worded.

### What happens to a Contentful (EU) connection when someone leaves?

Offboarding the person in Elaichi ends their access to Contentful (EU) through every client at once. A connection they shared with the team keeps working for everyone else. If you want to remove Contentful in EU entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Contentful (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Contentful (EU) 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 (EU)?

Yes. Both let Claude, ChatGPT or Cursor use Contentful (EU). 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 (EU) call.

### How is Elaichi different from Composio for Contentful (EU)?

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 (EU): one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.