AI Marketplaces Leaderboard

Watching That

Claude connectorCommunity

Ask your ad stack data anything. Watching That brings your entire stack into Claude to surface yield insights, revenue performance and deli…

View in Claude directory
Tools
6

exposed by this connector

Movement

From our daily snapshots over the last 30 days.

Rank by popularity

#2225of 5,1834places up24h76places down7d
#1,716#1,857#1,998#2,139Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Rank by trending score

—not ranked—24h—7d
#2,033#2,070#2,107#2,144Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Popularity score

6,820+6524h+3617d
6,2926,4366,5806,7246,868Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

Trending score

——24h—7d
9,92111,35912,79714,235Sep 13Sep 19Sep 25Oct 1Oct 7Oct 12

In its categories

How this connector compares with others in the same category. Positions are counted within the category, not across the whole directory.

Data analytics787th of 1,936 by popularity · not ranked by trending score
Order by

All 1,961 Data analytics connectors

Media entertainment103rd of 293 by popularity · not ranked by trending score
Order by

All 295 Media entertainment connectors

Productivity1,150th of 2,822 by popularity · not ranked by trending score
Order by

All 2,842 Productivity connectors

Watching That connects Claude to the systems where your ad revenue actually lives: FreeWheel, Google Ad Manager, SpringServe, your SSPs, DSPs, SSAI, Prebid, Video Players, Apps, Webpages etc. Instead of exporting reports and building pivot tables, you investigate revenue and delivery by simply having a conversation.

Ask the questions you'd put to a senior analyst:

  • Why did revenue move yesterday, and which SSP, deal or geo drove it?
  • Where is fill rate slipping, and what changed?
  • Which line items or ad servers are erroring or dropping impressions?
  • Is there a discrepancy between what we served and what we were paid for?

Watching That answers with the numbers behind the answer, then lets you drill across dimensions (SSP, deal ID, device, geo, ad unit, ad server) to effortlessly arrive at root-cause in minutes and not hours or days.

It's built for how modern ad ops actually works: multiple SSPs, header bidding, FreeWheel, GAM and SpringServe side by side and the insights that live in the gaps between systems.

Who it's for: ad operations, revenue operations, yield and monetisation teams at broadcasters, streaming and FAST platforms, pay-TV operators, and digital publishers running programmatic display and video. If you own a revenue number and it's harder to see into than it should be, this is for you, whether you're a global broadcaster or a fast-growing publisher.

Watching That already monitors revenue for leading broadcasters and publishers. One major broadcaster used it to recover significant revenue that was quietly leaking; another top-tier news publisher relies on it to protect more than two million ad impressions every day.

Connect your stack and ask your first question.

Tools

  • allowed_long_term_dim_combinations
  • current_user
  • list_accessible_dss
  • list_available_dimensions
  • list_available_metrics
  • search
Categories
Made by
Watching That Ltd · Website
Sign-in
Required
Connector URL
https://mcp.watchingthat.us/
Transport
Streamable HTTP
Permissions
This connector reads the advertising data in your Watching That workspace: revenue, impressions, fill rate, eCPM and similar metrics, across dimensions like SSP, deal, device, geo, ad unit and ad server. It uses that data to answer your questions and investigate revenue, yield and delivery on your behalf. It only reads and analyses your data. It cannot change your campaigns, ad-server settings or any configuration, and it cannot access anything outside your Watching That account. Access is limited to the data your own account is already permitted to see.
Works with
Claude, Claude API, Claude Code, Claude Desktop
Industry
Media & entertainment
Added
July 1, 2026
More info