MCP Client Services amplifier. Turn it on and the team ships better.

A turn-on-able MCP one-sheet the Diray client services team installs once and runs every week. It does three things: builds case studies from a single prompt, surfaces portfolio precision tactics that worked, and assembles proof points for any pitch. The bridge from the operating-system mandate to the two platforms that come next.

THE SHAPE OF IT

Three capabilities. One install.

Same MCP server, three operator-facing tools. Each maps to a job the client services team does every week.

Tool 01 · Builder

Case study builder.

One simple prompt. The skill pulls client name, campaign, channels, dates, MediaINSIGHTS attribution. Returns a one-page case study in the canonical Problem → Approach → Results frame, in Diray voice, ready to drop into any deck.

Tool 02 · Precision

Portfolio precision tactics.

"Show me every campaign in this category where we beat the brand's prior-year ROAS by 20% or more, and the three tactical moves that did it." Searches the portfolio and returns ranked tactics with the proof to back them.

Tool 03 · Proof

Proof-point assembler.

For any pitch, prospect, or category, returns the three strongest proof points Diray can stand behind. Outputs in three formats: pitch-deck stat, email one-liner, leave-behind paragraph.

THE CASE STUDY BUILDER · ONE PROMPT

What the operator actually types.

No template-filling, no formatting wrestling. The operator names the client and the campaign. The skill does the rest.

$ diray case-study build —client "Acme Brand" —campaign "Q3 Holiday DRTV + CTV" —period "Sep–Dec 2025"

Pull Campaign plan, channel mix, creative versions, flight dates, MediaINSIGHTS ROAS read, retail sell-through.

Frame Problem (in the client's own words) · Approach (the three tactical moves) · Results (numbers, with method).

Voice Outcome-first, hedged where the data is directional, sourced everywhere. Diray voice, never marketing prose.

Output Case study HTML on the Diray deck engine (1920×1080, theme-aware) plus a one-paragraph version for emails and a stat-only version for decks.

WHAT IT'S WIRED INTO

The MCP connections.

The skill is only as good as the data it has. Phase one wires it to the systems Diray already runs.

MEDIAINSIGHTS

ROAS · Attribution

Read-only access to the closed-loop attribution surface. Pull campaign-level lift, baseline comparison, MMM outcomes.

RETAIL

SELL-THROUGH

Retail-media networks, syndicated retail data, category share. Validates the sales-velocity claim.

PORTFOLIO

CASE LIBRARY

Every prior case study and its source data, structured so the precision-tactics tool can search across it.

THE BRIDGE · WHAT THIS LEADS TO

The on-ramp to the two platforms.

The MCP one-sheet is not the destination. It is the first concrete operator surface the team uses every week, which gathers the data, language, and voice that the two platforms inherit.

Platform 01 · Internal

Media Analysis.

Every time the MCP skill returns a precision-tactic finding, that finding earns a place in the Media Analysis surface. Operators see what worked, what did not, and what to look for next, scored against the Diray operating model.

Platform 02 · Client

Impact Engine.

Every case study the builder ships ladders into the Impact Engine surface clients see. The Impact Score becomes the visible scoreboard. Clients start asking: "what's our Impact Score?"

HOW THE TEAM TURNS IT ON

Installation, when the MCP server lands.

The Diray engineering on-call wires the MCP server to MediaINSIGHTS read-only.
Client services team runs diray mcp install in their Claude Code session.
The first case study the operator builds becomes the calibration artifact: Drew + the lead AE review, lock the voice, ship.
The team uses the builder before any pitch, any QBR, any case-study refresh.
Quarterly: the precision-tactics index gets re-scored against new portfolio outcomes.

Why this exists

Read the mandate first.

The MCP one-sheet is one of the deliverables the operating-system mandate calls for. The full picture lives in Research 11.02.

Open 11.02 · The Operating System mandate →