Skip to main content
Your AI advertising manager inside Cursor. One marketplace install gives you a Cursor subagent with 14 skills and 2 rules that auto-trigger the right workflow for every advertising task.

​
How It Works

Cursor’s agent mode uses an agentic loop: you describe a task, it reasons, calls tools, reads results, and repeats. When your task involves advertising, Cursor delegates to the ADSMCP subagent — which has its own prompt, memory, skills, and MCP tools.

​
What Makes Cursor Different

Two things no other client gives ADSMCP:
  1. Rules (.mdc files) — they fire on context, not on a command. Mention a campaign and the brand context and safety workflow load themselves.
  2. 14 separate skills — one per platform and one per workflow, so the agent loads the TikTok pixel rules when you’re on TikTok and nothing else.

​
Install

1. Open Customize and install ADSMCP In Cursor, open Customize in the sidebar, search adsmcp, select Install, and choose user scope (every project) or project scope (this folder only). From chat, /add-plugin adsmcp does the same thing. 2. Sign in The first tool call opens ADSMCP’s sign-in page. Sign in, authorize, and connect your ad accounts at adsmcp.com/connections. Full walkthrough with screenshots: Cursor setup. The same listing installs into Grok Bot.

​
What Gets Installed

Cursor Marketplace listing for ADSMCP showing 1 subagent, 14 skills, 2 rules, and 1 MCP server The ADSMCP plugin on the Cursor Marketplace — 1 subagent, 14 skills, 2 rules, 1 MCP server
[!NOTE] Nothing is copied into ~/.cursor/ by hand any more. The old install.sh script is retired — if you ran it, delete the adsmcp-* folders it left in ~/.cursor/skills/, ~/.cursor/agents/, and ~/.cursor/rules/ so they don’t shadow the plugin.

​
The 14 Skills

Skills appear under Agent Decides in Customize. Cursor matches them from what you ask; the / command forces one.

​
Behavior and contract

​
Workflows

​
Platforms

Each platform skill carries the traps that account for most failures on that platform: TikTok’s pixel-placement rule and the unsupported single-image ad, Meta’s required Facebook page ID, LinkedIn’s mandatory campaign group, Google’s asset-bundle expiry and ad-group-ID mismatch.

​
How Skills Work in Cursor

  1. Skill descriptions are always in context — Cursor knows what’s available
  2. Full skill content loads when you invoke it or Cursor matches it automatically
  3. You can invoke directly with /adsmcp-* or just describe what you want
Cross-platform wasted spend audit with savings estimate. Find wasted spend across all my platforms. Show me which keywords have spend but zero conversions, which Meta ads are fatigued, and how much I could save per month.
Sign up for ADSMCP — free to start 15 free tool calls/month. No credit card required. Connect your ad accounts in 2 minutes.

​
The Two Rules

Rules are .mdc files that fire on context instead of on a command. You can toggle each between Always, Agent Decides, and Manual under Customize → Rules.

​
brand-workspace

Auto-loads brand context on every advertising task:
  • Reads BRAND.md before answering any advertising question
  • Reads STRATEGY.md for active directives, and treats them as binding
  • Reads past decisions from .cursor/memory/performance-marketing-agent/MEMORY.md
  • Bootstraps a new workspace when BRAND.md doesn’t exist
  • Pulls fresh data rather than answering performance questions from memory
  • Updates context files when something significant changes

​
use-adsmcp

Enforces workflow safety automatically:
  • 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
  • Mandatory ad extensions for Google Ads campaigns
  • Post-creation verification before reporting success

​
Rules vs Skills

Rules and skills work together. The rule ensures safety; the skill provides the detailed workflow.
[!NOTE] Without rules, you say “create a Google Ads campaign” and Cursor might jump straight to create_search_campaign — which fails because there’s no keyword research, no asset validation, no strategy check. With rules, the same prompt triggers the full workflow automatically: connection check → strategy load → keyword research → asset validation → confirmation → creation → extensions → verification.

​
Context Files

The agent uses three persistent files. Cursor’s is BRAND.md (vs Claude Code’s CLAUDE.md).

​
BRAND.md — Brand Context

Created by /adsmcp-setup. Contains brand overview, voice, audiences, connected platforms, budgets, KPI targets, and performance snapshot. If you already have a BRAND.md that isn’t an ADSMCP workspace — a software project’s instructions, say — the agent leaves it untouched and tells you so, rather than writing over it.

​
STRATEGY.md — Strategic Decisions

Persists directives across sessions:

​
MEMORY.md — Past Decisions

Located at .cursor/memory/performance-marketing-agent/MEMORY.md. Tracks campaign actions, optimization results, and learnings.

​
The Agent Loop

When you invoke /adsmcp-performance-review in Cursor: 1. Rule activates brand-workspace fires, loading BRAND.md and STRATEGY.md into context. 2. Skill loads Cursor matches the performance review skill and loads its full workflow instructions. 3. Agent spawns The performance marketing subagent starts with brand context, strategy, and memory. 4. Data pull For each connected platform, calls performance and wasted spend tools via ADSMCP MCP. 5. Strategy check Compares campaign data against STRATEGY.md. Flags “Strategy Drift” items. 6. Results Presents a unified scorecard with recommendations and top 3 actions.

​
Web Research

Cursor’s agent has access to WebSearch and WebFetch for competitive research. Before creating any campaign, the agent:
  1. Crawls your website for positioning, pricing, and value propositions
  2. Searches for and crawls competitor websites
  3. Combines web data with ADSMCP data (search terms, keyword volumes)
  4. Presents a research brief before building your campaign

​
Safety Rules

​
Comparison with Other Clients

​
FAQ

Do I need the rules to use ADSMCP? No, but they make everything smoother. Without rules, you need to be more explicit (“first check my connections, then research keywords”). With rules, safety checks and context loading happen automatically.
Can I edit the rules and skills? The plugin’s copies update with the plugin, so edit them by adding your own alongside. Put project rules in .cursor/rules/ and personal skills in ~/.cursor/skills/ — yours load next to ADSMCP’s. To change a default outright, fork the plugin repo and load it from ~/.cursor/plugins/local.
What’s the difference between the subagent and Composer? Cursor’s Composer is the main agent mode for coding tasks. The ADSMCP subagent is a specialized agent that Composer delegates to when advertising tasks come up. The subagent has its own context, so ad workflows don’t bloat your coding session.
Can I use ADSMCP in Cursor without the agent? Yes. The agent is one part of the plugin, and the 400+ tools work from any Cursor chat whether or not the subagent is invoked. Install the plugin from the Cursor Marketplace either way. It’s Verified by Cursor, and it’s the supported way to connect. Don’t add the MCP server by hand. You’d lose brand awareness, workflow enforcement, strategy persistence, and memory, and a second copy of the server duplicates every tool.
Is the plugin open source? Yes — ADSMCP/adsmcp-cursor-plugin, MIT licensed. Cursor requires marketplace plugins to be open source and reviews every update before it ships.