Contentful
Contentful is a headless CMS allowing developers to create, manage, and distribute content across multiple channels and devices with an API-first approach
Verdict
Common use cases
- Audit space access before onboarding new editors
- Rename staging spaces during sprint planning
- Verify space metadata in deployment runbooks
- List all spaces for a client handoff report
Integration
- Vendor
- Contentful
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 3
- Composio slug
contentful
Tools
- Get space
Retrieves details of a specific space by its id. this action is used to get information about a single space in contentful.
- List spaces
Lists all spaces that the authenticated user has access to in contentful. this is a fundamental operation needed before performing any other content management actions since most operations require a space id.
- Update space
Updates the name of a specific space. notes: - the version number is required to ensure you're updating the latest version of the space. - you can get the current version from the sys.version field when fetching space details. - only the na
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Contentful and click Connect. 3. You'll be redirected to Contentful's OAuth consent screen — sign in with your Contentful account. 4. Grant the requested scopes: content_management.read and content_management.write (needed to list, view, and update spaces). 5. After authorizing, Switchy redirects you back and confirms the connection. 6. Open any Space in Switchy and type '@Contentful list spaces' to test — you should see a list of all spaces your account can access. 7. To invoke other tools, use '@Contentful get space [space_id]' or '@Contentful update space [space_id] [new_name] [version]'. 8. If the connection fails, check that your Contentful account has at least developer-level permissions on the organization.
What teammates see: by default, memories from Contentful are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Spaces
@Contentful list all spaces I have access to and show their names and IDs in a table.Open in a Space →
Get Space Details
@Contentful get the details for space ID 'abc123xyz' and summarize its configuration.Open in a Space →
Rename a Space
@Contentful update space 'abc123xyz' to the name 'Q1 2025 Staging' using version 3.Open in a Space →
Audit Space Access
@Contentful list all spaces and indicate which ones I have write access to.Open in a Space →
Prepare Handoff Report
@Contentful list all spaces and format the output as a markdown table with columns for name, ID, and creation date.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@contentful list all spaces I have access to and show me their current environment counts
Found 4 Contentful spaces under your account: 'Marketing Site' (3 environments: master, staging, dev), 'Product Docs' (2 environments: master, preview), 'Blog CMS' (1 environment: master), and 'Internal Wiki' (2 environments: production, test). Each space ID and creation date is included. You can drill into any space by referencing its ID in a follow-up prompt.
This example shows the MCP's read capability for discovering your Contentful organization structure. Requires OAuth2 scope allowing space read access. Useful as a first step before content operations, since most Contentful actions require knowing which space you're working in.
@contentful rename the space 'old-marketing-site' to 'Legacy Marketing Archive' and confirm the change
Successfully renamed space ID 'abc123xyz' from 'old-marketing-site' to 'Legacy Marketing Archive'. The update was applied to version 7 of the space metadata. Note that this change affects only the space name visible in the Contentful UI and API responses—it does not modify any content entries, assets, or environment configurations within the space.
Demonstrates the MCP's write capability for space management. Requires the current version number of the space (fetched via 'get space' first) to prevent concurrent update conflicts. This is an administrative action—most day-to-day content work happens at the entry level, not space metadata level.
@contentful get details on space 'product-catalog' and summarize what content models are likely defined there based on the space name and metadata
Retrieved space 'product-catalog' (ID: def456uvw, created March 2023). The space metadata shows 2 environments and 47 locales configured. Based on the name, this space likely contains content types for products, SKUs, categories, and possibly inventory or pricing data. The AI suggests checking for content models like 'Product', 'Category', 'Brand', or 'Variant'—but note the MCP's 'get space' tool returns only space-level metadata, not the actual content type schemas.
Shows how the AI can reason over space metadata to infer structure, but highlights a key limitation: the provided tools retrieve space info, not content models or entries. For deeper content inspection (content types, entries, assets), you'd need additional Contentful API tools or manual queries. This example is useful for auditing space configuration before diving into content.
Use-case deep-dives
When Contentful MCP beats manual CMS checks for content teams
A 5-person marketing team runs quarterly audits of their product site—checking which spaces hold live content, which are staging, and which can be archived. The Contentful MCP is the right call here because it surfaces space metadata (name, version, creation date) in one query instead of clicking through the web UI. The OAuth2 flow means the team lead authenticates once and shares the workspace; junior writers don't need admin credentials to run read-only audits. The trade-off: this MCP only exposes 3 tools, so you can't query entries or assets inside a space—it's strictly for space-level housekeeping. If your audit needs to count published entries or check asset usage, you'll hit the limit fast. For teams managing 10-30 spaces and running monthly cleanup, this MCP cuts a 2-hour manual task to 10 minutes.
Why this MCP works for agencies spinning up new Contentful tenants
A digital agency onboards 3-4 new clients per quarter, each getting a fresh Contentful organization with staging and production spaces. The Contentful MCP fits this workflow because the 'list spaces' and 'update space' tools let the ops lead verify space creation and rename defaults ('My Space' becomes 'Acme Staging') without leaving Slack or the AI workspace. OAuth2 means the agency account authenticates once; the whole team can run setup checks in shared threads. The boundary: this MCP can't create spaces or manage content models, so the actual provisioning still happens in Contentful's web UI or via their full REST API. If your onboarding checklist is just 'confirm spaces exist and are named correctly', this MCP saves 15 minutes per client. If you're scripting full tenant setup, you need Contentful's CLI or a custom integration.
When to use this MCP for customer support space identification
A 3-person support team at a SaaS company fields tickets like 'I can't find my staging space' or 'Which space ID is production?' The Contentful MCP is a good fit because support reps can query 'list all spaces for this customer's account' in the AI workspace and paste the space ID into the ticket response—no need to log into the customer's Contentful org or ask engineering. OAuth2 scoping means the support lead authenticates with a read-only service account; junior reps can't accidentally rename or delete spaces. The catch: if the customer has 50+ spaces, the list output gets noisy and you're better off teaching them Contentful's own search. For teams handling 10-20 space-lookup tickets per month across customers with under 20 spaces each, this MCP turns a 5-minute Contentful login into a 30-second query.
Frequently asked
What does the Contentful MCP do in Switchy?
It lets your AI agents read and modify Contentful spaces without leaving the conversation. Agents can list all spaces your account has access to, retrieve details about a specific space by ID, and update space names. This is useful for auditing content infrastructure or renaming spaces as part of a workflow, but it doesn't touch entries, assets, or content models yet.
Do I need admin access to connect Contentful via OAuth?
You need a Contentful account with at least read access to the spaces you want the MCP to query. Write access is required if you plan to let agents update space names. Contentful's OAuth flow will show you exactly which permissions the integration requests before you approve it. Check your organization's role assignments if the connection fails.
Can the Contentful MCP create or edit content entries?
No. The current toolset only manages spaces themselves — listing them, reading metadata, and renaming. It doesn't touch entries, assets, content types, or locales. If you need to automate content creation or updates, use Contentful's Content Management API directly or wait for Switchy to expand the tool list.
Why use this instead of Contentful's web app or API?
Use the MCP when you want an AI agent to answer questions like "which spaces do we have?" or "what's the ID of the marketing space?" without context-switching. It's faster than logging into the web app for read-only queries. For bulk operations or complex workflows, the API is still more flexible and doesn't count against Switchy's message limits.
Who on the team should connect the Contentful integration?
Whoever owns your Contentful organization account or has OAuth approval rights. Once connected, any Switchy workspace member can invoke the tools in their conversations, but the MCP acts with the permissions of the connecting user's Contentful account. If that person leaves, reconnect it under a service account or another admin.