Contentful MCP Server

The Contentful MCP Server gives AI assistants tools to work against the Contentful Management API: content types, entries, assets, spaces and environments, locales, tags, content preview, and a set of AI-assisted actions, distributed as @contentful/mcp-server and installed via npx @contentful/mcp-server over stdio. It authenticates with a static personal access token, supplied as CONTENTFUL_MANAGEMENT_ACCESS_TOKEN, and depends on a shared library, @contentful/mcp-tools, published separately from the same monorepo and versioned on its own release cadence. No hosted remote endpoint is documented; an internal "Contentful Remote MCP Server" is named in the repository's AGENTS.md as a separate downstream consumer of the shared tools library, but no public URL for it appears anywhere fetched.

Authority is first-party: the repository lives in the contentful GitHub organization, which GitHub reports as a verified organization, and both workspace packages' package.json files list "Contentful GmbH" as author. Vendor documentation on contentful.com could not be checked this session; the domain returned HTTP 429 on every attempt, so this record does not draw on any contentful.com page.

The repository carries one published security advisory, GHSA-2xhg-73j7-rrgx (CVE-2026-53957), a high-severity server-side request forgery (CVSS 3.1 7.7) in which the export_space and import_space tools passed caller- controlled host and proxy arguments to the Management API client. The record exists in two forms with different dates. The maintainer's repository advisory was published 2026-06-12, eleven days after the fix shipped in mcp-server 1.7.19 and mcp-tools 0.4.5 on 2026-06-01, and lists the affected ranges as <= 1.7.15 and <= 0.4.1 with no patched version entered. GitHub's reviewed record in the Advisory Database is dated 2026-08-19 and lists the ranges as < 1.7.19 and < 0.4.5 with those patched versions. The published story covers the disclosure.