LABSCO SUMMARY
Read-only on an ad platform is a defensible product decision, not a missing feature.
Advertising APIs are where an agent's mistake becomes a spend line. Snapchat shipped analysis without the ability to act, which makes this safe to hand to anyone on the team who needs to understand performance — and useless for the automation people usually want. Know which of those you are after. The admin-approves-then-members-authorise flow is the right shape for an agency too: approval happens once at the organisation, access stays per person.
What it is
Snapchat's endpoint over their Ads API, deliberately read-only: no create, no update, no delete.
What you get
Reviewing campaign setup, analysing performance, and planning delivery — all against live account data, none of it able to modify a campaign.
Requirements
- Sign in from the agent side, pick your organisation, and have an admin approve it
- Each member of the organisation then authorises at the same endpoint
- Agents are pre-registered by client ID; read-only access needs no allowlisting
- Authorisation is revoked from Snapchat's manage-apps page
Setup effort
Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Understanding performance
Analysis against live account data, with no path to change anything.
02
Auditing a campaign's setup
Review how it was configured before it spends more.
03
Handing access to the team
Admin approves the agent once; each member authorises for themselves.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth with a Snapchat business account — an org admin approves the agent, then each member authorises individually
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.snapchat.com/adsRequirements
- OAuth with a Snapchat business account — an org admin approves the agent, then each member authorises individually