Newsroom · MCP
News Agent
Your archive already holds the answer. News Agent is the layer that lets someone ask for it in a sentence.
Overview
A news database is a strange asset. It grows every day, it is the most valuable thing a publisher owns, and almost nobody in the building can query it. Search returns a list of headlines and leaves the reader to do the reading.
News Agent sits between the two. An MCP server exposes the archive as something an agent can actually reason over — not a keyword index, but structured, queryable knowledge. A second MCP server exposes your APIs, so the same agent can reach live systems as well as history.
The result is that a desk editor, a researcher or a reader can ask a question in a sentence and get an answer drawn from your own material, with the stories it came from.
Capabilities
What News Agent does
MCP over the news database
The archive is exposed through Model Context Protocol, so queries are handled flexibly rather than being locked to a fixed set of endpoints somebody has to maintain.
MCP over your APIs
A second server wraps the systems you already run, which means any MCP-capable agent can integrate without a bespoke connector being written for it.
Ask in plain language
What happened, when, who was involved, and how the story moved — asked as a question and answered from your own reporting.
Grounded in your archive
Retrieval runs over your material, and answers carry the stories they came from, so an editor can check the source rather than trust the summary.
Bring your own agent
Because the interface is MCP, you are not tied to our chat surface. Point your own assistant at it and it works.
Runs where the archive lives
Deployed on your infrastructure or ours. For a publisher whose archive cannot leave the building, on-premise is the normal configuration.
Who it is for
Built for these situations
Newsrooms with deep archives
Publications sitting on decades of reporting that is technically online and practically unreachable.
Research and reference desks
Teams answering "when did we last write about this" dozens of times a day, by hand.
Product teams building reader features
Anyone who wants a conversational surface over their own journalism without rebuilding retrieval from scratch.
Deployment
- On-premise, in your cloud, or hosted by us.
- Works with a hosted model API or a local model where nothing may leave the network.
- MCP endpoints for both the news database and your existing APIs.
- Schema mapping and tuning to your archive are part of the engagement.
Questions
Frequently asked
Does it need our archive to be in a particular format?
No. Mapping the MCP server onto your existing schema is part of the deployment — we work with the database you have rather than asking you to migrate.
Can we use our own AI assistant instead of yours?
Yes. The interface is Model Context Protocol, so any MCP-capable agent can connect to it directly.
Does our content leave our infrastructure?
Only if you choose a hosted model. Paired with a local model, the whole system runs inside your network with no external calls.
Is this a search engine?
No. Search hands you a list and stops. News Agent answers the question, and shows you which of your stories the answer came from.
Interested in News Agent?
Every deployment is customised to the organisation running it. Tell us about your environment and your constraints, and we will tell you honestly whether this is the right fit.