How to Connect Contentful to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Contentful, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Contentful + Meta Muse

Let your AI work with your Contentful content: search entries and assets, read content types, locales and tags, and create, change, publish or unpublish entries. Delivery token for reads, management token for writes.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CONTENTFUL_SPACE_ID, CONTENTFUL_ENVIRONMENT, CONTENTFUL_DELIVERY_URL, CONTENTFUL_DELIVERY_TOKEN

Step 1 — Get credentials

1. In Contentful (https://app.contentful.com), open your space, then Settings → API keys → Add API key. Name it (for example "AnythingMCP"), tick the environments it may read (at least master) and save.
2. Copy the Space ID into CONTENTFUL_SPACE_ID and the Content Delivery API access token into CONTENTFUL_DELIVERY_TOKEN.
3. Set CONTENTFUL_ENVIRONMENT to the environment id, usually master. Other environments are listed under Settings → Environments.
4. Set CONTENTFUL_DELIVERY_URL to https://cdn.contentful.com, or https://cdn.eu.contentful.com for a space in the EU data region, without a trailing slash. To let the AI read drafts as well, use https://preview.contentful.com (or https://preview.eu.contentful.com) together with the Content Preview API access token of the same key.
5. For writes, create a personal access token: avatar menu → Account settings → CMA tokens → Create personal access token. Pick an expiry and copy the token right away, as Contentful shows it only once. Paste it into CONTENTFUL_MANAGEMENT_TOKEN, without the word Bearer, and set CONTENTFUL_MANAGEMENT_URL to https://api.contentful.com (or https://api.eu.contentful.com). The token acts as you, in every space you can edit.
6. If your organization has to approve personal access tokens, an organization admin opens Organization settings, finds the token in the access settings for personal access tokens and grants it access. Until then the write tools answer 401 OrganizationAccessGrantRequired; reads with the delivery token are not affected.
7. Install the connector and start with contentful_get_space: it returns the space name and its locales, a quick check that the space ID and the delivery token belong together.

Two tokens, on purpose: the delivery token reads published content and nothing else (drafts too, with the preview token), so a connector set up with only the four required values can look everything up but changes nothing. Writes, unpublished drafts, spaces and environments go through the Content Management API with the personal access token. Leave CONTENTFUL_MANAGEMENT_URL and CONTENTFUL_MANAGEMENT_TOKEN empty and the management tools simply report that they are missing.

Publishing changes your live site: contentful_publish_entry and contentful_unpublish_entry change what visitors see on your website or app, so the AI names the entry and the effect and waits for your yes. contentful_delete_entry is switched off at install, as a deleted entry cannot be restored.

How edits work: contentful_list_content_types gives the content type and field ids, contentful_list_locales the locale codes. Field values are keyed by field id and then by locale, for example {"title": {"en-US": "Hello"}}. Before each change the AI reads the entry with contentful_get_entry_for_editing to get its current sys.version; if someone else saved in between, Contentful answers 409 VersionMismatch and the AI reads again. contentful_update_entry replaces all fields, so anything left out is deleted; for one or two fields the AI uses contentful_patch_entry. A change goes live only when the new version is published.

Searching: contentful_list_entries takes a content_type, a full-text query and further filters such as fields.slug=hello or fields.date[gte]=2026-01-01. Filtering or sorting by a field needs content_type. Linked entries and assets come back in includes, and asset URLs start with //, so the AI adds https:.

Paging: lists return total, skip and limit (up to 1,000); the next page starts at skip + limit.

Common errors: 401 AccessTokenInvalid means a wrong or expired token, or a delivery token used on the preview host (or the other way round). 404 NotFound is a wrong id, or a space or environment the token does not cover: Contentful answers 404 here, not 403. 400 "A Content Type ID is required" means a field filter without content_type. 422 ValidationFailed names the field that is empty or breaks a validation. 429 RateLimitExceeded: the management API allows about 7 requests a second, so wait and retry.

The connector does not upload assets, create or edit content types, or manage environments, webhooks, roles and apps, and it does not use the GraphQL API.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the Contentful tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "Find the blog posts we published in the last 30 days and list each one's title, slug and author."
• "Which entries have saved changes that are not published yet?"
• "List the images we uploaded this month, with their file size and dimensions."
• "Change the headline of the spring sale landing page to 'Spring sale: 20% off everything' and publish it once I confirm."

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT