Is this an official Meta Ads MCP server?

No. It is Memtro's MCP server with Memtro's Meta Ads connector behind it: the connector reads Meta Ads through its API with the credentials you connect on Dashboard → Connections, and Meta Ads publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Meta Ads?

Not yet. Today every Meta Ads tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Advertising

Meta Ads MCP server

Meta Ads in any MCP client, through Memtro: Meta Ads does not publish this server. Memtro's Meta Ads connector reads Meta Ads through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Facebook and Instagram advertising: ad accounts, campaigns and ad sets, insights (spend, reach, clicks, purchases, leads, ROAS) for a date range, ad creatives and audiences.

Reads

metaads_accountsList the Meta ad accounts the connection can see: id, name, business, currency, status, time zone and lifetime spend.
metaads_campaignsCampaigns in an ad account with status, objective, budgets (daily/lifetime, in account currency), schedule and bid strategy.
metaads_insightsPerformance by campaign (default) or ad set for a date range (default: last 7 days, ending yesterday): spend, impressions, reach, frequency, clicks…
metaads_creativesAds and their creatives in an account (optionally one campaign): headline, primary text, description, call to action, destination link…
metaads_audiencesCustom and lookalike audiences in an account: name, type (CUSTOM, WEBSITE, LOOKALIKE, ENGAGEMENT…), approximate size range…

Connect it

First connect Meta Ads on Dashboard → Connections, then add Memtro to your client once. The Meta Ads tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Meta Ads connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What was our ROAS on Meta last month by campaign?
› Which ad sets are spending the most this week?
› Show the creatives running in the Retargeting campaign
› How big is our website visitors audience?

Questions

Is this an official Meta Ads MCP server?: No. It is Memtro's MCP server with Memtro's Meta Ads connector behind it: the connector reads Meta Ads through its API with the credentials you connect on Dashboard → Connections, and Meta Ads publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Meta Ads?: Not yet. Today every Meta Ads tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.