Kayzen Analytics
springwqLABSCO SUMMARY
Permission-aligned by design, which is the part that matters for an analytics estate.
Access is granted through the product profile you already use, so connecting an agent does not widen anyone's reach — it inherits it. That is the right shape for enterprise analytics, and it is also why there is a setup step before anything works: someone with admin rights has to add MCP Access to the profile.
What it is
Adobe hosts this one. It connects an MCP client straight to your Analytics environment so an agent can query data, explore trends, build segments and manage components without going through the UI.
What you get
Natural-language querying over your analytics data, trend exploration, segment building and component management. Adobe's tool reference lists each tool.
Requirements
An Adobe account whose product profile includes the MCP Access permission — the same permission model as the UI, so the agent sees exactly what you see. OAuth server-to-server is also supported for headless use.
Setup effort
Paste a URL, then sign in — add the endpoint to your client and sign in to Adobe
USE CASES
01
Answering a reporting question without building a report
Ask what a metric did last quarter and it queries the analytics environment directly instead of someone assembling a workspace project.
02
Building a segment from a description
Describe the audience in words and let it construct the segment definition in your environment.
03
Keeping agent access inside existing permissions
Grant MCP Access on the product profile so the agent inherits the same visibility as the person using it, and no more.
BEFORE YOU INSTALL
What to know first
Requires
an MCP client that can reach a remote endpoint
INSTALLATION
Connect your client
Add the endpoint to your client and sign in to Adobe.
Server setup
ENDPOINT URL
https://aa-mcp.adobe.io/mcp
