Contentful MCP connector for AI agents

Contentful MCP tools for AI agents

CALL ANY TOOL

12 tools covering archive, create.

contentfulmcp_archive_asset

Archive asset

Archive one or more assets that are no longer needed but should be preserved.

Parameters

Name

Type

Required

Description

assetId

string

Required

The unique identifier of the asset.

environmentId

string

Required

The Contentful environment ID (e.g. 'master', 'staging'). Find it in Settings > Environments.

spaceId

string

Required

The unique identifier of the Contentful space. Find it in your Contentful dashboard under Settings > General.

contentfulmcp_create_ai_action

Create ai action

contentfulmcp_create_concept_scheme

Create concept scheme

contentfulmcp_create_entry

Create entry

contentfulmcp_create_locale

Create locale

contentfulmcp_delete_ai_action

Delete ai action

contentfulmcp_delete_concept

Delete concept

contentfulmcp_delete_content_type

Delete content type

contentfulmcp_delete_environment

Delete environment

contentfulmcp_get_ai_action

Get ai action

contentfulmcp_get_asset

Get asset

contentfulmcp_get_concept_scheme

Get concept scheme

contentfulmcp_get_entry

Get entry

contentfulmcp_get_locale

Get locale

contentfulmcp_invoke_ai_action

Invoke ai action

contentfulmcp_list_ai_actions

List ai actions

contentfulmcp_list_concept_schemes

List concept schemes

contentfulmcp_list_content_types

List content types

contentfulmcp_list_environments

List environments

contentfulmcp_list_orgs

List orgs

contentfulmcp_publish_ai_action

Publish ai action

contentfulmcp_publish_content_type

Publish content type

contentfulmcp_search_entries

Search entries

contentfulmcp_unarchive_entry

Unarchive entry

contentfulmcp_unpublish_asset

Unpublish asset

contentfulmcp_update_ai_action

Update ai action

contentfulmcp_update_concept

Update concept

contentfulmcp_update_content_type

Update content type

contentfulmcp_update_entry

Update entry

contentfulmcp_upload_asset

Upload asset

For more tools, view docs.

Build your Agent

Same auth pattern across every framework.

token = client.agent.get_token(user_id="user_id", connector="contentfulmcp")
mcp = MultiServerMCPClient({"contentfulmcp": {"url": "https://mcp.scalekit.com/contentfulmcp", "headers": {"Authorization": "Bearer " + token}}})

const token = await client.agent.getToken({ userId: "user_id", connector: "contentfulmcp" });
// Connect to MCP at https://mcp.scalekit.com/contentfulmcp

const token = await client.agent.getToken({ userId: "user_id", connector: "contentfulmcp" });
// Connect to MCP at https://mcp.scalekit.com/contentfulmcp

token = client.agent.get_token(user_id="user_id", connector="contentfulmcp")
# Connect to MCP at https://mcp.scalekit.com/contentfulmcp

Try these prompts

Paste any prompt into your agent to get started.

Upload a new asset to Contentful from a URL or file handle?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Contentful MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Contentful MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Contentful MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Contentful MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

Deal room sync

Pulls opportunity context from Salesforce, captures key decisions from Slack, and syncs a running summary to the deal room doc in Google Drive, but only when the deal actually changed.

People Ops and HR teams

Performance review collector

Collects review feedback from Airtable and Google Forms scoped to each manager's direct reports, writes per-employee summaries to Notion, and DMs the manager a Slack digest.

People Ops and HR teams

Offer letter routing agent

Drafts the offer in PandaDoc, blocks on the hiring manager's approval in Slack, then emails the candidate their e-signature link. Every call runs as the recruiter who triggered it, never a shared HR bot.

Support and Ops Teams

Support ticket automation agent

Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. Scalekit resolves the real user credential.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Contentful as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Contentful OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Contentful?
Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Contentful.

What happens when a user revokes Contentful access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent publish content or only draft it?
Whatever the authorizing user's Contentful role allows. Entry, asset, and content type tools follow space roles, and you can filter out publish and archive tools to keep agents in draft-only mode.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit