Attentive's New CEO Bets on AI Personalization — and Hands Agents the Keys

Attentive confirmed in its own press release that co-founder Eric Miao, newly installed as CEO, is steering the company toward individualized marketing decisions made in real time across the full customer lifecycle, rather than segment-based campaigns sent on a schedule. Independent coverage from MarTech Series confirmed the same announcement date and added the detail that matters most for anyone who doesn't work inside Attentive's product team directly: Model Context Protocol (MCP) support is now generally available, giving AI assistants like Claude and ChatGPT a standing, authenticated connection into a brand's Attentive workspace.

That second part is easy to read past as a developer footnote. It isn't one. MCP support means a marketer — or anyone with access to the right credentials — can now type a plain-language prompt and have an AI tool pull segment data, build an audience, or create and edit a live campaign inside a client's account, without going through Attentive's own interface at all.

What Actually Changed

Before this release, connecting an AI assistant to a platform like Attentive meant custom API work, a middleware layer, or no connection at all — campaigns and segments were built by a human clicking through the dashboard. MCP flips that: it is a standard protocol that lets an AI tool discover what actions an app supports and call them directly, authenticated and in real time. Attentive is one of a growing list of marketing platforms shipping MCP support this year, and the practical effect is the same everywhere it lands — a new access path into live client data and live client campaigns that didn't require a login to the platform's actual UI.

Why This Is an Agency Problem First

A nonprofit or professional services client rarely audits which tools are plugged into their SMS and email platform. That oversight sits with whoever manages the account day to day — usually the agency. An MCP connection is, functionally, a new integration with write access to campaigns and customer data, and most of the governance questions that come with any new integration apply here just as hard: who authorized the connection, what scopes does it have, and is anyone reviewing what it changes before it goes to a client's list.

• Check whether MCP is enabled on every client Attentive account your firm manages, not just the ones actively being redesigned.
• Treat an AI-tool connection like any other third-party integration — scoped access, a named owner, and a review step before it can send to a live list.
• Don't assume "it's an official Attentive feature" means "someone already reviewed it for this client" — general availability means it's live by default, not that it's been vetted for your account.

This is exactly the kind of platform-level integration review a dedicated SaaS development team is built to run: someone who treats a new AI connection into a client's martech stack as a scoped, documented integration rather than a toggle someone flips and forgets.

The Pattern Behind the Update

MCP support is becoming table stakes across marketing SaaS this year, not a one-off Attentive move — the direction across the category is toward AI tools with standing, authenticated access to live customer data and campaign controls. Firms that treat each new AI integration as a quick toggle, instead of a piece of client infrastructure with its own access list, will keep discovering the gap the same way: after a client asks who built the segment that just went out.

If your firm manages an Attentive account — or any martech platform rolling out MCP — and nobody has reviewed what's connected to it, that's worth doing before your next campaign cycle. If the review turns up more than a quick settings change, book a free consultation and we can help you scope what needs governance.