Integration · Automate and collaborate

Contentful and Meteor AI agents

Connect Contentful to a WhatsApp Met: search entries, read articles and files, and update or publish content through the official MCP server.

Book a demo See every integration

How does Contentful connect to Meteor?

With the Contentful ready connector, your WhatsApp Met uses Contentful's official MCP server with the account the admin authorizes. It searches entries by text or by meaning, opens an entry with its references and gets images or documents, so it answers with the help articles or product pages your team already published, not from memory. If the admin leaves writing on, it also creates and updates entries and publishes them: publishing moves the change into the published content your site reads. Archiving and deleting entries start switched off. On top of that, a Contentful admin decides in the Contentful MCP app which tool categories each environment allows.

What it automates

What a Meteor Met does with Contentful

Answer with your help articles

When a customer asks how to do something, the Met searches Contentful for the matching help article, by text or by meaning, opens it and answers with what your team wrote.

Send the right image or document

If the product page or the article has an image or a PDF attached, the Met gets that file and shares it in the conversation.

Update and publish an entry

If the admin leaves writing on, the Met updates an entry, such as a branch's opening hours, and publishes it. Publishing moves the change into the published content your site reads.

Check what changed in an entry

The Met gets an entry's version history to tell you when it changed and how it looked before, without touching the content.

22 tools

Everything your Met can ask Contentful for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_initial_context`	Starts the connection and returns the server's usage instructions.
`list_spaces`	Lists the Contentful spaces available to the account.
`get_space`	Gets the details of a Contentful space.
`list_environments`	Lists the environments in a Contentful space.
`list_locales`	Lists all the locales set up in the environment.
`list_content_types`	Lists all the content types in the environment.
`get_content_type`	Gets the detailed information of a content type.
`search_entries`	Searches and filters content entries.
`semantic_search`	Finds entries by meaning, with vector search.
`get_entry`	Gets a specific content entry.
`get_entry_snapshot`	Gets an entry's version history (snapshots).
`resolve_entry_references`	Resolves the references of a content entry.
`create_entry`	Creates new content entries.
`update_entry`	Modifies existing content entries.
`publish_entry`	Publishes entries, one or several at once.
`unpublish_entry`	Unpublishes entries, one or several at once.
`archive_entry`	Archives a content entry. Starts turned off.
`delete_entry`	Deletes content entries. Starts turned off.
`list_assets`	Lists and browses the files (assets) in the environment.
`get_asset`	Gets a specific file (asset) from the environment.
`publish_asset`	Publishes files (assets), one or several at once.
`list_tags`	Lists all the tags in the environment.

The limits

What the Contentful integration does NOT do

We would rather say it here than have you find out during rollout.

It does not work without the Contentful MCP app. It has to be installed in each space and environment, and there a Contentful admin chooses which tool categories are allowed, read only or read and write.
It does not upload new files. Uploading through the remote server needs the bytes sent in a separate request, so that tool is not on this page.
It does not archive or delete entries by default: those two actions start switched off until the admin turns them on in Connections.
It does not ask you for confirmation in the chat before writing or publishing. The admin decides in Connections which actions stay on, and publishing arrives switched on.
It does not work with environment aliases: Contentful asks for the real environment ID. And Met uses the global server, while Contentful serves EU region organizations on a different one.
It does not pay your Contentful plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Contentful

1

A Contentful account with access to the space

Your team's Contentful account. The Met works with that account's permissions in the spaces and environments you pick when connecting.
2

The Contentful MCP app in the space

A Contentful admin installs the MCP app from the Marketplace in each space and environment, and in its settings chooses the allowed tool categories and whether they are read only or read and write.
3

Connect it in Met

In Met, open Connections → Contentful → Connect. A Contentful window opens so you sign in, pick the spaces and environments and authorize Met.

Frequently asked questions

Questions about Contentful and Meteor

Yes, in two ways: in the Contentful MCP app you mark the categories as read only, and in Connections you turn off the write and publish actions.

Publishing puts the entry in Contentful's published content, which is what your site reads. If you do not want the Met to publish, turn that action off and let your team publish from Contentful.

Because the Contentful MCP app has not authorized that category in that space or environment. A Contentful admin enables it in the app settings and then you connect again.

You do, with your Contentful account and plan. Meteor does not resell Contentful or charge for the actions your Met takes there.

Step by step