Adsagent AI Skills

AdsAgent Tri-Channel Plugin

MCP here means Model Context Protocol (the Claude/Cursor tool-calling standard). It does not mean Multi-Channel Platform.

Public skill pack and plugin for AdsAgent tri-channel hosted MCP: Meta, Google Ads, and TikTok. It supports ChatGPT, Claude, Codex, and Cursor.

Directory SEO one-liner: AdsAgent is a hosted Meta Ads MCP (Model Context Protocol) plus Google Ads & TikTok MCP — connect Claude/Cursor via adsagent.md/connect.

Install:

• Claude plugin: claude plugin marketplace add adsagents/adsagent-ai-skills then claude plugin install adsagent@adsagent
• Cursor plugin: install AdsAgent from Cursor Marketplace (this repo's .cursor-plugin/ + mcp.json)
• Dashboard fallback: AdsAgent dashboard -> Settings -> MCP Access -> Copy install prompt (clients without plugin support)

Supported clients:

Skills describe client-independent behavior. Install steps differ per client and live in Installation.

Distribution split (important):

Official GitHub repo: github.com/adsagents/adsagent-ai-skills

Website: adsagent.md
Official links hub: adsagent.md/connect
Skill pack landing page: adsagent.md/skills
Support: support@adsagent.md

Privacy: AdsAgent Privacy Policy

Also listed on Product Hunt, Cursor Directory, and MCP Market.

Current contract version: 0.7.83. The plugin slug is adsagent (marketplace key adsagent).

Claude, Codex, Cursor, and Glama read this repository root. Skills live only in skills/. Marketplace source is ./. Cursor reads .cursor-plugin/plugin.json and root mcp.json. Glama builds from the root Dockerfile and root skills/.

For contributor cloud environments, provision uv in the image and run the bundled bash scripts/cloud-agent-setup.sh; see cloud setup. Plugin users do not run this setup. New Meta connections default to the v2 product profile; all three hosted endpoints negotiate modern MCP 2026-07-28 stateless discovery while retaining supported legacy initialize clients.

Version history lives in CHANGELOG.md.

The local helper scripts/update_reminder.py compares strict semantic versions and stores only bounded version/timestamp state in ~/.cache/adsagent-ai-skills/update-reminder-v1.json. Pass --cache-dir to choose another directory. Cache failure never blocks MCP work.

What This Is

• A public Claude plugin marketplace package: behavior skills in skills/ plus the hosted MCP URLs in .mcp.json. Directory review scans the whole repository.
• A behavior guide for Claude Code, Cursor, Codex, and other MCP-aware clients.
• A reliability and safety layer that tells agents when to retry, when to wait, and when to stop.
• A versioned GitHub distribution for AdsAgent user onboarding and agent behavior guidance.
• A data-minimization contract for AI agents that should not scan AdsAgent like a raw database.
• Optionally, a Glama-deployable AdsAgent Skill Pack (docs) stdio MCP that lists and reads public skills/ Markdown. See docs/glama-release.md.

What This Is Not

• Not the hosted AdsAgent Meta, Google Ads, or TikTok MCP backend. The optional Docker/Glama image only serves this repository's public docs; ads tools remain on the HTTP URLs in mcp.json and require AdsAgent OAuth.
• Not the Anthropic Connectors Directory MCP listing (that is registered separately on the hosted servers).
• Not a complete MCP tool reference.
• Not an SDK.
• Not a local transport relay for ads APIs.
• Not a disclosure of AdsAgent backend routes, schemas, database tables, or internal diagnostics.

For Claude Code plugin installs, OAuth MCP setup comes from this repo's .mcp.json. For clients without plugin support, the AdsAgent dashboard install prompt remains the manual fallback:

AdsAgent dashboard -> Settings -> MCP Access -> Copy install prompt

Use that copied prompt only for a manual connection when the account exposes MCP Access. Installed Claude plugins already include the three URLs. The setup skill guides users from a missing connection through authorization to their original advertising task.

Connect After Installing

Start with the channel you need. Installing the skill pack does not authorize an advertising account, and a Meta task does not require Google or TikTok setup.

Then ask: "Check my Google Ads connection and help me finish any missing authorization, then show yesterday's campaign performance." Substitute your channel and task. AdsAgent checks that channel, supplies a browser link when needed, waits for you to finish, and resumes the same task. For a connection check alone, it reports the result without starting a report.

Each server has its own OAuth authorization. Use the same AdsAgent login in the browser and client; never copy an OAuth token between the three URLs.

For multiple OAuth tenants on one server, each workflow retains its selected connection through approval, confirmation, task queries and retries. Selection uses an explicit account choice, uniquely verified object ownership, or the sole available connection; ambiguous choices need one account question. See multi-tenant routing for the installed policy and optional client-adapter dispatch guard.

Platform authorization and initial asset/history sync are separate steps; "connected" does not mean history is loaded or ads are ready to launch.

Claude connection controls are documented in the official custom connector guide and Claude Code MCP guide.

Official MCP Registry manifests

Three hosted-server manifests record the existing md.adsagent/* entries in the official MCP Registry, first published on 2026-08-18. Version 1.0.0 was verified active/latest on 2026-10-09; these files are snapshots, not pending publications. GitHub first-time directory inclusion remains under manual review. The public skills, guides and connection configurations are MIT; the hosted advertising backends are proprietary.

Included Skills