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
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)
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
| Category | Weight this run | Storyblok | WordPress | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 79 | 78 | Storyblok +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 68 | 65 | Storyblok +3 |
| Agent ergonomics | 13%16.2 | 78 | 74 | Storyblok +4 |
| Security & auth | 14%17.5 | 73 | 62 | Storyblok +11 |
| Payments & pricing | 10%12.5 | 35 | 60 | WordPress +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 83 | WordPress +3 |
| Transparency & trust | 7%8.8 | 80 | 68 | Storyblok +12 |
| Negative events | ≤15 | -3 | -5 | |
| Total | 67.7 · B | 64.8 · B |
Facts side by side
| Fact | Storyblok | WordPress |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Storyblok GmbH | WordPress.org (open-source project) |
| Hosted endpoint | https://mapi.storyblok.com/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Proprietary service under Storyblok's terms. The SDKs, API clients and CLI in storyblok/monoblok are MIT | GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too |
| Tools exposed | 7 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-02 | 2026-10-06 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | 2025-10-06 | no date given |
| Customer content may train models | couldn't be read | |
| Terms restrict automated access | couldn't be read | |
| Terms restrict benchmarking | couldn't be read | |
| Terms or service can change without notice | couldn't be read | |
| Arbitration or class-action waiver | couldn't be read | |
| Popularity | 68 stars, 433k npm/wk | 21k 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
- 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
- Create stories without
publishto keep them as drafts, then call the publish endpoint. It is a GET, so never prefetch or blindly retry it - Write translations as
field__i18n__<code>keys inside the same content object, and set the component field to translatable first - Upload an asset in three steps (signed response, POST to S3, finish upload). Through MCP the S3 step needs shell access for curl
- 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
- 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
- Send the Application Password as Basic auth over HTTPS only. Core disables Application Passwords on plain HTTP outside a local environment
- Upload a file with POST
/wp-json/wp/v2/mediafirst, then setfeatured_mediaor reference the returned URL in the post content - To roll back, GET
/wp/v2/posts/<id>/revisions/<rev>?context=editand POST its title and content to the post. There's no restore route - Pass
_fields=id,status,link,modifiedon lists and read X-WP-TotalPages.per_pagestops 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
- Contentstack vs Storyblok
- Contentstack vs WordPress
- DatoCMS vs Storyblok
- DatoCMS vs WordPress
- Directus vs Storyblok
- Directus vs WordPress
- Ghost vs Storyblok
- Ghost vs WordPress
- Payload vs Storyblok
- Payload vs WordPress
- Sanity vs Storyblok
- Sanity vs WordPress
- Storyblok vs Strapi
- Storyblok vs Webflow
- Strapi vs WordPress
- Webflow vs WordPress
Machine-readable
- This page as Markdown
/compare/storyblok-vs-wordpress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/storyblok.json·/api/v1/tools/wordpress.json - From a terminal
anchor compare storyblok wordpress(the CLI) - Over MCP
compare_tools {"a": "storyblok", "b": "wordpress"}at/mcp, no key