Head to head · Content management · October 2026 research run

Directus vs Payload

Directus scores 61.6 (C) on agent readiness against Payload's 53 (D), and leads in 6 of 7 scored categories. Both do content management.

Best headless CMS and website publishing for AI agents · All 136 cms comparisons

Which one, for what

Directus C

Best for Teams that already keep content in an SQL database and want an agent to edit items, files and the data model under a named user's permissions.

Ahead on

  • Reliability, 82 against 76
  • Schema & documentation, 81 against 70
  • Agent ergonomics, 73 against 64
  • Security & auth, 68 against 57
  • Payments & pricing, 83 against 68
  • Maintenance & community, 86 against 78

Watch for

Version 12 (10 June 2026) added licence enforcement. The free Core tier allows 3 Studio seats, 25 collections and 5 flows, and an instance over its limits is locked after a grace period

Payload D

Best for Teams that build on Next.js and want the content model in TypeScript, with drafts, versions and localisation in the free core.

Also in its favour

  • Open source

Watch for

38 security advisories on OSV in the 12 months to 4 November 2026, 7 critical, 28 published on 6 and 7 October

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Directus +15

Directus 83

Scored with the self-hosted rule, taking prices from the paid options beside the free tier. No x402, MPP or L402 (0). Core is $0, Team is $499 a month on an annual term or $599 monthly, extra seats are $50 each a month, and Directus Cloud hosting is a $99 a month add-on, all public. Enterprise is priced by sales (20). The Core tier is free to self-host with no card and no account, and Cloud has a 14-day trial (20). ADMIN_EMAIL, ADMIN_PASSWORD and ADMIN_TOKEN create the first administrator and a static token at start-up, so the REST route needs no browser. The docs enable the MCP server only through the Studio settings page, so we took 5 off (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

Payload 68

Scored with the self-hosted rule. No x402, MPP or L402 (0). The software is free under MIT, which the get-started page states. The only paid option, Enterprise, is priced by sales, and Payload Cloud is closed to new projects, so 15 of 20. No card and no account at Payload are needed (20). npx create-payload-app installs it, but the docs create REST and MCP API keys in the admin panel, so half (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Schema & documentation Directus +11

Directus 81

An OpenAPI file ships in @directus/specs with 70 paths, each instance serves its own at /server/specs/oas, and every MCP tool has a typed input schema. The spec's info.version still reads 10 (22 of 25). llms.txt, llms-full.txt and a raw Markdown copy of every docs page (10). Each tool has a one-sentence description and a prompt.md of instructions with worked examples, up to 13 KB for flows, and a system-prompt tool sets conventions (16 of 20). Actions are enums and validation uses strict unions per action, but item data, filters, deep, and field schema and meta are open records (8 of 15). The errors page lists HTTP statuses and error codes with the response shape, and guides show REST, GraphQL and SDK examples side by side (14 of 15). A monthly changelog, release notes and breaking-change pages per major version. REST paths carry no version and releases aren't semantic (11 of 15).

Payload 70

No OpenAPI file is published or generated by the core packages, because endpoints depend on each project's config. Every MCP tool carries a typed input schema built from the collection's fields, and the GraphQL schema is generated from the same config (20 of 25). llms.txt per major version, llms-full.txt and a Markdown copy of every docs page (10). Default MCP tool descriptions are one line, such as Create a document in a collection., unless the owner writes one in the plugin config. The docs tell owners to do so (10 of 20). Field inputs are typed with bounds on limit and depth, but where is JSON passed as a string. select became an object in the MCP find tools in 3.91.0 (10 of 15). REST operations show a request and a response each. No reference page for error responses or status codes was found (8 of 15). Semver, release notes on GitHub and separate docs per major version. REST paths carry no version (12 of 15).

Security & auth Directus +11

Directus 68

MCP OAuth uses PKCE with dynamic client registration or client ID metadata documents, issues a token with the single mcp:access scope and the MCP endpoint as audience, and lets administrators revoke clients. Static tokens are one per user, don't expire and are stored in plain text. We scored 26 and took 10 because ?access_token= in the URL is a documented option that the MCP guide uses for three clients (16 of 30). Access policies limit a user by collection, action, field and item rule, the MCP server is off by default, and deletes are refused unless Allow Deletes is on. No server-side approval step for other writes (16 of 20). A security guide for MCP covers prompt injection, mixing servers and auto-approval, with advice only (11 of 15). The activity log records user, action, time, IP address, user agent, collection and item, kept 30 days on Core (11 of 15). A disclosure policy with private GitHub reports and a security address, advisories published in public, and SOC 2 Type 2 with a penetration test report on the trust centre. No bug bounty found, and security.txt returns 404 (14 of 20).

Payload 57

REST keys are per user, revocable and regenerable, shown once, and limited by that user's access control down to field level. MCP keys carry per-collection, per-operation switches. Both travel only in the Authorization header. Neither expires, and there is no OAuth (24 of 30). A find-only MCP key is a config switch away and the collection's access control still runs under it. Nothing asks a person to approve a delete or a publish in the free edition (14 of 20). Documents hold text written by other people, and no prompt-injection guidance was found. overrideResponse can strip fields before they reach a model (3 of 15). Versions record each change, and onEvent and verboseLogs expose MCP calls to the owner's own logging. No built-in audit log (7 of 15). SECURITY.md gives a reporting address and, since 16 October 2026, says Payload pays no monetary rewards and runs no bug bounty. Advisories are published on GitHub with affected versions, patches and workarounds. No security.txt or SOC 2 statement was found (9 of 20).

Agent ergonomics Directus +9

Directus 73

Default mode lists 12 tools, the 11 to 30 band, but each definition carries its whole instruction file, 78,855 bytes in total at v12.5.0, so we scored 10 and added 8 for registry mode, which lists three tools and loads details on demand (18 of 25). limit (default 100), offset, page, fields, filter, search, sort and aggregate, with QUERY_LIMIT_MAX as a server cap (20). One error shape with a machine-readable extensions.code. Missing items answer FORBIDDEN, not 404, by design (17 of 20). Tools set readOnlyHint and destructiveHint, though one items tool covers reads and writes and is marked destructive. No idempotency keys were found in the reviewed documentation (10 of 20). Few required parameters. One official SDK, @directus/sdk for JavaScript and TypeScript (8 of 15).

Payload 64

Four MCP tools per enabled collection and two per global, so five collections give 20 tools, the 11 to 30 band (15). We added 7 because the owner enables collections and operations one by one, each key narrows the list again, and find tools default to 10 documents at depth 0 with select (22 of 25). Page-based pagination with limit and page, 17 where operators, sort, select and populate (20). REST errors come back in an errors array and MCP tools return a text line beginning Error:. Neither format is documented as a list an agent can match on (10 of 20). No idempotency keys, and no readOnlyHint or destructiveHint in the plugin source. An update by id is repeatable (4 of 20). Few required parameters and sensible defaults. The one official client, @payloadcms/sdk for TypeScript, is labelled beta (8 of 15).

Maintenance & community Directus +8

Directus 86

v12.6.0 was tagged on 27 October 2026 (30). Seven tagged releases in the 90 days from 3 August (12.3.0, 12.3.1, 12.4.0, 12.4.1, 12.5.0, 12.5.1 and 12.6.0) (20). 339 open issues, the newest labelled and answered, with 170 commits on main since 10 July, per the 8 October check, not re-read on 1 November. Closed-issue counts weren't readable (17 of 25). @directus/sdk is current and is the only official SDK. We couldn't reach the official MCP registry, which matters less for a server built into the product (10 of 15). Dependency updates for CVEs land in each release (12.5.1 and 12.6.0 among them), CI passed on main on 8 October and CodeQL runs (9 of 10).

Payload 78

3.92.1 is tagged on 27 October 2026, 8 days before this check (30). Nine stable releases from 3.87.1 on 6 August to 3.92.1 on 27 October 2026, with 4.0.0 betas alongside, which don't count (20). 225 issues opened against 116 closed since 10 July, 140 open issues awaiting triage and 763 open pull requests, per the 8 October check (12 of 25). @payloadcms/sdk ships with each release but is beta and TypeScript only, and the official MCP registry has no Payload entry, which fits a plugin that runs inside each install (8 of 15). CI runs on every push. The latest 3.x run had failed on 8 October 2026, and runs couldn't be read on 4 November (8 of 10).

Reliability Directus +6

Directus 82

Read with the local-software lines, since the graded surface is the self-hosted software on the free Core tier. Directus Cloud's status page isn't scored here. Official Docker image directus/directus and npm package directus 12.6.0, with Node.js 26 or later in engines since 12.6.0 and the supported databases listed (20). The Check workflow passed on the 10 most recent runs on main on 8 October, per the 8 October check, not re-read on 1 November, and separate end-to-end and CodeQL workflows exist (25). 339 open issues. The 15 newest carry labels and one to eight comments, but we couldn't read closed counts, and at least 20 advisories were fixed between June and September 2026 (15 of 25). The docs say releases don't follow semantic versioning and any release may break. Breaking changes are listed per version, and 12.1 to 12.6 each had some (7 of 15). Version 12, and the MCP server isn't marked beta (15).

Payload 76

Read with the local-software lines, since the graded surface is software its owner hosts. Official npm packages, with Node.js ^22.23.4 || >=24.22.1 in engines and in the installation docs since 3.92.0 (20). A public ci workflow runs unit, type, integration and end-to-end tests on every push to 3.x. GitHub's pages and API couldn't be read on 4 November, so the result is unread (15 of 25). 499 issues were open on 8 October, 140 of them awaiting triage, with 225 opened and 116 closed since 10 July 2026, not re-read (12 of 25). A written semver policy marks breaking commits with ! and lists them in release notes, but lets security fixes and experimental APIs change in minor releases (14 of 15). 3.x is the stable line, with 4.0 in beta (15).

Score by category

CategoryWeightDirectusPayloadEdge
Reliability16%8276Directus +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8170Directus +11
Agent ergonomics13%7364Directus +9
Security & auth14%6857Directus +11
Payments & pricing10%8368Directus +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8678Directus +8
Transparency & trust7%6265Payload +3
Negative events≤15-15-15
TotalC 61.6/100D 53/100

Facts side by side

FactDirectusPayload
KindHTTP APIHTTP API
VendorMonospace Inc. (Directus)Payload CMS, Inc. (Figma)
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFree
x402nono
LicenceMSCL-1.0-GPL (Monospace Sustainable Core Licence 1.0), source-available with a licence key for paid tiers, each version converting to GPL-3.0 after four years. @directus/sdk is MITMIT for the core and the official packages. Enterprise add-ons are sold separately through sales
Tools exposed12none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-27
Terms last updatedno date givenno document linked
Privacy policy last updated2026-06-092024-03-28
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity38k stars, 23k npm/wk45k stars, 1.1M npm/wk
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Directus

The built-in MCP server runs under the connecting user's permissions, supports OAuth limited to the MCP endpoint and refuses deletes unless an administrator allows them. A licence check caps the free Core tier at 3 seats, 25 collections and 5 flows, and Directus published more than 30 security advisories in the past year.

Payload

Payload generates REST, GraphQL and MCP interfaces from one typed config, with drafts, restorable versions and per-key MCP permissions in the free MIT core. The security record is the limit. 38 advisories were published in the 12 months to November 2026, most on 6 and 7 October, so an install older than 3.90.0 is exposed. No OpenAPI file is published.

Before you call either

Directus

  1. Connect with OAuth or an Authorization: Bearer header. Don't put the token in the URL as ?access_token=, where it can be logged
  2. Use /mcp?tool_mode=registry when the client loads every tool definition. Default mode sends each tool's full instructions, about 79 KB in total
  3. Read the schema tool before writing. Item payloads are untyped objects, so field names and types come only from the data model
  4. Publish a version with POST /versions/{id}/promote over REST. The MCP items tool refuses system collections such as directus_versions
  5. Count translation and junction tables against the 25-collection Core limit before creating collections

Payload

  1. Check the installed version first. Anything below 3.90.0 carries published critical advisories, and 3.92.0 and later need Node.js 22.23.4 or 24.22.1, so ask the owner to upgrade before writing
  2. Send REST keys as Authorization: {collection-slug} API-Key {key} and MCP keys as Authorization: Bearer {key}. The two key kinds are separate
  3. To publish, set _status: 'published' in the data. The draft parameter only relaxes validation and chooses where an update is written
  4. Upload files with multipart POST to the upload collection, with other fields as JSON in _payload. No MCP upload tool is documented
  5. Roll back with POST /api/{collection-slug}/versions/:id after listing versions. Versions exist only where the collection config enables them

Questions

Which is better for AI agents, Directus or Payload?

Directus scores 61.6 (C) on agent readiness against Payload's 53 (D), and leads in 6 of 7 scored categories.

Do Directus and Payload need an API key?

Directus takes an API key or an OAuth sign-in. Payload needs an API key.

Can an agent call Directus and Payload without installing anything?

No hosted endpoint is listed for Directus. No hosted endpoint is listed for Payload.

Are Directus and Payload open source?

No open-source release is listed for Directus. Payload is open source (MIT for the core and the official packages. Enterprise add-ons are sold separately through sales).

Other comparisons with Directus or Payload

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.