Snapchat Ads

Snapchat Ads MCP server

Bring your Snapchat Ads accounts into your MCP client.

Read campaigns and performance, and prepare changes for the ad accounts you select.

Watch the film · What's new · Install · Tool reference · Try hosted getmcpads

Play the 45-second film

The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.

21 read tools · 25 write tools, disabled by default.

Run locally with your own Snap Marketing API credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to Snap. For managed connections, including supported ChatGPT setups, use the hosted option.

What's new

v1.0.0: First standalone release · October 23, 2026

• First standalone server, ported from the getmcpads gateway at revision 3e1c2c8: 21 native read tools, 25 native write tools and the snapchat://guide and snapchat://reporting-fields resources.
• Require SNAPCHAT_ADS_ACCOUNT_IDS and check every request and every referenced entity against the selected ad account.
• Keep writes off unless SNAPCHAT_ADS_ENABLE_WRITES is exactly true. Every write previews until confirm: true, and campaigns, ad squads and ads are created paused.
• Renew the access token in memory from the refresh credentials, without writing it anywhere, and redact credentials from every error.
• Reach only adsapi.snapchat.com and accounts.snapchat.com, with no redirect followed, timeouts and a 16 MB response bound.
• Report HTTP 200 replies that carry a failed request or failed items as errors, and an explicit single-create rejection as not applied.
• Leave out the hosted frozen-file uploads, creative gallery UI, alerts and Launcher.
• Require Node.js 22.23.4, 24.22.1, 26.12.1 or newer in those lines, warn on stderr otherwise, and test Node 22, 24 and 26 in CI.

Full changelog · All releases

Source synchronization: SOURCE_SYNC.md.

Upgrade notes

Requires Node.js 22.23.4, 24.22.1, 26.12.1 or a newer release of those lines. These releases carry the October 2026 security fixes, and the server prints a warning on stderr when it runs on an older one. CI covers Node 22, 24 and 26. Writes remain optional and require explicit confirmation. Hosted creative integrations and MCP Apps UI are outside this release.

Install this release

This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.

git clone --branch v1.0.0 --depth 1 https://github.com/get-mcp-ads/snapchat-ads-mcp-server.git
cd snapchat-ads-mcp-server
npm ci
npm run build

Configure your MCP client to run node with the absolute path to dist/cli.js and the environment variables documented below.

Managed connection. Use Snapchat Ads with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.

Configuration

Provide these environment variables through the client's secret configuration:

Set either SNAPCHAT_ADS_ACCESS_TOKEN or the three refresh variables together. The server validates the configuration at startup and names the variable to fix, without repeating any value.

To obtain credentials, create an OAuth app for the Snap Marketing API, authorize it once with the snapchat-marketing-api scope, and exchange the authorization code for a refresh token, as described in Snap's authentication guide. This package does not run an OAuth browser flow. It keeps renewed tokens in memory only, so a restart begins again from the refresh token you configured.

Example client entry, once the package is on npm:

{
  "mcpServers": {
    "snapchat-ads": {
      "command": "npx",
      "args": ["-y", "@getmcpads/snapchat-ads-mcp-server"],
      "env": {
        "SNAPCHAT_ADS_ACCOUNT_IDS": "your-ad-account-uuid",
        "SNAPCHAT_ADS_REFRESH_TOKEN": "your-refresh-token",
        "SNAPCHAT_ADS_CLIENT_ID": "your-client-id",
        "SNAPCHAT_ADS_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

npm run doctor reports which variables are present, never their values, and whether your Node.js release carries the October 2026 security fixes.

Safety and coverage

Writes preview by default. Review the exact account, target and parameters before repeating the call with confirm: true. Campaigns, ad squads and ads are created paused. Activation through snapchat_update_status can spend advertising budget, and its preview says so. A write whose outcome is uncertain is never retried. A timeout, a network failure, a server error or an unreadable reply after a write is reported as unknown: read the entity and reconcile it first. A successful write is followed by an account-scoped readback, and the receipt is kept even when that readback fails. Before any write, the parent and every referenced pixel, app, audience, media, creative and lead form are read and checked against the selected ad account. Unknown arguments are rejected. Snap can answer HTTP 200 with a failed request_status or failed items. Both are reported as errors. An explicit single-create validation rejection is reported with applied: false. Monetary fields ending in _micro, spend and monetary conversion values are micro currency: 1,000,000 equals one unit of the account currency. List tools return next_cursor for the next page, and insights flag partial: true when Snap returned another page. Snap documents about 20 requests per second per app and 10 per second per access token. An HTTP 429 is reported with an instruction to wait.

Requests go only to adsapi.snapchat.com and to accounts.snapchat.com for token renewal. No request follows a redirect, every request has a timeout, and replies are capped at 16 MB. Media links that Snap returns are passed through as data and never downloaded. Tokens are redacted from every error.

Uploads take base64 bytes: 5 MB per image and 10 MiB per direct video, or up to 256 MiB of video through the multipart tools in parts of 8 MiB. Follow every upload with snapchat_get_media_status until ready is true. The gateway's four frozen-file upload tools read files from the hosted Launcher storage, so they are not part of this server. The gateway's native upload takes bytes and fetches no URL, so this server adds no local-file or URL upload either.

This server exposes a reviewed subset of the Snap Marketing API. Use tools/list or server-card.json for exact schemas, the snapchat://guide and snapchat://reporting-fields resources for units and curated reporting fields, and the official API reference for provider details.

Snap's official Ads MCP server

Snap documents its own Snapchat Ads MCP server. The comparison below uses only Snap's introduction and connection guide, read on October 23, 2026.

Hosted option

getmcpads for Snapchat Ads manages the hosted connection and account selection. Hosted and source releases can differ. Contact: hello@getmcpads.com.

Development

npm run typecheck
npm run lint
npm run build
npm test
npm run catalog

All tests run offline with synthetic responses and a mocked fetch. No live account is read or changed.

Tools

Every tool is listed below. See server-card.json for complete parameter and output schemas. An ad squad is Snap's ad group.

21 read tools

25 write tools

Disabled by default. Calls preview unless explicitly confirmed. Check the configuration and exact schema before use.

Resources

License

Apache License 2.0. See NOTICE.

More from getmcpads

Meta Ads · Google Ads · Google Analytics 4 · Google Search Console · TikTok Ads · Pinterest Ads · X Ads

Maintained by Emmanuel at getmcpads. Questions: hello@getmcpads.com.