Contentful Automation

When to use this skill

Use Contentful Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.

When not to use it

Skip Contentful Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

1. Personal install: create ~/.claude/skills/contentful-automation/SKILL.md (and any bundled scripts) so Claude Code, Claude Desktop, and compatible agents can load it in every project.
2. Project install: commit the same folder at .claude/skills/contentful-automation/ so teammates get the skill with the repo.
3. Restart the agent session after copying files so it re-scans the skills directory, then ask for the task in words that match the skill description.

Full install guide for Claude, Cursor, and Codex

What this skill does

# Contentful Automation

Manage your **Contentful** headless CMS spaces directly from Claude Code. List spaces, retrieve metadata, and update space configurations without leaving your terminal.

**Toolkit docs:** [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful)

---

## Setup

1. Add the Composio MCP server to your configuration: ``` https://rube.app/mcp ``` 2. Connect your Contentful account when prompted. The agent will provide an authentication link. Ensure your access token has space management scopes.

---

## Core Workflows

### 1. List All Spaces

Discover all Contentful spaces accessible to your authenticated account. This is typically the first operation since most other actions require a `space_id`.

**Tool:** `CONTENTFUL_LIST_SPACES`

Key parameters: - `limit` (1-1000) -- maximum number of spaces to return (default: 100) - `skip` -- number of spaces to skip for pagination - `order` -- sort by field, e.g., `sys.createdAt` or `-sys.createdAt` for descending

Example prompt: *"List all my Contentful spaces"*

---

### 2. Get Space Details

Retrieve detailed metadata for a specific space including its current `sys.version`, which is required for updates.

**Tool:** `CONTENTFUL_GET_SPACE`

Key parameters: - `space_id` (required) -- the ID of the space to retrieve (alphanumeric, 1-64 chars)

Example prompt: *"Get details for Contentful space abc123def"*

---

### 3. Update Space Name

Update the name of a specific space. Requires the current version number for optimistic locking to prevent concurrent modification conflicts.

**Tool:** `CONTENTFUL_UPDATE_SPACE`

Key parameters: - `space_id` (required) -- ID of the space to update - `name` (required) -- new name for the space (1-255 chars) - `version` (required) -- current space version from `sys.version` (must be > 0)

Example prompt: *"Rename Contentful space abc123def to 'Production Content Hub'"*

---

### 4. Audit Space Inventory

Combine space listing and detail retrieval to audit your organization's Contentful spaces.

**Tools:** `CONTENTFUL_LIST_SPACES` then `CONTENTFUL_GET_SPACE`

Workflow: 1. List all spaces to get IDs and names 2. Fetch details for each space to get version info, creation dates, and metadata

Example prompt: *"Audit all Contentful spaces -- list them with their creation dates and current versions"*

---

## Known Pitfalls

- **Version conflicts on update:** `CONTENTFUL_UPDATE_SPACE` requires the latest `sys.version` from `CONTENTFUL_GET_SPACE`. If someone else modified the space between your read and write, the update will fail with a version conflict. Always fetch the space immediately before updating. - **Pagination for many spaces:** `CONTENTFUL_LIST_SPACES` uses `limit` and `skip` parameters. When you have many spaces, iterate by incrementing `skip` until no more results are returned to avoid missing spaces. - **Scope limitations:** These tools only manage space-level metadata (names). They cannot create or modify entries, content types, or assets within a space. - **Auth/permissions mismatch:** Updates via `CONTENTFUL_UPDATE_SPACE` will fail if your token lacks space management scopes, even if reads via `CONTENTFUL_GET_SPACE` succeed. Verify your token has write permissions. - **Space ID format:** The `space_id` must match the pattern `^[a-zA-Z0-9-_.]{1,64}$`. Invalid characters will be rejected.

---

## Quick Reference

| Tool Slug | Description | |---|---| | `CONTENTFUL_LIST_SPACES` | List all spaces accessible to your account | | `CONTENTFUL_GET_SPACE` | Retrieve detailed metadata for a single space | | `CONTENTFUL_UPDATE_SPACE` | Update the name of a space (requires version) |

---

*Powered by [Composio](https://composio.dev)*

Intended uses

• Use Contentful Automation when this documented workflow matches the task.