{"title":"Contentful vs WordPress","slug":"contentful-vs-wordpress","tools":[{"name":"Contentful","slug":"contentful","category":"cms","type":"cloud","website":"https://www.contentful.com","pricing":"freemium","pricing_tiers":["Free (5 users, 2 spaces)","$300/mo Medium","Custom Enterprise"],"open_source":false,"self_hosted":false,"sdk_languages":["python","javascript","typescript","ruby","java","csharp","php"],"frameworks":["langchain","nextjs","gatsby"],"agent_features":{"rest_api":true,"graphql_api":true,"real_time":false,"content_versioning":true,"webhooks":true},"compliance":["soc2","gdpr","iso27001"],"best_for":"Enterprise headless CMS with strong API-first design — well-suited for AI-powered content pipelines","limitations":"Expensive at scale; content model changes require migrations; rate limits on free tier are tight for AI workloads","verified_by":"editorial","last_verified":"2026-04-28","source_urls":{"docs":"https://www.contentful.com/developers/docs","pricing":"https://www.contentful.com/pricing"}},{"name":"WordPress","slug":"wordpress","category":"cms","type":"hybrid","website":"https://wordpress.org","pricing":"open-source","pricing_tiers":["Free (self-hosted)","WordPress.com from $4/mo","WordPress VIP custom pricing"],"open_source":true,"self_hosted":true,"sdk_languages":["python","javascript","php","ruby"],"frameworks":["langchain"],"agent_features":{"rest_api":true,"graphql_api":true,"real_time":false,"content_versioning":true,"webhooks":true},"compliance":["gdpr"],"best_for":"The largest CMS ecosystem — massive plugin library, REST API for headless use, and the widest hosting options","limitations":"PHP-based architecture; REST API is verbose and less modern than headless-native alternatives; security requires ongoing maintenance; performance depends heavily on hosting and plugins","verified_by":"editorial","last_verified":"2026-04-28","source_urls":{"docs":"https://developer.wordpress.org/rest-api","pricing":"https://wordpress.com/pricing"}}],"category":"headless-cms","last_verified":"2026-05-09","body":"WordPress was built for publishing; its REST API came later. Contentful was designed as headless from the start. That difference shows on every agentic dimension: MCP support, webhooks, API design, and token security. WordPress self-hosting is real but not relevant for new agent projects.\n\n## Where Contentful wins\n\n* **Four dedicated APIs.** Contentful separates Delivery API (read, CDN), Management API (write), Preview API (drafts), and Images API (transforms). GraphQL schema auto-generates with no deploy—agent queries stay valid after content updates. WordPress has one REST API at `/wp-json/wp/v2/` for reads and writes. GraphQL needs a third-party plugin.\n\n* **MCP server and maintained SDKs.** Contentful's MCP server at `mcp.contentful.com/mcp` (Beta, OAuth) plus local open-source option. Agents use it as a tool without custom code. Maintained SDKs for JavaScript, Python, PHP, Ruby, Java, .NET, Android, iOS. WordPress has no documented MCP server; SDKs are community-maintained.\n\n* **Outgoing webhooks with retry.** Contentful fires webhooks on content events with documented retry and payload transforms. WordPress core has no outgoing webhooks—its hook system is server-side PHP only. Agents that react to content changes require custom layers outside the platform.\n\n* **Token scoped by API type.** Contentful tokens separate read (CDA), write (CMA), and preview (CPA) at the API boundary, enforcing least privilege. WordPress Application Passwords grant full user permissions with no way to restrict to post types or operations.\n\n## Where WordPress wins\n\n* **Self-hosted, GPL-licensed, no vendor lock-in.** WordPress runs on any PHP 8.3+ and MySQL/MariaDB host: shared, VPS, or on-premises. No API limits, seat fees, or mandatory SaaS backend. Contentful is cloud-only. For agent deployments needing data residency or ownership, WordPress self-hosting removes this blocker. WordPress software is free; only infrastructure costs.\n\n## The agentic difference\n\nWordPress has no documented agentic integration. No MCP server, no outgoing webhooks in core, no content-scoped tokens. Application Passwords grant full user permissions with no way to scope to post types or operations. Agents accept broad permissions or build custom layers.\n\nContentful's MCP server lets agents call content as tool calls. Separate delivery and management tokens enforce least privilege at the API boundary without custom code. This makes Contentful a simpler, lower-risk target for agents than WordPress.\n\n## When to pick which\n\n* **Pick Contentful** when the project is new and agents or API clients are the primary content interface. MCP server, separate APIs, and maintained SDKs cut integration work to near zero for agentic patterns.\n\n* **Pick WordPress** when you already run WordPress and just need to expose content to agents—existing content, authors, plugins, and workflows stay unchanged.\n\n* **Skip WordPress** for new headless CMS projects for agents. Building webhooks, MCP servers, and content-scoped tokens from scratch belongs in the platform, not your application."}