Skip to main content
The performance marketing agent is an expert advertising manager that sits on top of Adspirer’s 400+ tools. It knows your brand, remembers past decisions, follows your strategy, and uses proven workflows to manage campaigns across all platforms.

How It Works

The agent reads your brand context, strategy directives, and past decisions before choosing the right skill and tools for your request. Every action goes through the same pipeline — whether you’re analyzing performance, creating campaigns, or writing ad copy.

Where It Runs

The agent is available across 3 IDEs:
The agent is installed automatically with the plugin or one-command installer. See the Claude Code, Cursor, or Codex setup guides.

Brand Workspace

When you first run setup (/adspirer:setup in Claude Code, /adspirer-setup in Cursor, $adspirer-setup in Codex), the agent creates a brand workspace — a set of local files that give it context about your business, strategy, and past decisions.

What Setup Creates

Brand Context File

The brand context file is the foundation. It contains everything the agent needs to make brand-aware decisions:
The more brand docs you drop into your folder before running setup, the better the agent’s ad copy and recommendations. Brand guidelines, media plans, competitor analyses, and audience research all improve output quality.

Strategy Playbook

STRATEGY.md is where strategic decisions persist across sessions. When you analyze competitors, review performance, or make strategic decisions, the agent saves confirmed directives to this file. All skills read it before executing.

Why This Matters

Without strategy persistence, each session starts fresh. You might spend 30 minutes analyzing your competitive landscape, concluding “don’t bid on broad match competitor terms — they’re too expensive.” Then when you create a campaign, the skill does its own keyword research and recommends those exact terms. With STRATEGY.md, the analysis produces directives that are saved and enforced:

Directive Types

What Triggers Saving

Not every conversation produces directives. The agent classifies conversations before persisting:
Directives are only saved after you explicitly confirm them. The agent proposes, you approve. Nothing is saved automatically from casual conversation.

How Skills Use Strategy

Every skill reads STRATEGY.md before executing:
  1. Campaign creation — loads directives at Step 0, uses them as context for keyword research, bidding, targeting, and ad copy. Flags conflicts between research results and directives.
  2. Keyword research — after getting results, cross-references against AVOID/PREFER directives. Deprioritizes matching AVOID terms and highlights PREFER terms.
  3. Ad copy — checks Creative Direction and Competitive Positioning directives for messaging guidance.
  4. Performance review — flags campaigns that violate active directives as “Strategy Drift” items.
  5. Wasted spend — flags campaigns violating directives as priority waste sources.

STRATEGY.md Structure


Memory

MEMORY.md tracks past decisions, learnings, and your preferences across sessions. Available in Claude Code and Cursor. What gets saved to memory:
  • Campaign actions taken (what was created, modified, or paused)
  • Optimization results (what worked, what didn’t)
  • Your preferences (reporting format, approval style, platform priorities)
  • Key learnings (which audiences convert best, seasonal patterns)
What doesn’t get saved:
  • Raw performance data (always pulled fresh from Adspirer)
  • In-progress work or temporary analysis
  • Unconfirmed conclusions
The agent reads memory at the start of each session and when analyzing performance, providing continuity across conversations.

Rules

Rules are IDE-specific safety and workflow enforcement files. They complement skills by auto-triggering behavior based on context.

Cursor Rules

Cursor supports .mdc rule files that apply automatically when relevant. Adspirer ships two: brand-workspace.mdc — Auto-loads brand context on every advertising task:
  • Reads BRAND.md and MEMORY.md at session start
  • Reads STRATEGY.md for active directives
  • Bootstraps new workspaces if BRAND.md doesn’t exist
  • Updates context files when significant changes happen
use-adspirer.mdc — Enforces workflow safety:
  • Always checks connections first
  • Read-before-write enforcement
  • User confirmation before spend-affecting actions
  • Campaign creation in PAUSED status
  • Strategy directive checks before campaign creation and keyword operations
  • Mandatory ad extensions for Google Ads campaigns
  • Verification before reporting success

Rules in Action

Without rules: You say “create a Google Ads campaign” and Cursor jumps straight to create_search_campaign — which fails because there’s no keyword research, no asset validation, and no strategy check. With rules: The same prompt triggers a full workflow — connection check, strategy load, keyword research, asset validation, user confirmation, campaign creation (PAUSED), ad extensions, and post-creation verification.

Codex Safety Rules

Codex uses campaign-safety.rules to block direct API calls to ad platforms:
This ensures all ad platform operations go through Adspirer’s authenticated, auditable pipeline — not raw API calls.

IDE Feature Comparison


FAQ

No. You can connect Adspirer MCP directly and use the 400+ tools without the agent. But the agent adds brand awareness, strategy persistence, memory, and workflow orchestration — turning raw tools into a managed advertising system.
No. All campaigns are created in PAUSED status. The agent always asks for your confirmation before any action that affects spend. This is enforced by both skills and rules.
The agent uses switch_primary_account to manage different accounts. Each brand folder has its own context file, strategy, and memory — so you can manage multiple clients by working in different folders.
Not yet. ChatGPT supports MCP connectors (tools) but not agent files, skills, or rules. You get the full 400+ tools but without workflow enforcement or brand awareness. Perplexity supports skill uploads (SKILL.md) for workflow guidance. The Claude, Claude Code, Cursor, and Codex integrations support the full agent experience.
Strategy directives are guidance, not rigid rules. Skills use them to inform research — not bypass it. If a directive conflicts with fresh data, the agent flags the conflict and asks you. You can archive or update directives anytime. The Decision Log includes dates so you can see when directives were last validated.
Yes. The agent prompt is a markdown file. Edit it to change default behaviors, add custom workflows, or modify how the agent interacts with you. The source is in the ads-mcp repository.
If the agent can’t reach the MCP server (all tools fail, not just one platform), follow these steps:
  1. Check tool permissions — read tools should be set to Always allow, write tools to Custom (ask each time). Blocked tools prevent the agent from executing anything.
  2. Disconnect and reconnect the Adspirer connector in your AI client settings, then complete the OAuth flow again.
  3. Refresh your Adspirer session — log out of adspirer.ai, log back in, then return to your AI client.
Claude and ChatGPT web users: Connectors may disconnect every 1–2 weeks. This is normal behavior for web-based clients — just re-enable and re-authenticate.Important: If some platforms work but one doesn’t (e.g., Google works but LinkedIn fails), that’s a platform-specific issue, not a connection problem. Reconnect just that platform at adspirer.ai/connections.See Troubleshooting FAQ for more details.
Last modified on July 8, 2026