Do I need a Meta developer app for the ads MCP server?

No, not to use it: Meta's Get started page says owning a Meta app is not a prerequisite for the ads MCP server, and sends you to its help article on setting up Meta ads AI connectors for that route. You need your own Meta developer app when you connect an AI application you build, which Meta opened to any developer on July 16, 2026.

Everything about Meta comes from its Get started page, its July 16 developer post and its AI connectors announcement, read 2026-09-29. Sume is not part of Meta's flow; the last section compares how Sume's own hosted MCP signs you in, from OAuth and API keys.

How do I connect with my own Meta app?

Meta's steps for this integration method are to create or open an app at developers.facebook.com/apps and add the **Create & manage ads with ads MCP server** use case. The July post adds a step for agencies and partners: if you manage data for other businesses, you submit the app for review and request Advanced Access on the ads_mcp_management permission.

Then choose how to authenticate. Meta describes two methods.

Which permissions does the access token need?

When you request a user access token, Meta's page lists these permissions to grant:

• ads_mcp_management
• ads_read
• ads_management
• catalog_management
• business_management
• pages_show_list
• instagram_basic

curl -i -X POST "https://mcp.facebook.com/ads" \
  -H "Authorization: Bearer $META_ACCESS_TOKEN" \
  --data-raw '{"jsonrpc":"2.0","method":"tools/list","id":1}'

Is the ads MCP server generally available?

Meta's April 29, 2026 announcement introduced the Meta ads AI connectors, which include the MCP server and an ads command line interface, as an open beta. Meta's July post says it is gradually rolling out access to tools available to ad accounts through this integration method, and suggests asking your agent what tools it has access to.

How does Sume's own MCP sign-in compare?

It is a different product with its own rules. Sume's hosted MCP endpoint is https://mcp.sume.com/mcp. Its OAuth grants read-only access by default; turning Write on at consent adds mcp:write. Automation that does not speak OAuth can send an API key as a Bearer or x-api-key header, and an API-key session sees the write and paid tools.

Keep both secrets out of chat and client code. The Sume quickstart says not to paste API keys into chat and to prefer the OAuth connector flow for interactive clients. For the ways an agent can reach Sume, see Give my agent video generation: three routes.