Alison AI MCP

Point any MCP client — Claude Code, Claude, Cursor, Codex — at Evo and it reads your creative-performance warehouse directly: spend and KPIs, creative tags, competitor intelligence, previews. Read-only, and scoped to the accounts each user already has.

Server URLhttps://evo.alison.ai/mcpstreamable-http read-only

14 tools13 analytics + creative previews

SSO sign-inOAuth 2.1 — no token to distribute

Server-side scopethe grant decides, not the client

What you get, and what you can't do with it.

The MCP surface is the same analytics engine that Evo's own analyst agent runs on, exposed directly to your client. Every tool is a read: nothing on this surface writes, mutates, or spends model budget. There is no SQL to author — the tools take structured arguments (metrics, dimensions, filters) and compile them server-side against the KPI registry.

The server speaks streamable-http at/mcp. Both/mcpand/mcp/work, so a client that doesn't follow redirects still connects.

Add the server with no credential. Everything else happens in your browser, once.

claude mcp add --transport http evo https://evo.alison.ai/mcp

Then run/mcp, pickevo, and authenticate — your browser opens on the Evo sign-in page, you choose a product and approve, and Claude Code keeps the token it's handed.

Pre-approving every tool is safe.All 14 are read-only and none spends model budget, so there is nothing here worth a per-call confirmation prompt.

The client's first call comes back401with aWWW-Authenticateheader pointing at/.well-known/oauth-protected-resource/mcp. From there the client registers itself and opens Evo, where the user sees two screens:

On approval the server mints a token and hands it back through the redirect. The client stores it and reconnects on its own; it is never displayed, and the product chosen on that screen is the ceiling on what the client can ever see. Some clients open the browser for you, others print the URL — same pages either way.

OAuth 2.1 with PKCE and dynamic client registration, so no client is pre-provisioned on either side:

GET /api/keyslists every client connected under your user — name, product, when it was created, when it was last used.DELETE /api/keys/{id}disconnects one. Revocation is immediate, not eventually consistent: authorization is re-resolved from the store on every single request and never cached, so the next call from that client fails closed.

The client cannot widen its own reach. Only the server decides what's visible.

Every request resolves the token to the accounts its user holdswithin the product it was approved for, and that set becomes the query grant. Anintegration_idsoutside the grant comes back as avalidation_error— never as data, never as a silent empty result. A token whose accounts carry no servable data is refused outright rather than handed zeroes.

The same rule governs the product tools, soget_creativecannot reach an asset the analytics tools would refuse.

draft_content— the agent loop's copy-writing tool — is deliberately not mounted here: it spends a model call per invocation, so exposing it would widen what a connected client can do rather than replace anything the read tools already offer.

Every call is logged with the calling user, the client's token and the product it was approved for, so traffic on this surface is attributable to a person rather than to a shared service account.

The map, not the API reference — your client reads every argument schema over the protocol and fills them in itself.scope_overviewis where a session starts: one call that reports what these accounts can be measured and grouped by.

Report rows carry creative ids, not images. When you want toseethe creatives, pass the ids fromrun_report,run_recipeorrun_competition_reportinto one batchedget_creativecall.

HTTP status codes cover transport and authentication only. A tool that refuses its arguments answers200with anerror_kindin the result, so your client can correct itself and retry rather than treating it as an outage.

Per-call blast radius is bounded at 150 integration ids in one list, andget_creativetakes at most 25 ids per call. Neither is the authorization boundary — the grant is.

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Let AI clients add payments to your website. Create checkout pages, events and forms and embed them on your site in minutes.

Airefs monitors your visibility in AI answers then creates the articles, answers and earned mentions that influence them.

Official remote MCP server for Canvora (canvora.ai): turn any idea, URL, doc, or PDF into on-brand visuals – carousels, posts, decks, and infographics in 100+ formats, native in 150+ languages. Brand kits, localization, PDF/PPTX export. Free tier. npx @canvora/cli

Product and onchain analytics for AI agents: query KPIs, funnels, retention, revenue, users, and wallet profiles.

Create, manage, publish, and analyze Inblog content through AI agents.

Browse cited competitive-intelligence reports and head-to-head competitor comparisons from any MCP-aware AI agent — live B2B SaaS data, sources included.

Official Loops MCP server for managing contacts, mailing lists, campaigns, transactional email, and account data.

AI visibility MCP for agencies and marketing teams to audit brand visibility in AI answers, monitor competitors and cited sources, and fix GEO gaps.

Intent based keyword monitoring for LinkedIn, X, Reddit, Hackernews, Bluesky