
Snapchat Ads
com.getmcpadsPublished by getmcpads.comv1.0.1Updated Oct 27, 2026
Snapchat Ads MCP server: 21 read tools, 25 opt-in preview-first writes.
Overview
Local stdio MCP server for Snapchat Ads: 21 read tools plus 25 opt-in, preview-first write tools for the ad accounts you select.
- What you can do
- Read campaigns, ad squads, ads, creatives, media, audience segments, lead forms, pixels and mobile apps in the selected ad account
- Read performance insights for an interval with granularity, entity breakdown and delivery pivots
- Inspect targeting configuration, targeting specs and discoverable targeting options such as geo, languages, interests and devices
- Create and update campaigns, ad squads, ads, creatives, segments, creative elements, interaction zones and lead forms
- Rename entities, pause or activate campaigns, ad squads and ads, and manage audience users and lookalikes
- Upload image and video media, including multipart video uploads, and check processing status
- When to use it
- Useful when you want an assistant to report on Snapchat Ads performance and configuration, or to prepare and apply campaign, creative and audience changes from a desktop MCP client, without a hosted intermediary.
- Requirements
- Runs locally over stdio via npm package @getmcpads/snapchat-ads-mcp-server; Node.js 22.23.4, 24.22.1, 26.12.1 or newer on those lines. Needs SNAPCHAT_ADS_ACCOUNT_IDS, plus either SNAPCHAT_ADS_ACCESS_TOKEN or the refresh set SNAPCHAT_ADS_REFRESH_TOKEN, SNAPCHAT_ADS_CLIENT_ID and SNAPCHAT_ADS_CLIENT_SECRET from your own Snap Marketing API OAuth app. Network access to Snap's ads API.
Installation
In SourceWeft
- Open Snapchat Ads in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
[Release] [CI] [License: Apache 2.0] [Node]
Watch the film · What's new · Install · Tool reference · Try hosted getmcpads
[Watch the getmcpads film: every ad account in one conversation with your AI assistant]
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.1: Zod 4 security update · October 26, 2026
- Update
zodto 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix.npm audit --omit=devreports no vulnerability again. - Keep the Zod 3 validation behaviour. A parameter default is still validated and completed before use, so an omitted object must still supply its required fields.
- Keep each parameter's own description when the parameter is optional or has a default. Zod 4 stores a description on the wrapped schema only, so the shared fallback description could otherwise replace it.
- Tool names, parameters and descriptions published over MCP are unchanged.
server-card.jsonis regenerated with Zod 4's JSON Schema output, which spells some constraints differently.
Earlier 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.
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:
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: [email protected].
Development
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: [email protected].
Source: README.md at commit 14f076b
Tools
0Version history
2- v1.0.1LatestOct 26, 2026
- v1.0.0Oct 23, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts