What Happens to CDP Implementation Expertise When Configuration Is Driven by AI Agents?

Angle

Tealium's Configuration Agent (MCP + natural-language configuration + human-in-the-loop approval) and Adobe's CX Enterprise Coworker (MCP + Agent2Agent open standards) introduce a new CDP operating model: AI agents configure the CDP, humans approve. The article doesn't ask whether AI will replace CDP teams — it asks the more useful question: what does 'implementation expertise' mean when the team's job shifts from configuration execution to configuration review and judgment? The answer changes hiring profiles, training priorities, and oversight model design before the technology is mature enough to force the question.

Key decision this helps with

How does MCP-powered CDP configuration change the skills, staffing ratios, and oversight models required to operate a CDP at production quality?

Tradeoffs the article will map

• AI-assisted configuration speed (rapid iteration, natural-language interface) vs. human judgment depth required for approval (expertise requirement shifts, not shrinks)
• MCP-based interoperability (connect any AI assistant to CDP configuration) vs. vendor-specific MCP implementation lock-in
• Human-in-the-loop approval models (maintain accountability) vs. latency introduced by approval cycles for production CDP changes

Open questions / uncertainties

• Whether MCP-powered CDP configuration becomes standard across vendors within 18 months or remains an early-adopter differentiator is unknown
• The risk surface of natural-language configuration (misinterpreted intent, undocumented changes, adversarial prompt injection into CDP configuration workflows) has no established threat model in the industry

Knowledge-graph nodes this draws from

• vendor.tealium
• vendor.adobe-experience-platform
• org-dim.operational-profile.marketing-led-cdp
• concept.real-time-decisioning