Head to head · Cms content · October 2026 research run

Storyblok vs WordPress

Storyblok scores 67.7 (B) on agent readiness against WordPress's 64.8 (B), and leads in 5 of 7 scored categories. WordPress leads on payments & pricing. Both do cms content.

Which one, for what

Storyblok B

Good for Teams already on Storyblok who want an agent to draft, translate and publish stories or change component schemas under scoped, per-space permissions.

Ahead on

  • Security & auth, 73 against 62
  • Transparency & trust, 80 against 68

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

The Management API's OpenAPI spec sits in a private repository. Only the Content Delivery API has a public spec (OpenAPI 3.1, 14 operations)

WordPress B

Good for Sites that already run WordPress, where an agent drafts posts and uploads media under a Contributor or Author account and a person publishes.

Ahead on

  • Payments & pricing, 60 against 35

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

Application Passwords have no scopes or expiry. Each one carries every capability of its user

Score by category

CategoryWeight this runStoryblokWordPressEdge
Reliability16%207978Storyblok +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26865Storyblok +3
Agent ergonomics13%16.27874Storyblok +4
Security & auth14%17.57362Storyblok +11
Payments & pricing10%12.53560WordPress +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88083WordPress +3
Transparency & trust7%8.88068Storyblok +12
Negative events≤15-3-5
Total67.7 · B64.8 · B

Facts side by side

FactStoryblokWordPress
KindHTTP APIHTTP API
VendorStoryblok GmbHWordPress.org (open-source project)
Hosted endpointhttps://mapi.storyblok.com/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceProprietary service under Storyblok's terms. The SDKs, API clients and CLI in storyblok/monoblok are MITGPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too
Tools exposed7none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-022026-10-06
Terms last updatedcouldn't be readno document linked
Privacy policy last updated2025-10-06no date given
Customer content may train modelscouldn't be read
Terms restrict automated accesscouldn't be read
Terms restrict benchmarkingcouldn't be read
Terms or service can change without noticecouldn't be read
Arbitration or class-action waivercouldn't be read
Popularity68 stars, 433k npm/wk21k stars

Verdicts

Storyblok

The hosted MCP server covers the whole Management API with seven tools, OAuth scopes split into read, write and publish per space, and a confirmation step on deletes. The Management API has no public OpenAPI spec, no idempotency keys and no monitor on the public status page, and publishing is a GET request.

WordPress

The REST API is part of core, and a post created without a status is saved as a draft with revisions kept on the owner's server. Application Passwords carry no scopes, so limits come only from the user's role. Revisions can be read and deleted but not restored over REST, and a critical flaw was fixed on 22 September 2026.

Before you call either

Storyblok

  1. Pick the base URL by the space's region (mapi.storyblok.com for the EU, api-us, api-ca or api-ap otherwise). A token sent to the wrong region fails
  2. Create stories without publish to keep them as drafts, then call the publish endpoint. It is a GET, so never prefetch or blindly retry it
  3. Write translations as field__i18n__<code> keys inside the same content object, and set the component field to translatable first
  4. Upload an asset in three steps (signed response, POST to S3, finish upload). Through MCP the S3 step needs shell access for curl
  5. Stay under 3 calls a second on Starter and 6 on paid plans, and back off exponentially on 429. Saves that break a field's max_length return 422

WordPress

  1. Ask the owner for a dedicated user with the lowest role that fits. A Contributor can draft and edit its own posts but can't publish them
  2. Send the Application Password as Basic auth over HTTPS only. Core disables Application Passwords on plain HTTP outside a local environment
  3. Upload a file with POST /wp-json/wp/v2/media first, then set featured_media or reference the returned URL in the post content
  4. To roll back, GET /wp/v2/posts/<id>/revisions/<rev>?context=edit and POST its title and content to the post. There's no restore route
  5. Pass _fields=id,status,link,modified on lists and read X-WP-TotalPages. per_page stops at 100

Questions

Which is better for AI agents, Storyblok or WordPress?

Storyblok scores 67.7 (B) on agent readiness against WordPress's 64.8 (B), and leads in 5 of 7 scored categories. WordPress leads on payments & pricing.

Do Storyblok and WordPress need an API key?

Storyblok takes an API key or an OAuth sign-in. WordPress needs an API key.

Can an agent call Storyblok and WordPress without installing anything?

Storyblok has a hosted endpoint at https://mapi.storyblok.com/v1. WordPress runs on your own machine, with no hosted endpoint listed.

Are Storyblok and WordPress open source?

No open-source release is listed for Storyblok. WordPress is open source (GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too).

Other comparisons with Storyblok or WordPress

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.