Claude Contentful MCP connectorWhat Claude can do in your Contentful MCP account.
The Claude Contentful MCP connector exposes 70 tools. 18 read your spaces and content, 26 write, from drafting an entry to deleting an environment, and 26 carry no official description. Below: what Claude can publish, what a space admin controls, and where the documentation stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Contentful MCP connector changes for content teams
A content manager has to update the price mention on forty product pages after a pricing change. Opening each entry in Contentful, editing and publishing would take the afternoon. With the connector she asks Claude: it searches the entries, proposes the new wording, applies it and, once she agrees, publishes the batch. The model, the locales and the media are within reach too.
Find content by meaning, not just by keyword. search_entries filters entries by type or field value, and semantic_search finds them by meaning, so a vague memory of an article is enough. get_entry_snapshot shows how an entry looked before, useful when someone asks what changed.
Draft, edit and publish in one conversation. create_entry turns a brief into a draft, update_entry applies edits, and publish_entry takes one or several entries live. Assets follow the same path with upload_asset and publish_asset.
Shape the model itself. create_content_type and update_content_type add or adjust fields, create_locale opens a new market, and create_environment gives you a sandbox to try it all away from production. AI actions, the reusable prompts your editors run inside Contentful, can be listed, built and published too.
Now the part the sheet does not explain. Twenty-six tools, around concepts, archiving, editor interfaces and individual fields, have no description in any official source we could read, so this page does not guess what they do. A space admin also decides which tools are exposed at all, space by space. And nothing runs on its own: no tool fires when an entry is published. Scheduled or event-driven flows belong to the tools on our Integrations hub.
Five words before you plug it in
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector gives Claude. Claude picks the ones it needs as it answers; the directory lists each by name.
- Authorization
- Contentful's own sign-in and consent screen, where you grant Claude the access it will use. Given once per person, and revocable later.
- Approval
- The confirmation Claude waits for in the conversation before it goes ahead with something that would alter your space.
- MCP
- The shared standard connectors are built on, here even in the connector's name: it is what lets an assistant like Claude talk to Contentful.
Plug Contentful MCP into Claude in three steps
- 01
Find Contentful MCP in Claude
In Claude's settings, open Customize, then Connectors, and look for Contentful MCP. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; each member then signs in on their own.
- 02
Start the connection
Click Connect on its row and sign in to Contentful in the window Contentful opens itself. If the link breaks later, use Disconnect and connect again from the same list.
- 03
Read the authorization screen
Look at Contentful's authorization screen before you accept. It belongs to Contentful, not to Claude, and it is what sets the scope of the access. You can withdraw that access later from the Contentful side as well.
The 70 tools, sorted by what they do
Contentful MCP gives Claude 70 tools: 18 that read your account, 26 that change something in it, and 26 no official source describes.
Three groups: what Claude reads, what it writes, and the tools no source describes. Names stay exactly as Claude displays them.
- 18 read
- 26 write
- 26 not documented
What Claude reads (18)
18 toolsEighteen tools that look at spaces, content, media, locales and AI actions without altering them.
get_ai_action
Opens one AI action of your space so Claude can see its configuration and the instructions it carries, before deciding whether to use it on a batch of content.
get_ai_action_invocation
Fetches the details of a past run of an AI action, so Claude can report what came back from it and whether it completed as expected.
get_asset
Retrieves a single asset from your space, an image, a PDF or a video, with its title, description and file details, so Claude knows exactly which file it is looking at.
get_content_type
Returns the full definition of one content type: its fields, their types and their validation rules, which is the blueprint every entry of that type follows.
get_entry
Brings back one entry with its field values, so Claude can read a page, an article or a product exactly as it is stored in Contentful today.
get_entry_snapshot
Pulls the version history of an entry as snapshots, showing how its content looked at earlier points in time and letting Claude compare two states.
get_initial_context
Sets up the session and hands Claude the usage instructions for the Contentful tools, the kind of briefing it reads before the real work on your space begins.
get_locale
Retrieves the information Contentful holds on one locale of your environment, for example German for Austria, so Claude works with the exact locale code rather than a guess.
get_space
Returns the details of one Contentful space, so Claude confirms it is working in the right place before it goes any further with your request.
list_ai_actions
Lists the AI actions set up in a space, the ready-made prompts your team built inside Contentful to handle recurring editorial jobs.
list_assets
Browses the assets of your space page by page, with their names and basic details, so Claude can find media without you opening the media library.
list_content_types
Shows every content type defined in the environment, the map of what kinds of content your team can publish and how they are organized.
list_environments
Returns the environments of a space, so Claude knows which ones exist before it works in one of them.
list_locales
Lists all the locales configured in your environment, the languages and regions your content can be published in, with their codes.
list_spaces
Shows the Contentful spaces your account can reach, the top-level containers that hold separate sites, brands or products.
list_tags
Returns all the tags available in the environment, the labels your team uses to group content across types and campaigns.
search_entries
Searches and filters entries by content type, field values or other criteria, returning the matching pieces of content in one go.
semantic_search
Finds entries by meaning rather than exact words, using vector search, so a loosely phrased question still surfaces the right content.
What Claude writes (26)
26 toolsTwenty-six tools that create, edit, publish or delete. No source describes a confirmation specific to any of them: the general rule below applies.
create_ai_action
Approval: see the ruleBuilds a new AI action in your space, a reusable prompt-based workflow your editors can run on content later.
create_content_type
Approval: see the ruleAdds a new content type to the environment, with the fields it should hold, so a new kind of content can exist in your model.
create_entry
Approval: see the ruleCreates a new entry of a given content type and fills in its fields, a draft article or product that did not exist before.
create_environment
Approval: see the ruleOpens a new environment in the space, a separate workspace where content and model changes can be tried away from production.
create_locale
Approval: see the ruleSets up a locale in the environment so content can be written for a new language or region.
create_tag
Approval: see the ruleRegisters a new tag in the environment, a label your team can then attach to entries and assets.
delete_ai_action
Approval: see the ruleRemoves an AI action from the space for good, so editors no longer see it in their list.
delete_asset
Approval: see the ruleDeletes an asset from your space, the stored image, document or video it points to.
delete_content_type
Approval: see the ruleDeletes a content type from the environment, removing that kind of content from your model.
delete_entry
Approval: see the ruleDeletes an entry, removing that article, page or product from the environment.
delete_environment
Approval: see the ruleWipes out an entire environment of the space along with everything it holds.
delete_locale
Approval: see the ruleDrops a locale from the environment, taking that language or region out of your setup.
publish_ai_action
Approval: see the rulePublishes an AI action so editors can actually use it across the space.
publish_asset
Approval: see the ruleMakes one or several assets live, so websites and apps reading from Contentful can display them.
publish_content_type
Approval: see the rulePushes the pending changes of a content type live so new or edited fields take effect for editors and for delivery.
publish_entry
Approval: see the ruleSends one or several entries live, so the content they hold becomes visible wherever your space is delivered.
unpublish_ai_action
Approval: see the ruleWithdraws a published AI action, keeping it in the space but hiding it from everyday use.
unpublish_asset
Approval: see the rulePulls one or several assets offline, so channels stop showing them while the files stay in the space.
unpublish_content_type
Approval: see the ruleUnpublishes a content type, a step that takes it out of the active model, often before deleting it.
unpublish_entry
Approval: see the ruleTakes one or several entries offline while keeping them as drafts in the environment.
update_ai_action
Approval: see the ruleEdits an existing AI action, for example its instruction or its settings.
update_asset
Approval: see the ruleChanges an asset's metadata, such as its title or description, without replacing the file itself.
update_content_type
Approval: see the ruleModifies an existing content type, adding or adjusting its fields and their settings.
update_entry
Approval: see the ruleRewrites the field values of an existing entry, the everyday editing of your content.
update_locale
Approval: see the ruleModifies the settings of a locale that already exists in your environment. Contentful's table does not list which settings are concerned.
upload_asset
Approval: see the ruleUploads a new asset into your space, a file that becomes available to attach to entries.
Not documented (26)
26 toolsThe directory publishes these names and nothing else we could cite. No official text says what they do, and we will not guess from a name.
append_entry_field
This name is on the directory sheet only: Contentful's public tool table does not list it and no other official source describes it, so we say nothing about its effect on your content.
archive_asset
Contentful's documentation that we could read does not mention this tool at all. With no official description available, its behaviour is not something this page can state.
archive_entry
No official text we read mentions it; the name alone appears on the sheet. We would rather flag the gap plainly than guess its effect from a single verb.
create_concept
Neither the directory description nor Contentful's tool reference explains this one. It stays undocumented on this page until a source says more about what it does.
create_concept_scheme
Undocumented: the directory publishes the name and Contentful's public reference skips it entirely, so its role is left open here rather than invented.
create_upload_session
No official sentence describes this tool. Contentful's reference covers asset uploads through another name, and never mentions this one in any line we could cite.
delete_concept
A name without a description: no Contentful page and no Claude page we read covers it, so this page does not say what it does or when Claude would call it.
delete_concept_scheme
Only the directory lists it. Contentful's tool table has no entry under this name, and no other source fills the gap, so its effect remains unstated here.
delete_content_type_field
Nothing official documents this tool. Contentful's public table describes whole content types, never a field-level tool with this name, so we leave it unexplained.
disable_content_type_field
Absent from Contentful's reference and from Anthropic's pages, this entry carries no description we could cite, so its role stays unconfirmed on this page for now.
get_concept
The sheet names it; no source describes it. Contentful's documentation that we read does not include the concept tools at all, so there is nothing reliable to report.
get_concept_scheme
Described nowhere in the official material we could read, this tool is left without a role on this page rather than given an invented one based on its name.
get_editor_interface
Contentful's public reference has no line for it and no other source mentions it, so we do not describe it, even though the name may look self-explanatory.
get_org
Its name appears on the directory sheet and nowhere else in the official sources we read. We stop at that fact instead of speculating about what it returns.
invoke_ai_action
Contentful's repository describes it in one line, running an AI action with variables, and adds that the run generates content without writing to the environment, and no source classes it as read or write, so this page leaves it unclassified.
list_concept_schemes
There is no official description of this tool in the sources we collected. The directory shows the name, and that is the full extent of what is published.
list_concepts
No source describes it: Contentful's tool table and every Claude page we checked are silent, so this one keeps an open question mark on this page.
list_editor_interfaces
None of the official texts we read describes it, and a name is not a description. This page therefore adds nothing further about its purpose or its output.
list_orgs
Listed on the sheet without a single sentence of documentation from Contentful or Anthropic, so its purpose is not stated here and should not be assumed.
omit_content_type_field
Contentful's reference does not include this tool, and no other official source explains it. We leave its effect on your content model unstated on purpose.
resolve_entry_references
The directory gives the name; no official page gives a description. Rather than infer one from the wording, this page marks it plainly as undocumented.
unarchive_asset
We found no source that describes this tool, in Contentful's documentation or in Anthropic's, so it remains unexplained here until one does.
unarchive_entry
Its only official trace is the tool list of the directory. No text describes what it does, so we do not either, however clear the name looks.
update_concept
Not part of Contentful's public tool table, and not described anywhere else we looked. The page keeps it in the undocumented group until a source says more.
update_concept_scheme
Not described by any source we could cite. The directory publishes the name, and the documentation we read says nothing about it at all.
update_editor_interface
No official description exists in the material we collected. We leave it without a role instead of reading one into the name of the tool.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request appears in the conversation when it matters.
On a Team or Enterprise workspace, owners decide whether members may let certain actions run without a prompt each time. They can also restrict a connector for the whole organization, for instance keeping reads open and closing every write, and no member overrides that. Contentful adds its own switchboard: space admins choose, environment by environment, which tools the connector exposes, read-only for a team auditing content or write tools for developers. Claude works with your Contentful rights and nothing more.
Which plans include it
Of the 819 sheets in the official directory, none shows availability per plan. That connector-by-connector answer is published nowhere: a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can sign in. On the Contentful side, the Remote MCP app has to be installed in each environment you want Claude to use. For the current state, check the connector's sheet in the official directory.
Where the Claude Contentful MCP connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an entry is published or an asset is uploaded.
Only Contentful documents this connector: no Claude help article covers it, and the tool descriptions we could cite come from Contentful's public repository, whose table does not match the directory list exactly. The tool list is an observed floor, not a promise, since administrators can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic says on each sheet that it neither picks a publisher's tools nor guarantees them. For another connector documented only by its publisher, see the Claude juro connector.
Need help connecting Contentful MCP to Claude?
A person reads every message.
