---
title: "MCP Server for Spotify Ads: Setup, Tools & Claude Plugin"
description: "How to reach Spotify Ads from an AI client in 2026: Synter MCP server, Spotify's own agent plugin, what each can actually do, and how to choose."
date: 2026-09-03
draft: false
rendered: markdown
category: guides
tags:
  - "AI Marketing"
  - "Paid Media"
---

## MCP Server for Spotify Ads: Complete 2026 Guide

Spotify advertising sits in an unusual spot for anyone automating paid media. The inventory is genuinely differentiated, since listening moment is a targeting signal no visual platform has, and the tooling around it is younger than the rest of your stack.

There are two routes to consider: our hosted MCP connection for cross-platform reporting and creative work, and Spotify's official agent plugin for workflows through its Ads API. This guide explains their setup and scopes so you can choose the route that fits your task.

This guide covers both routes, what each can actually do as of September 2026, and how to pick.

*Tool coverage verified against our hosted MCP tool reference on 5 September 2026.*

## **Two Different Things Called "Spotify Ads MCP"**

The phrase is used for two products that work differently, and conflating them is the most common confusion in this topic.

Our MCP server is a hosted Model Context Protocol server covering 16 ad platforms, including Spotify. One connection, one API key, and Spotify sits in the same agent context as Meta, TikTok, and Snapchat.

**Spotify's own plugin** is not an MCP server. Its [ads-agentic-tools](https://github.com/spotify/ads-agentic-tools) package, Apache 2.0 licensed, describes itself as "a Codex, Claude Code, and Antigravity CLI plugin package that lets you manage Spotify advertising campaigns through natural language. Create campaigns, target audiences, launch ads, and pull performance reports." Their [engineering write-up](https://engineering.atspotify.com/2026/5/spotify-ads-api-claude-plugins) is explicit about the protocol choice: "This plugin is opinionated. To build fast, we focused on Claude Code, macOS, used a CLI-first approach backed by an OpenAPI spec, and deliberately avoided MCP for now."

So if you are searching for an official Spotify Ads MCP server, there is not one. There is an official plugin covering three CLI clients, and there are third-party MCP servers that include Spotify.

## **Why Spotify Chose a Plugin Over an MCP Server**

Their reasoning is worth reading if you are making similar decisions, because it is a technical argument rather than a positioning one.

The Spotify Ads API v3 has "over 30 resource types, nested targeting structures, and multi-step entity hierarchies where campaigns contain ad sets that contain ads." Expressing that as MCP tool definitions "would produce a massive tool registry that would consume significant context window space in every interaction, whether or not the user needs those endpoints." The plugin instead loads only the reference documentation a given request needs.

The second reason is about auditability. Every API call the plugin makes is a visible curl command shown to the user, who can copy it, modify it, and run it independently. In Spotify's words, this "provides auditability and user control in an advertising system where every request can impact real budgets."

That is a platform choosing its architecture around the fact that money moves, which is the right instinct and worth noticing.

## **Setting Up Spotify's Agent Plugin**

The plugin covers Codex, Claude Code, and Antigravity CLI. Its architecture has four parts, which is useful to know because it explains what you can change:

  - **Skills** define the slash commands. Each is a self-contained Markdown file describing the command's behavior, endpoints, request formats, and output handling.
  - **Agents** handle freeform language. A request-builder agent triggers when you describe an advertising task conversationally and decomposes it into the right sequence of API calls.
  - **Hooks** intercept calls before execution. A PreToolUse hook transparently refreshes OAuth tokens and injects HTTP headers.
  - **Settings** store per-user configuration such as credentials, ad account, and environment in a local file that stays out of version control.

