Connect Snapchat Ads to Claude and Claude Code
To connect Snapchat Ads to Claude Code, connect your Snap advertising account to Adport, then register Adport as an MCP server. Claude can request campaign and ad-squad reports through that connection. A useful review keeps Snap-specific concepts such as swipes, attributed purchases, and the account timezone visible.
Prepare Snap Business and API access
The local integration needs a Snap Business organization, permission for the advertising account, and your own OAuth app. Configure the exact callback http://127.0.0.1:53684/callback for the local wizard. Supply the app client ID and client secret through the connection setup rather than a Claude prompt.
Check the Snapchat integration prerequisites before starting. OAuth app access and ad-account permissions are separate requirements. Adport is an independent integration with the Snap Marketing API; installing its package does not imply that Snap has approved your application or advertiser for every operation.
Connect Snapchat Ads to Claude Code locally
With Node.js 22.13 or newer installed, run the wizard and verify that the intended account is returned:
npm install -g adport
adport connect snapchat
adport doctor
adport accounts --provider snapchatThe wizard opens Snap authorization and checks account discovery before saving the grant. Confirm the returned account against the one you use in Ads Manager. Then register the local MCP process:
claude mcp add --transport stdio adport -- adport mcpOpen Claude Code and inspect /mcp to confirm the server is connected. Claude Code documents local stdio servers. If the process is unavailable, check that the Adport command is installed on the PATH visible to Claude Code. A configured server without accessible Snap accounts still needs the provider connection fixed.
Use the hosted connector when available
If Snapchat is available in your Adport Cloud workspace, connect it there, save the selected ad accounts, and enable agent access. Add the hosted endpoint to Claude Code with the shared setup command:
claude mcp add --transport http --scope user adport https://app.adport.dev/mcpComplete browser authorization for the intended project. In Claude web or desktop, follow the hosted connector instructions on Adport's AI assistants page. The hosted setup uses Adport sign-in; the local setup uses your own Snap application. Hosted provider availability depends on rollout and app approval, so use the documented local path when your workspace does not offer Snapchat.
Ask for campaigns and ad squads
Use Adport to list the connected Snapchat ad accounts. For the account I select, report campaign and ad-squad spend, swipes, and attributed purchases for the last seven completed account-local days. Show the timezone, currency, and attribution definitions available from the connector. Do not change anything.
Snapchat ad squads map to Adport's ad-group reporting level. Normalized clicks represent swipes, and normalized conversions represent attributed purchases. Keep those labels in your analysis when comparing Snapchat with another platform's click or conversion totals.
The connector requests purchase attribution with a 28-day swipe window and a 1-day view window. Reporting dates follow the ad account's timezone. Match these assumptions before comparing a report with a dashboard export. A difference in attribution windows is a reason to reconcile definitions before drawing a budget conclusion.
Review a campaign budget proposal
Inspect the campaign's existing daily budget or lifetime cap before asking for an adjustment. Give Claude the exact account and campaign ID, the amount, and the intended budget scope. Ask for a preview and read its proposed budget effect in the account's currency.
Snapchat previews in this connector are local plans, not Snap server validation. Applying still needs a matching pending operation and the same arguments. The platform may reject the operation if your grant or campaign is ineligible. After an approved change, request the campaign again and check the value the platform accepted.
A newly created campaign is paused by policy. It does not include a complete creative and ad-squad setup by implication. Inspect those components before requesting a separate activation.
Turn the first report into a useful comparison
Choose ad squads with comparable objectives and enough purchase data to support the decision. Ask Claude to identify where missing purchase values prevent a ROAS comparison, and keep spend-only observations separate from evidence of acquisition efficiency.
Snap documents campaigns, ad squads, reporting, and authorization in its Marketing API reference. The Snapchat Ads MCP page lists Adport's supported operations. For a second platform, follow the Meta Ads guide or TikTok Ads guide and preserve their reporting differences.
Sources & further reading
Provider documentation for the setup and platform behavior described above.
- Claude Code: connect tools with MCPcode.claude.com
- Snap Marketing APIdevelopers.snap.com