Skip to content

Review request: PR #182 β€” refresh adspirer-ads-agent entry (repoint to ads-mcp)Β #183

@amekala

Description

@amekala

Hi Anthropic team πŸ‘‹ β€” opening this to surface PR #182 for review.

Context

The adspirer-ads-agent entry in .claude-plugin/marketplace.json was added via PR #95 (merged 2026-03-13) and pins amekala/adspirer-mcp-plugin at a Feb 14 sha. Since then:

  • The Claude Code listing at https://claude.com/plugins/adspirer-ads-agent has grown to 1,288+ installs
  • Active development moved to the monorepo amekala/ads-mcp (the repo we submitted via the community form on 2026-04-16, approved status: Published)
  • Product expanded significantly: LinkedIn Ads support, Meta video/carousel campaigns, Google YouTube and Demand Gen, conversion tracking audit, scheduled briefs, multi-account management β€” now 150+ tools total

The pinned entry is stale. Users installing from the public listing today get Feb 14 content.

What PR #182 does

  • Repoints source.url from amekala/adspirer-mcp-plugin β†’ amekala/ads-mcp (actively maintained)
  • Bumps source.sha to current ads-mcp HEAD (2b50e11)
  • Updates description to reflect current capabilities (150+ tools)
  • Changes category from productivity β†’ marketing (no paid-media plugin in that surface today)
  • Adds author: { "name": "Adspirer" } to match convention used by Sanity, Apollo, Zoom

Verification

  • Plugin installs cleanly via /plugin marketplace add amekala/ads-mcp then /plugin install adspirer-ads-agent
  • MCP server at https://mcp.adspirer.com/mcp β€” streamable HTTP, OAuth 2.1 with Dynamic Client Registration + PKCE
  • Verified working in Claude Cowork via Personal marketplace path
  • Test account available on request

Related

  • Original entry: PR add(plugin-json): adspirer-ads-agentΒ #95 (merged 2026-03-13) β€” cc @tobinsouth
  • Community form submission: 2026-04-16 "Adspirer Ads Agent" (Published)
  • Earlier community submission: 2026-03-22 "adspirer-ads-agent" (Published) β€” also pointing at adspirer-mcp-plugin, potential duplicate once new submission syncs

Ask

  1. Review and merge PR update(plugin-json): adspirer-ads-agent β€” repoint to ads-mcp, bump sha, recategorizeΒ #182 so the public listing reflects current capabilities
  2. Guidance on whether the Mar 22 community submission should be superseded by the Apr 16 one to avoid duplicate listings in the community marketplace mirror

Happy to adjust scope, open a separate PR for anything contentious, or hop on a call.

Thanks!
β€” Abhi (Adspirer)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions