The Agent Surface

Every CMS decision in media publishing history has been about the same question: who interacts with the content? The answer used to be obvious. Editors write. Readers read. The CMS serves both.

In 2026, a third actor arrived. Agents — AI systems that read, write, search, and act on content without human mediation. And the CMS platforms that let agents in are pulling away from the ones that don't.

Three Eras of CMS Evaluation

Era 1 built for editors. Era 2 built for developers. Era 3 builds for agents. Each era didn't replace the previous one — it added a new consumer of the CMS. The platforms that won Era 2 aren't automatically winning Era 3. New evaluation criteria are emerging: Does the CMS have an MCP server? Can agents discover the content model without receiving the entire schema? Do agents inherit the same permission model as human editors?

The shift happened fast. Anthropic published the Model Context Protocol in November 2024. By May 2026, over 10,000 public MCP servers exist globally, with close to 100 million SDK downloads. The protocol is now governed by the Linux Foundation and adopted by OpenAI, Google, and Microsoft. MCP did for agent-to-system communication what REST did for web APIs — it made it boring enough to be universal.

Who Shipped

The competitive map has redrawn itself in six months:

Seven of the eight platforms in this table shipped agent accessibility in the first quarter of 2026. One — Arc XP — is shedding engineering staff too fast to build it. And one — Graphene-Selene — is a question mark.

What Agent Accessibility Actually Requires

An MCP server is not a REST API with a new name. The technical requirements are specific:

Self-discovery. An agent connecting to a CMS should not receive the entire content schema upfront. Brightspot's approach — agents request only what they need at each step — keeps context lean and reduces accuracy loss. Token efficiency matters. Sanity's bulk operations "burn through token budget fast" when iterating across thousands of documents. The CMS that serves its entire schema in one payload will hit context window limits on the first query.

Permission inheritance. When an AI agent acts on behalf of a junior editor, it gets that editor's access rights — not elevated permissions. This isn't a nice-to-have. It's the difference between a CMS that deploys agents safely and one that creates a security incident. Brightspot built this natively. WordPress.com uses OAuth 2.1 to scope agent access.

Structured content models. This is where the architecture from Era 2 pays off — or doesn't. Flat, page-shaped content blocks undermine every agent capability. Typed schemas with explicit references let agents reason about content relationships. Publishers who built headless-first content models in Era 2 have a structural advantage entering Era 3. Publishers still on monolithic page builders are building on sand.

Write access. Read-only agent integration is table stakes. WordPress's March 2026 expansion to full write access — agents can draft, publish, moderate comments, restructure taxonomies, fix metadata — is the bar. A CMS that lets agents read content but not act on it is a library, not a platform.

The Arc XP Cautionary Tale

Arc XP is what happens when a CMS enters Era 3 already dying. The Washington Post's external CMS product has never turned a profit on approximately $100M in annual revenue. 130+ layoffs since 2023. Revenue declining 12%. Rate-limited API at 30 requests per minute. No export capability — authenticated CDN URLs, non-exportable password hashes, no bulk data extraction.

Publishers on Arc XP face a compounding problem: the platform isn't building agent accessibility, and it's actively harder to leave. Migration estimates run $30-60K for redirects alone, $25-60K for identity systems, with 5-15% subscriber churn risk during transition. The lock-in was always the business model. Now the lock-in is the threat.

WordPress VIP, by contrast, starts at $25K/year (vs. Arc XP's $400-600K), handles 100K+ requests per second, and now has full MCP agent support. The cost-performance gap has never been wider, and the capability gap is opening.

The Graphene-Selene Question

People Inc built their own CMS. That was the right decision in 2017 when they broke About.com into six verticals and needed a content platform that served both editorial workflow and D/Cipher's targeting engine. It was the right decision again when they migrated 1M+ Meredith content pieces onto the same stack. Building Graphene-Selene gave them tight integration between content, taxonomy, and ad targeting that no off-the-shelf CMS could match.

But Era 3 changes the calculus.

Every CMS vendor in the table above shipped MCP support with dedicated product teams. Brightspot has an AI division. WordPress has Automattic's platform engineering. Sanity has a hosted MCP server managed as a first-party product. These vendors are competing on agent accessibility as a feature — pouring engineering resources into making their CMS the best agent surface available.

People Inc is pouring engineering resources into D/Cipher+, the People app, Inversion product experiments, and MyRecipes cross-brand identity. Agent accessibility for Graphene-Selene is competing for time on a roadmap already stretched across four strategic priorities, inside a financial envelope where debt service consumes 81% of free cash flow.

A Graphene Services and Search internship posting (Calgary — People Inc's Edmonton-area hub) confirms active development. But an intern building features is not the same as a product team shipping an MCP server. The question isn't whether Graphene-Selene is a good CMS. It's whether a proprietary CMS can keep pace with the vendor ecosystem when a new capability layer emerges this fast.

What the CTO Should Do

People Inc doesn't need to abandon Graphene-Selene. They need to decide whether it becomes an agent surface or stays an internal tool.

If agent surface: Build an MCP server for Graphene-Selene. Expose the content graph — the same five-consumer architecture I've written about before — to external agents with self-discovery and permission governance. This makes People Inc's content visible to the agentic web. It lets AI agents query the content graph, understand the taxonomy, and interact with structured content. This is the high-investment, high-control path.

If internal tool: Deploy WebMCP on the rendered sites instead. WebMCP — now in Chrome 149 origin trial — lets agents interact with published pages without touching the CMS at all. Lower investment, but agents see rendered HTML, not structured content. They get the page, not the graph. D/Cipher's taxonomy, Graphene's entity relationships, Selene's cross-brand connections — none of that is visible through WebMCP. You're showing agents the magazine, not the intelligence.

The first path is harder. It's also the only one that preserves People Inc's structural advantage — the deep integration between content, taxonomy, and targeting that no competitor has replicated. If agents can access Graphene-Selene natively, D/Cipher's 100 million taxonomy connections become not just an ad targeting asset but a content intelligence layer available to every AI system that queries the content graph.

If agents can only see rendered pages, People Inc's content looks exactly like everyone else's.

The CMS decision used to be about editors. Then developers. Now agents. People Inc made the right call building their own when the question was editorial efficiency and ad integration. But every era adds a new consumer, and each new consumer demands its own interface. The vendor ecosystem shipped the agent interface in Q1 2026. The question for Graphene-Selene is whether the team that built the best proprietary CMS in publishing can build the agent layer before the advantage of owning the CMS becomes the burden of maintaining it alone.