Ad Legends · Model Context Protocol

MCP Server
for Brands

Brands asked if they could connect their own AI tooling to Ad Legends. Now they can. Point Claude Code, Claude Desktop, or Claude Design straight at your brand — read and write its memory, hand over a design system, and generate ads, all from inside Claude.

Connect · /settings/mcp Download onboarding skill OAuth for chat apps · API keys for the CLI · 149 tools 
claude mcp add --transport http ad-legends \
  https://www.adlegends.ai/api/mcp/brands \
  --header "Authorization: Bearer al_mcp_…"
The idea

Your brand becomes something Claude can reason over — and build with.

Ad Legends already holds a brand's memory: its voice and strategy, its visual identity, its characters and products, its audiences. The MCP server exposes that — safely, scoped, and revocable — so a brand owner can teach it, query it, and turn it into finished ads without leaving the tools they already work in.

Three surfaces
01

Brand memory, read & write

  • Durable memory, strategic identity, research
  • Design systems — import a Claude Design export, export ours back (DTCG)
  • Entities: characters, props, scenes, logos, voices — list, upload, archive
  • Audiences / ICPs, focus-group participants, signals
02

Fast Ads V3, from a prompt

  • Describe a strategy — get on-brand ads back
  • Runs the real V3 engine: concepts → brand-candy heroes
  • Owner-only, 9 credits, refunded on failure
  • Read past sessions + their generated assets
03

The Strategist, out front

  • Public, no-login funnel tool
  • Three ad strategies for any brand or URL
  • Each result invites you deeper into Ad Legends
How it works

Three steps, then it just lives in Claude.

Step 1

Add the connector

In a chat app (Cowork, Desktop, ChatGPT), add Ad Legends as a custom connector. In a CLI (Claude Code, Codex), mint a key at /settings/mcp.

Step 2

Sign in & approve

Chat apps send you to Ad Legends to sign in via OAuth and approve the scopes + brands — no key. CLIs use the key you minted.

Step 3

Work your brand

Ask Claude to read your audiences, teach it a new fact, hand over a design system, or make ads.

The catalog

149 tools; the core brand surface below.

Read

whoamilist_brandsget_brandget_brand_memoryget_brand_identityget_brand_guidelinesget_brand_researchexport_design_systemlist_brand_entitiesget_brand_entityget_brand_media_downloadlist_brand_entity_typeslist_audiencesget_audiencelist_focus_group_participantslist_audience_signalslist_brand_collaboratorslist_ad_sessionsget_ad_session

Write & make

update_brandupdate_brand_memoryupdate_brand_identityimport_design_systemadd_brand_entityadd_brand_entitiesset_primary_brand_entityupload_approved_brand_assetarchive_brand_entityupdate_audiencecreate_ads

Writes are owner-only by default. Guide ingestion, approved-asset upload, and primary-logo promotion also accept an authorized editor; every other collaborator write remains blocked. Every tool is scope-gated and logged.

Under the hood

Built to be trusted with a brand's keys.

Safe by construction

  • API keys or OAuth 2.1 (PKCE, rotating refresh) — only SHA-256 hashes stored
  • Gated behind a beta entitlement; every grant honors your plan live
  • Owner-only writes by default; narrowly listed editor-safe governance operations; per-call telemetry
  • Private media IDs plus five-minute MCP resource links — never a bearer or public bucket URL

One engine, no drift

  • Tools call shared services — no looping back through our own API
  • create_ads and the web ad-builder share one generation path
  • Long runs survive real clients (progress heartbeats, 300s)
0
security findings · fresh review
3
real ads generated end-to-end
44
tests · live-smoked on preview
Built on the Forge

Planned on paper, proven on real infra.

Every decision was locked in a handoff before code; each phase was proven — migrations run dev-first then prod, the auth boundary security-reviewed by a fresh reviewer, the design surface passed through Brass Hour's drift-checker, and the headline feature validated by generating actual ads. The compounding step: the web ad-builder and the MCP tool now run the same engine, so they can never fall out of sync.

Connect your brand to Claude.

Sign in from your chat app, or mint a key for the CLI — and your brand memory + ad engine are right there in the conversation.

Get connected