Add Agency Memory alongside the MCP tools you already use. Give your AI agents the brand knowledge, playbooks, and account details they need for each client.
For solo agencies and teams managing dozens of clients.
“Prepare a campaign for Northstar.”
Codex
BUILT FOR SOLO OPERATORS AND AGENCY TEAMS
SOLO MODE
Move between clients and tools without rebuilding context. Every connected AI agent reads the same workspace. Keep your knowledge available across the agents and conversations you use.
AGENCY MODE
Give each person or AI connection its own MCP key. Everyone works from the same maintained brand context, while you choose which keys can make changes.
One current brief per brand: positioning, audiences, messaging, terminology, and market context.
Brand-specific instructions for recurring work: reporting rules, campaign checks, naming conventions and keyword rules.
The exact ad, social and analytics assets each brand uses, organized by ownership, links, and defaults.
Choose whether all keys or selected keys can edit. Every change is versioned and attributable.
A SHARED FOUNDATION
Add it to Claude Desktop, Claude Code, Codex, Cursor, or another compatible MCP client alongside the creative and marketing MCPs you already use.
Add positioning, audiences, tone, offers, and playbooks in the app, or update them through a connected agent with write access.
The agent retrieves relevant brand knowledge, then uses your connected tools to create images, videos, designs, landing pages, or campaigns.
MCP is the connection that lets an AI agent access external tools and context.
Agency MemoryPRODUCT PREVIEWMaintain brand knowledge in the app or through a connected agent with write access. Use version history to keep changes traceable.
BUILT FOR WHAT COMES NEXT
Your agency’s tools will evolve. Keep the knowledge about your clients in a shared home, and connect the agents you choose to use next. Your brand context remains available across new conversations, new workflows, and new tools.
For connected, MCP-capable workflows.
THE CONTEXT GAP
Every operator on the account works from one shared source of client truth.
Needs the brand personality, visual direction, and audience.
Seedance + brand contextNeeds the positioning, offer, and ad account details.
Google Ads + brand contextNeeds the voice, offer, and funnel playbooks.
Design tools + brand contextNEWS + INSIGHTS
Practical guides to giving your AI agents better brand context and building repeatable workflows across your agency.
A practical brand brief for AI work: what to record, how to make it specific, and how to keep it current across clients and tools.
Read articleOne client, several people and agents. A step-by-step workflow for retrieving brand context, checking outputs, and keeping approved decisions reusable.
Read articleBEFORE YOU CONNECT
Agency Memory gives your team and connected AI agents a shared source of client and brand context. Organize clients and brands, maintain Brand Knowledge, write repeatable Playbooks, and record the platform accounts and assets each brand uses. Agents retrieve that context through MCP, the Model Context Protocol.
The app provides connection instructions for Claude Desktop, Claude Code, Codex, Cursor, and other compatible MCP clients. The connection uses Streamable HTTP with an MCP key sent as a bearer token. Claude Desktop uses a local bridge. A client that only offers an OAuth connection or cannot send the required authorization header may need a different setup. A regular browser chat is not automatically compatible.
No. Every active MCP key can read all clients, brands, and records in its workspace. The permission controls decide whether it can also change memory; they do not limit which brands it can read. Issue keys only to people and agents you trust with that workspace’s contents.
In Solo mode, the MCP writes switch in Permissions controls writes for every MCP key. In Agency mode, each key has its own Can edit memory setting in Agent access. Owners and admins can edit through the app. Changes to an MCP key’s effective write permission apply on its next request.
Agency Memory supplies context. Your separately configured advertising, analytics, and creative tools perform external work. Registering an account in Platforms records its identifiers, relationships, and brand assignment; it does not authenticate with the provider or grant permission to publish, change budgets, or spend.
Changes permitted by the caller’s write access apply directly; Agency Memory does not put them into an approval queue. Version history and audit records help you trace changes afterward. If your workflow requires human review, begin with a read-only key and review proposed changes before enabling writes. Instructions in a Playbook do not replace permission controls.
YOUR TOOLS. YOUR TEAM. YOUR BRAND TRUTH.
Connect Agency Memory alongside the tools you already use. Keep your client context consistent across agents, workflows, and teammates.
Read the setup guideIllustrative workflow with synthetic Northstar data: Agency Memory connects to a shared agent box containing Claude and Codex. A marketer asks Codex to prepare a campaign. Codex retrieves audience, tone, offer, and assets from Agency Memory, then calls an independently connected advertising MCP. A designer asks Claude for launch visuals. Claude retrieves the same brand context and calls a creative tool MCP. The agent box branches to the available tools. Agency Memory supplies context; the agents operate the tools. Tool connections are configured separately and do not imply bundled integrations or partnerships.