Snapchat Ads MCP and hosted Sume tools in one agent

Yes, an agent can hold both. Snap's Ads MCP server gives it campaign data and, at launch, only read access; Sume's hosted MCP at https://mcp.sume.com/mcp gives it tools that make media. Use the first to decide what to make and the second to make it, as two separate connectors in one session.

Snap details are from its launch post; Sume details from the hosted MCP and tools and gates docs, read 2026-10-01.

What does the Snap Ads MCP server do?

Snap says it connects Snap Ads API data to Claude, ChatGPT and Gemini so you can ask natural-language questions such as which campaigns changed most week over week. You add a connector with the URL https://mcp.snapchat.com/ads, sign in, and an Organization Admin must approve the AI tool, then each user authorizes their own access. At launch all connections are read-only; write access is planned and would be enabled per agent by Admins.

What does the Sume side add?

Sume's remote MCP works over OAuth or an API key. Write and paid tools are hidden until the session has mcp:write or an API key, and every one needs an idempotency_key. An API key gets the full hosted tool set.

What does the loop look like?

Ask the Snap server for last week's changes, write a brief from the answer, then call a Sume create tool with an idempotency_key and wait on the job. For video, the trim flow is video_trim, then jobs_wait, then jobs_result. Preview spend with dry_run=true or max_spend_usd before a burst. Long waits are covered in jobs_wait for long video jobs.

Does Sume read or change my Snap account?

No. Sume only receives what the agent puts in its tool calls. Whatever the Snap connector returns stays in the agent's context, so share only what a creative brief needs.