Connect your AI Agents to Contentful in minutes

What is a Contentful MCP server?

It’s an MCP server that exposes functionality and tools from Contentful via tools. Your agents can use these tools to create new assets, unpublish assets, share links to assets in Slack, and more.

How can I use the Contentful MCP server?

Here are some use cases:

• Connect an agent to Contentful content without building custom API glue. Let your agent browse Contentful spaces and entries, then pull the exact content it needs for a response or workflow
  

• Draft and update content from natural language. Create or update entries (for example, landing page copy, FAQs, changelog posts) based on a prompt, then write them into Contentful as a new draft
  

• Create content ops workflows. Triage a list of requested edits, apply changes across many entries, and keep fields consistent (titles, slugs, metadata, references)
  

• Implement content quality and governance measures. Find missing fields, inconsistent metadata, or outdated content, then propose fixes (or apply them) across your content model

• Add localization support: Duplicate an entry into multiple locales, populate translated fields, and flag what is still missing before publishing
  

• Coordinate releases and publishing. Prep a batch of entries for a release, move items through draft to ready for review, and (if your server supports it) publish at the right time

What makes Merge Agent Handler’s Contentful MCP server better than alternative Contentful MCP servers?

Merge Agent Handler provides platform-level capabilities that extend beyond what you can do with Contentful’s official MCP server. This includes:

• Enterprise-grade security and DLP: All tool inputs and outputs pass through a security gateway that can block, redact, or mask sensitive data using default or custom rules. This helps prevent data leakage during agent-initiated Contentful actions
  

• Real-time observability and audit trails: Every tool call is logged with full request and response metadata. Logs are fully searchable, making it easier to audit agent behavior, debug failures, and optimize workflows over time
  

• Managed authentication and credential handling: Merge Agent Handler handles connector authentication flows, including user onboarding and credential storage, so agents can invoke tools without embedding secrets or custom auth logic
  

• Evaluation Suite: Pressure-test your Contentful tool calls before production with an evaluation suite to validate that the connector behaves consistently across prompts and scenarios

Can I set custom security rules for Contentful tool calls in Merge Agent Handler?

Yes. Merge Agent Handler allows you to configure custom security and data-loss-prevention (DLP) rules that inspect Contentful tool inputs and outputs. Rules can block, redact, or mask sensitive fields based on your organization’s policies.

Here some specific examples:

• Prevent publishing secrets into Contentful. Block any <code class="blog_inline-code">create_entry</code> or <code class="blog_inline-code">update_entry</code> tool call if the payload includes API keys, bearer tokens, passwords, or other credential-like strings
  

• Stop PII from being stored in CMS fields. Block tool calls that attempt to write SSNs, credit card numbers, or other sensitive entities into Contentful fields (for example, bio fields)
  

• Redact sensitive values while still allowing the action. Allow the tool call to execute, but automatically redact flagged entities in the underlying API request behind the tool call
  

• Mask sensitive data on reads before it reaches the agent. When your agent reads entries, mask internal identifiers or other sensitive tokens so the agent can’t copy/paste them into other systems
  

• Use custom regex-based rules for your org’s patterns. Add regex rules for things like proprietary customer IDs, internal environment URLs, or “do-not-publish” markers that appear in drafts

How can I start using Merge Agent Handler’s Contentful MCP server?

You can follow these steps:

1. Create a free Merge Agent Handler account.

2. Create a Tool Pack for the Contentful workflow you want (for example, “Website content updates”).

3. Add the Contentful connector to that Tool Pack.

4. Configure authentication for Contentful (shared org auth vs individual end-user auth, depending on your setup).

5. Create a Registered User (this is the identity container that will hold the credentials used to execute tool calls).

6. Complete the Contentful authentication flow for that Registered User so Contentful tools become available.

7. Copy the MCP entry URL for your Tool Pack + Registered User and add it to your MCP client (Cursor, Claude Desktop, VSCode, Windsurf, etc.).

8. Use the Playground to run a few Contentful tool calls end-to-end and confirm the calls succeed and logs are generated.