Updates merge rather than replace — send the fields and locales you are changing and everything else stays put — and publishing takes up to 100 entry IDs at once, which turns a content migration into a handful of calls. Pagination is the thing to plan around: entry search returns at most 3 items and content type listing at most 10 per request, so anything wide is a skip loop. AI Actions defined in the space are invokable from the same session as the edits they feed.
40 tools over the Contentful Management API: entries, assets, content types, spaces and environments, plus the space's AI Actions and threaded comments on entries.
- Entries searched, created, read, updated and deleted, and published or unpublished up to 100 IDs at a time through the bulk path
- Field-level merging on update, so only the fields and locales you send change, and bulk validation across a set of entry IDs before anything goes live
- Assets uploaded, updated, deleted, published and unpublished
- Content types created, updated, published, listed and deleted, with the field definitions readable first
- Spaces and environments listed, created and deleted
- AI Actions listed, created, updated, published and invoked with variables, and the result of an earlier invocation fetched by ID
- Threaded comments on an entry: created with a parent, read with status, updated and deleted
A Contentful account and a Content Management API token in CONTENTFUL_MANAGEMENT_ACCESS_TOKEN. Space and environment IDs are supplied per call.
One command plus a key — npx -y @ivotoby/contentful-management-mcp-server --management-token YOUR_TOKEN, then supply credentials