MCP server · Snapchat

Snapchat Ads MCP Server

Snap ships a first-party, hosted, remote MCP server for the Snapchat Ads API. A supported agent POSTs directly to https://mcp.snapchat.com/ads over streamable HTTP and authenticates with OAuth 2.0 (authorization code + PKCE S256, public client, scope snapads.read). The current release is READ-ONLY — an agent can read authorized Snapchat Ads data but cannot create, update, or delete; Snap says write access is planned. Onboarding is self-serve: an organization Admin or Business Admin approves each agent once during sign-in, then every member authorizes their own access, and a member only ever reaches the organizations and ad accounts their existing Ads permissions already allow.

Open docs → Snapchat provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Snapchat Type: Documentation link Transport: streamable-http Host: developers.snap.com

Documentation

https://developers.snap.com/marketing-api/Ads-MCP/Introduction.md

Documentation link · transport streamable-http

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.