$HEADLESS SYSTEMS
03 / Scorecard / Content Management

TinaCMS

F
Headless Index
25/100
denominator 20
JAIRF
N/A
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
TinaCMS is not built for machine consumption today. The Headless Index thesis-fit score of 25/100 fails the floor checks of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are not built for machine consumption today: agents can poke at them, but the dashboard remains the source of truth, and the rest of this verdict explains where TinaCMS lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. On API-first posture, the structured collectors did not surface an OpenAPI spec, GraphQL endpoint, or SDK ecosystem strong enough to score this criterion automatically. Editorial follow-up should confirm whether an API spec exists behind authentication or in unindexed documentation.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? GraphQL introspection enabled at content.tinajs.io. The schema is the developer-authored TypeScript model. Schema discoverability is reference-class for git-based CMS.[2] Driving this product through an agent is not realistic with the current surface: the API exists, but it is not the contract the vendor optimises for. On headless operability: On headless operability, the docs crawl did not produce topic coverage sufficient to score programmatic setup, billing, teams, schema, or CLI workflows. A targeted AI review pass should visit the vendor's docs index and confirm what programmatic surfaces actually exist.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: On MCP posture, no official MCP server was detected in the vendor's GitHub organization and no community server was published to the MCP registry under their name. This may change rapidly given the recent MCP adoption curve.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: TinaCMS fails the floor checks of the methodology, with schema observability[5] as the most acute gap. Any agent integration here will be brittle and short-lived until the vendor invests in machine-readable surfaces. Not currently suitable for agent consumption.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intentUnknown
Unknown

TinaCMS is git-based headless CMS with visual editing. Content lives in the git repo as JSON or markdown; the API layer provides a GraphQL Content API at content.tinajs.io plus a Tina Admin GraphQL surface for editor flows. SDKs in TypeScript with tight Next.js, Astro, and Remix integration. The product positioning is content-as-code rather than database-backed CMS.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPI specNot found across 17 probe paths
  • −GraphQL endpointNot discovered (6 probes; project-scoped endpoints require a real project ID)
  • −SDKs maintainedNone detected in vendor org
cite (3)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
  • github.sdks@2026-05-20
Headless operationUnknown
Unknown

Content models (schemas as TypeScript code), collections, fields, references, and media management are all code-first. The tinacms CLI handles local dev, schema generation, and deployment. Self-host plus TinaCMS Cloud share the GraphQL contract.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.topics_found.setup@2026-05-20
  • docs.topics_found.billing@2026-05-20
  • docs.topics_found.teams@2026-05-20
  • docs.topics_found.cli@2026-05-20
  • docs.topics_found.schema@2026-05-20
MCP & agent postureUnknown
Unknown

No first-party TinaCMS MCP server. The git-based content model is structurally agent-friendly because agents can read and write the underlying repo through standard git tools; MCP-driven content authoring is feasible without protocol-specific wrappers.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·MCP detector statusTimed out during collection (likely GitHub search API rate limit without GITHUB_TOKEN). No verified evidence about MCP presence.
cite (1)
  • mcp.registry_query@2026-05-20
Schema observability5/20
scored

GraphQL introspection enabled at content.tinajs.io. The schema is the developer-authored TypeScript model. Schema discoverability is reference-class for git-based CMS.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPINot discovered across 17 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (6 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
Webhooks & eventsUnknown
Unknown

Git-backed content changes propagate through standard git hooks plus deployment-platform webhooks (Vercel, Netlify). TinaCMS itself does not publish a webhook product; the integration is at the deployment layer.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-20
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:F band triggered: HeadlessIndex=25

04 / Embed

Show TinaCMS's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

TinaCMS mini badge preview
Get embed code
Peers in Content Management
PayloadF
Headless Index 25/100
Builder.ioF
Headless Index 25/100
StrapiD
Headless Index 35/100
See full Content Management ranking →