Alison, Everywhere
One engine. Three access points. Ask Evo in plain language, plug Alison into your AI workspace through MCP, or build with the API. The same creative intelligence, wherever your team already works.
3 Access Points
Evo for marketers, MCP for AI workspaces, API for engineering and data teams. Every one of them runs on the same analysis engine behind your Alison dashboard.
14 Read-Only Tools
The MCP surface exposes analytics, creative previews and competitive intelligence. Nothing on it writes, mutates or touches live campaigns.
0 Tokens to Distribute
Sign in with the identity you already have. OAuth handles the rest, and access is scoped server-side to the accounts each user already holds.
Meet Evo, the Analyst Everyone on Your Team Can Ask
Not everyone wants to swim in dashboards. Evo is a standalone chat, opened from a simple link, where anyone can ask questions about their connected ad accounts in plain language. Evo pulls the answer from your Alison analysis and returns it simplified, with suggested follow-up questions to keep you moving. No dashboard required, no analytics background required.
Book a Demo
Evo
by Alison
Online
Alison Inside Claude, Cursor and Codex
The Alison MCP server brings your creative performance warehouse into that workspace, readable directly from Claude, Claude Code, Cursor or Codex. Cross-reference Alison data with everything else your AI workspace can see, from CRM to analytics to spend, and let one question pull from all of them at once. No token to copy, no config file to manage, and access is always scoped to the accounts you already hold.
Connect Your AI WorkspaceWorks with your existing Alison login. Not a client yet? Book a demo.
The Alison API, Your Build Kit
For engineering and data teams who want Alison inside their own stack. The Alison API gives you programmatic access to the full analysis layer, so you can feed BI dashboards, power internal tools, and join creative intelligence with the rest of your company data on your terms.
Book a DemoOne Engine Behind All Three
Evo, MCP and the API are not three products. They are three doors into the same intelligence: the analysis engine and Creative Genome that power your Alison dashboard. Every answer, in every surface, is compiled from the same KPI registry against your live account data.
Analysts live in the dashboard. Marketers ask Evo. Builders plug in through MCP and the API. Same intelligence, wherever your team already works.
Book a DemoKey Features
Plain-Language Answers
Evo turns your Alison analysis into simple, direct answers anyone on the team can act on, no analytics background needed.
Read-Only by Design
Every MCP tool is a read. Nothing on the surface writes, changes campaigns or spends budget, so connecting is safe by default.
Scoped to Your Accounts
Access is resolved server-side on every request. Each user sees exactly the accounts they already hold in Alison, and nothing more.
Same Intelligence Everywhere
Dashboard, chat, AI workspace or your own stack: every surface runs on the same engine, so every team works from the same truth.
Frequently Asked Questions
What is Evo, and how is it different from the Alison dashboard?
Evo is a standalone chat interface for your Alison data, opened from a simple link in its own tab. The dashboard is built for deep analysis: filtering, comparing and drilling into creative performance. Evo is built for everyone else. You ask a question in plain language, and Evo returns an answer built from your Alison account analysis, simplified and ready to act on, along with suggested follow-up questions. Analysts keep living in the dashboard. Evo brings the same intelligence to the rest of the team.
Which AI tools does the Alison MCP server work with?
Any MCP client. That includes Claude, Claude Code, Cursor and Codex, and the list keeps growing as more tools adopt the Model Context Protocol. Setup is the same everywhere: add the server URL, sign in through your browser with your existing Alison credentials or SSO, choose which product the client may read, and approve. The connection is live from that point on, with no token to copy or distribute.
Is it safe to connect Alison to an AI assistant? What can it access?
Yes, and this is by design. The MCP surface is read-only: all 14 tools read data, and none of them can write, change live campaigns or spend budget. Access is scoped server-side on every single request, meaning each connected client can only see the accounts its user already holds in Alison, within the product approved at sign-in. You can view every connected client at any time and revoke access instantly, and revocation takes effect on the very next call.
Can the MCP server or the API change my campaigns or spend money?
No. Both surfaces are read-only. They analyze and report, they never act on live campaigns. Any request outside your permitted scope is rejected with a clear validation message rather than returning partial or misleading data. If you want recommendations turned into action, that happens where it always has: in your workflow, with your approval.
What can I build with the Alison API?
The API exposes the full analysis layer programmatically, so engineering and data teams can bring creative intelligence into their own stack. Common builds include feeding BI dashboards with creative performance and tag data, joining Alison insights with CRM and revenue data in your warehouse, and powering internal reporting tools. If your team can consume an API, it can consume Alison.
Don’t Just Take Our Word for It
Alison was a great fit for our already data-driven work process. With Alison’s input, Scatter Slots’ creatives received a much-needed boost, leading to an instant improvement in performance. This not only enhanced the game’s already strong position but also sparked a wave of fresh ideas, enabling the swift development of unique concepts and further success in the creative strategy.
Gadi Shoshani
VP Marketing at Murka Games
Official Partner of Leading Social and Digital Channels
