The Alison MCP server is live. Your creative performance data, spend, KPIs, creative tags and competitor intelligence, is now readable directly inside Claude, Claude Code, Cursor, Codex and any MCP client, through one URL and a browser sign in. Launching with it: Evo, an experimental agent that showcases the data into takeaways and ready-to-run, ready-to-use videos, and the Alison API for your own stack.
One engine. Everywhere your team already works.
Here is why this is the launch we have been building toward. Think about where your questions actually happen now. Not in a dashboard you opened on purpose, but mid task, in a chat with an AI assistant. You are planning a campaign in Claude, reviewing code in Cursor, drafting a brief, and the question surfaces: which of our creatives are fatiguing? What is the competition running? Until today, answering meant leaving the conversation, opening another tab, and coming back. Today that changes.
The main event: your creative data, inside your AI workspace
The Alison MCP server exposes your creative performance warehouse to your AI workspace: spend and KPIs, creative tags, competitor intelligence, and creative previews. Ask in plain language, inside the conversation you are already having, and the answer comes back compiled from your live Alison analysis.
This is where it gets powerful. Your AI workspace already sees your other tools. Connect Alison, and one question can cross reference creative performance with CRM data, analytics and spend, all at once. “Which of our top spending creatives are driving pipeline, not just clicks” stops being a three-team project and becomes a single prompt.
Connecting takes one URL and a browser sign in. No API token to copy, no config file to edit, no credential to distribute across the team. Paste the URL, sign in with the Alison identity you already have, approve, done.
And it is safe by design, not by policy. The entire surface is read only: all 14 tools read data, and none of them can touch live campaigns or spend a cent. Access is scoped server side on every single request, so each connected client sees exactly the accounts its user already holds in Alison, and nothing more. Every call is logged to a person.
Evo: the agent that translates the data
An experiment that showcases the power of Alison’s MCP. The MCP delivers the data. Evo makes it speak your language.
Evo is the agent we built on top of the MCP, and it is our way of showcasing what the connection returns. Instead of raw metrics, Evo delivers clear, prioritized takeaways: what is fatiguing, what is winning, what to do next. The analysis is the same engine behind your Alison dashboard. The difference is the form it arrives in.
Then Evo goes one step further. It can turn those takeaways into ready to run videos, generated from what your data says works. Not just the insight, the asset. The gap between “we know what performs” and “we have a creative built on it” just got very short.
The Alison API: the build kit
For engineering and data teams, the Alison API opens the full analysis layer programmatically. Feed BI dashboards with creative performance and tag data. Join Alison insights with revenue data in your warehouse. Power internal tools your team already trusts. If your stack can consume an API, it can now consume Alison.
Why everywhere
The industry has spent two years generating more creative than ever. The bottleneck has moved: it is no longer the ability to create, it is the intelligence to guide creation. And intelligence that lives in one tab, opened on purpose, is intelligence that arrives late.
The way teams work has changed too. Questions start in AI assistants. Decisions happen mid conversation. A platform that only answers in its own dashboard is answering in the wrong room.
That is the thinking behind this launch. Not three features, but one decision: the intelligence should meet the team, not the other way around. Analysts live in the dashboard. Marketers ask Evo. Builders plug in through MCP and the API. Same intelligence, wherever your team already works.
How to get access
The MCP server, Evo and the API are live for Alison clients, running on your existing account and permissions. The MCP server connects with one URL and a browser sign in, and the [MCP documentation] has everything your team needs to connect in a minute. API access is provisioned through your account team.
Not an Alison client yet? Book a demo and we will show you the full surface running on real data.
Your data has answers. Now they are everywhere you ask.
