Report across campaigns and ad squads
Use normalized reporting at account, campaign, ad-group, and ad levels. Snapchat ad squads map to the ad-group level so your agent can compare the right entities.
Snapchat Ads MCP server
Bring Snap campaign data into your agent with reporting that respects Snapchat’s native metrics. Review spend, swipes, and attributed purchases before planning a budget or delivery change.
Available locally with npm. Set up Snapchat Ads
Built for this platform
Use normalized reporting at account, campaign, ad-group, and ad levels. Snapchat ad squads map to the ad-group level so your agent can compare the right entities.
Read normalized clicks as swipes and conversions as attributed purchases. Reporting dates use the ad account’s timezone, not an arbitrary UTC day boundary.
Inspect an existing daily budget or lifetime cap, then preview the adjustment. Campaign creation is paused by policy and does not imply a complete creative or ad-squad setup.
The integration has synthetic API-contract tests, not a claim of live advertiser validation. Local previews are not server-side validation. Current normalized purchase attribution uses a 28-day swipe and 1-day view window.
Local setup · Bring your own credentials
The npm CLI and MCP server run on your machine. You need Node.js 22.13 or newer, your own provider credentials, and permission to access the ad account.
npm install -g adportadport connect snapchatThe wizard opens Snap authorization and verifies account discovery before saving a grant. Store-backed credentials persist rotated refresh tokens.
adport doctor
adport accounts --provider snapchatCheck that the intended account appears before asking your agent to report on it. Never paste tokens, client secrets, or private keys into chat.
For Claude Code:
claude mcp add --transport stdio adport -- adport mcpFor Cursor, merge this entry into your MCP configuration:
{
"mcpServers": {
"adport": {
"command": "adport",
"args": [
"mcp"
]
}
}
}ChatGPT uses an HTTP MCP endpoint instead of launching this local process.
Your tools. Your choice.
Use the same Adport MCP endpoint and OAuth sign-in in each client. First connect your ad accounts in your Adport workspace. No platform secrets belong in chat.
Enable developer mode, then open Settings → Apps → Create. Choose OAuth and use the endpoint below.
https://app.adport.dev/mcpScan the tools, finish Adport authorization, and enable the new app in your chat.
Developer mode and custom apps must be enabled for your ChatGPT account or workspace. In newer layouts, enable Developer mode under Settings → Security and login, then use the + button in Plugins to create your app. ChatGPT connects over HTTP; the local stdio command is for clients that can launch a process.
Run this command once and complete the browser authorization. Codex stores the MCP configuration and starts OAuth automatically.
codex mcp add adport --url https://app.adport.dev/mcpOnly if authorization did not start or you need to sign in again, run “codex mcp login adport”. Otherwise, check “codex mcp list” and ask Codex to list your ad accounts.
Add Adport at user scope so it is available across your local projects.
claude mcp add --transport http --scope user adport https://app.adport.dev/mcpRun /mcp inside Claude Code if the browser authorization does not open automatically.
Open Customize → Connectors → Add custom connector. Name it Adport and use the endpoint below.
https://app.adport.dev/mcpSelect Connect, approve the workspace, then enable Adport from the + menu in a conversation.
Add this server to ~/.cursor/mcp.json, then restart Cursor.
{
"mcpServers": {
"adport": {
"url": "https://app.adport.dev/mcp"
}
}
}Approve the browser sign-in when prompted. Cursor will keep the OAuth session refreshed.
Open the Command Palette and choose “MCP: Open User Configuration”, then add this server.
{
"servers": {
"adport": {
"type": "http",
"url": "https://app.adport.dev/mcp"
}
}
}Start the Adport server from VS Code and complete the browser authorization.
Use the MCP URL from Agent access if you run your own Adport deployment. Client settings, workspace permissions, and advertising-platform approvals still apply. The Cloud waitlist below is separate from these connection instructions.
You stay in control
The first mutation call returns a preview and a short-lived pending-operation token. Applying requires that token and the same arguments. Budget caps and protected accounts are checked by the policy engine; new campaigns are paused by policy.
Local operations are recorded in an append-only audit log. An approved preview is not a guarantee of provider acceptance, and a connected agent does not grant additional account permissions.
Snap’s native swipe metric is mapped to normalized clicks. It is not identical to every other platform’s click definition. Keep that distinction visible in cross-platform comparisons.
Yes. Install Adport from npm, connect your own Snapchat Ads credentials, and register the local MCP server with a stdio-compatible agent such as Claude Code or Cursor. Your provider may have its own approval, access, or billing requirements.
Account discovery, reporting, and mutations can require different permissions. Check the requested account, provider app scopes, advertiser eligibility, and environment. Start with adport doctor and the connection guide above. Do not bypass a denied operation by sharing secrets with the agent.
Adport Cloud · Coming next
Join the waitlist for the cloud version. We’ll email you when early access opens.