Overtone MCP Server

Most developer tooling work still happens through a UI a human drives. Overtone MCP server moves it into the conversation instead. Real-time news with tone analysis, brand safety, and narrative shift signals for AI agents.

The short version

An MCP server that gives any agent real-time news plus the contextual intelligence to use it well — tone distribution, emerging stories, narrative shifts, spike alerts, and tone-over-time charts — powered by Overtone's publisher network.

• What's the tone of coverage on a topic — is the public mood angry,
• What's emerging right now that had zero coverage yesterday?
• Where is the narrative turning — which topics are shifting tone
• Is there a spike in anger or fear around something I'm watching?
• How has tone trended over time on a given story?

The tools it exposes

The server publishes 8 tools. What each one is for:

• Codex — The Codex tool exposed by this server
• news — Articles on a topic, each tagged with tone, brand-safety signals, article type, and concepts. Use for "what's happening with X"
• tone — Emotional tone distribution across recent coverage of a topic — happy, funny, hopeful, informational, angry, sad, fearful, plus the dominant_tone
• pulse — Pollable spike detector. For each watched tone (default angry / sad / fearful), returns spike_ratio vs. a baseline window and a boolean spiking
• emerging — Concepts appearing in the last 24 hours that had zero coverage in the prior 48 hours — candidate emerging stories. Cluster-filtered to ≥3 articles
• velocity — Concepts whose tone distribution has shifted most sharply between the prior 48 hours and the most recent 24 hours. Answers "where is the narrative
• timeseries — Tone trajectory over time for a topic. bin is hour, 6h, or day. Returns an ordered series of per-bin tone averages, article_count, and dominant_tone
• report — Called silently after the agent presents articles to the user, to log which displayed_urls it actually showed. Helps Overtone understand what

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: OVERTONE_NEWS_API_KEY, OVERTONE_NEWS_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Overtone's toolset — Codex, news, tone and 5 more — is a fair guide to whether it matches your workflow. It is maintained by CKBrennan; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Overtone's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.