Most of it is Markdown, alongside a handful of scripts and per-platform manifests. As the [engineering write-up](https://engineering.atspotify.com/2026/5/spotify-ads-api-claude-plugins) puts it: "There is no compiled code in this plugin. There is no build step, no package manager, no bundler, no transpiler." So you can read every skill, see what it will send, and edit it if your workflow needs something different.

Prerequisites are one of those three CLIs, a Spotify Developer account with an ads-enabled app, an ad account ID, and Python 3.8+ for the automated OAuth flow, with a manual fallback if you do not have it.

Install, by client:

\# Claude Code
claude plugin i spotify-ads-api

\# Codex
codex plugin marketplace add spotify/ads-agentic-tools

\# Antigravity CLI
agy plugin install https://github.com/spotify/ads-agentic-tools

After adding the marketplace in Codex, restart Codex, open /plugins, and install and enable the Spotify plugin. Then set up the Spotify side: create a Developer app, add http://127.0.0.1:8080/callback as a redirect URI, tick Ads API, and accept the API terms against the ad account you want to use. Run /spotify-ads-api: configure to complete OAuth, or /configure on Antigravity. Three auth modes are supported: automated OAuth, a manual flow if Python is unavailable, and a legacy direct-token mode with no refresh.

Worth knowing about the write model before you point it at a live account. Campaign, ad set, and ad changes stage as validated drafts by default, "including requests that do not use the word draft", and publish only after a separate request and explicit confirmation.

## What Synter MCP Actually Does for Spotify Today

Use the current tool and script catalogs to check the operations available for your connected Spotify account.

Our [hosted tool reference](https://docs.synterai.com/mcp/tools) includes these Spotify reporting and creative tools:

|  |  |  |  |
| :-: | :-: | :-: | :-: |
| Capability | Tool | Type | Cost  |
| Pull Spotify Ads metrics | pull\\_spotify\\_ads\\_performance | read-only | 2 credits |
| Generate ad creative sized for Spotify | Creative generation tools, platform: Spotify | write | varies by tool |
| Generate ad copy for Spotify | Ad copy tools, platform: Spotify | write | 5 credits |

For Spotify campaign creation, targeting, budgets, and scheduling, use the supported operations in our [Spotify integration](https://docs.synterai.com/integrations). Through MCP, use list_available_scripts and inspect_script to identify the relevant operation and its arguments before calling execute. Named cross-platform tools have their own platform restrictions.

We support Spotify reporting, creative work, and campaign operations through our integration. The route for each action depends on the exposed tool or script. Check its schema, account selection, and permissions before execution. Spotify also provides an official plugin for its Ads API.

Setup, if reporting and creative are what you need:

claude mcp add synter-ads \\
  --transport http \\
  https://mcp.synterai.com \\
  --header "X-Synter-Key: syn_your_api_key_here"

Connecting the Spotify ad account itself is a separate step and runs through OAuth in the browser. Account connections and read-only reporting carry no connector fee. pull_spotify_ads_performance is priced at 2 credits in the [tool reference](https://docs.synterai.com/mcp/tools).

## Synter MCP vs Spotify's Plugin

|  |  |  |
| :-: | :-: | :-: |
|   | Synter MCP | Spotify's agent plugin  |
| Type | Hosted MCP server | CLI plugin package, explicitly not MCP |
| Publisher | Synter | Spotify |
| AI clients | Claude, ChatGPT, Cursor, Codex, Amp, Windsurf | Codex, Claude Code, Antigravity CLI |
| Platforms | 27, Spotify among them | Spotify only |
| Spotify reads | Yes, pull\\_spotify\\_ads\\_performance | Yes |
| Spotify campaign writes | Supported through our Spotify integration; inspect the relevant script and permissions | Yes, staged as drafts, published on confirmation |
| Creative generation | Yes, Spotify-sized images and copy | No |
| Cross-platform comparison | Yes | No |
| Auth | API key for the server, OAuth for the ad account | OAuth; automatic refresh on macOS, manual fallback on Windows |
| Cost | Metered in credits | Free, Apache 2.0 on GitHub |

Choose our hosted MCP when Spotify belongs in a wider cross-platform workflow. Choose Spotify's plugin when you want its first-party campaign workflow. Confirm the available action and permission scope in either route.

### **What the plugin can do**

Seventeen skills, grouped by what they are for:

|  |  |
| :-: | :-: |
| Area | Skills  |
| Setup | configure |
| Planning and building | campaign-strategy, build-campaign, clone |
| Managing | campaigns, ads, bulk, assets, audiences |
| Reporting | report, dashboard, export |
| Measurement | measurement-setup, measurement-debug |
| Operations | monitor, account-admin, change-history |

Two of those are worth calling out because they are not what you would expect from a first-party plugin. measurement-debug diagnoses missing, stale, duplicated, or unattributed Pixel and CAPI events, and change-history gives a timeline of who changed what and when. That is governance tooling shipped by the platform itself.

## **Example Prompts**

What you can usefully ask depends on which route you took, so these are split.

### **Through Spotify's plugin, where campaign operations live:**

"Create a Spotify audio campaign for our sports nutrition brand. Target the workout moment, 18-34, US only, $100 a day. Use our 30-second spot and the product shot as the companion display."

"Set up a podcast ad campaign against business and technology listeners, 30-second mid-roll, $150 a day, 25-45."

The request-builder agent handles the decomposition: looking up geo-targeting identifiers, converting dollar amounts into the micro-units the API expects, validating audience size, then creating the campaign, the ad set with its targeting and budget, and the ad with its creative. It prompts for anything missing rather than guessing.

### **Through a cross-platform MCP, where the comparative questions live:**

"Compare Spotify and TikTok this month. Show CPM and completion rate for each."

"Draft three audio ad scripts and matching companion display images sized for Spotify."

The two routes serve different operating preferences: a hosted cross-platform connection or Spotify's first-party plugin workflow.

## **Spotify Ad Formats**

Useful context, whichever route you take, because format choice drives creative production more than targeting does.

Spotify groups its current formats as follows, per its [ad specs](https://ads.spotify.com/en-US/ad-specs/). Take the exact durations and dimensions from that page for your chosen placement.

|  |  |  |
| :-: | :-: | :-: |
| Group | Formats | Best use case  |
| Audio | Audio ads, plus Canvas as an optional visual loop | Brand awareness and product recall against engaged listening |
| Video | In-stream video, in-feed video | Visual storytelling where the screen is in view |
| Display | In-feed and leaderboard display | Retargeting and promotional messaging |
| Sponsorships | Sponsored Playlist, Homepage Takeover | High-impact brand moments |
| Carousel | Carousel ads | Swipeable multi-card exploration |

The targeting signal worth building around is the listening moment: workout, focus, commute, party. That is a statement about what someone is doing right now rather than an inference about who they are, and it is the thing Spotify has that other platforms do not. Genre, playlist category, and podcast category work alongside it.

## **When Spotify Ads Are Worth the Setup**

**Strong fit:** consumer brands aimed at 18-34 audiences; fitness, health and wellness; food and beverage; music, entertainment and streaming; podcasters promoting their own shows; gaming and mobile app installs.

**Weaker fit:** B2B products and professional services; financial products needing detailed explanation; high-consideration purchases that need a visual demo; any campaign without budget for audio creative production.

That last one decides more Spotify programs than targeting does. Audio creative is a genuinely different production job from resizing a static, and a repurposed video soundtrack tends to sound like one.

## Conclusion

The short version, and it is narrower than the version of this page you may have read in April.

Spotify's official agent access is a CLI plugin package. Our hosted MCP places Spotify reporting, creative work, and supported campaign operations in the same context as your other connected ad platforms. Choose based on the workflow you need, and inspect supported actions before granting write access.

Begin with a reporting request through our [MCP connection](https://syntermedia.ai/mcp), confirm the account and returned data, and configure the required approvals before attempting campaign writes.

[Contact our team](https://syntermedia.ai/contact) to discuss your Spotify campaign workflow.

## **Frequently Asked Questions**

### **Is there an official Spotify Ads MCP server?**

No. Spotify shipped official agent access as a plugin package, ads-agentic-tools, covering Codex, Claude Code, and Antigravity CLI, and its engineering team said they "deliberately avoided MCP for now" because the API surface was too large for static tool definitions. Third-party MCP servers include Spotify, but none of them is Spotify's own.

### **Can I create a Spotify campaign from Claude?**

Yes. Our Spotify integration supports campaign operations, accessed through the applicable tools or scripts with the required account permissions. Spotify's official plugin also supports campaign, ad set, and ad workflows, with publication requiring confirmation.

### **What can Synter MCP do with Spotify?**

Our Spotify integration supports performance reporting, creative work, campaign creation, targeting, budgets, and scheduling. Through MCP, inspect the relevant tools and scripts before execution. This keeps Spotify in the same working context as your other connected ad platforms.

### **Which should I use?**

If Spotify is the campaign you are building and you work in a CLI client, use Spotify's plugin. If Spotify is one line in a media plan and you want it in the same reporting and creative workflow as everything else, use an MCP server that covers all of them. Plenty of teams will use both, since they do different jobs.

### **How does Spotify's targeting differ from other platforms?**

Listening moment is the distinctive signal: workout, focus, sleep, party. It targets activity rather than demographics or inferred interest, which suits products with a natural moment. Genre, playlist category, podcast category, and the usual demographic and geographic filters sit alongside it.