Google Ads MCP server
Google Ads in any MCP client, through Memtro: Google Ads does not publish this server. Memtro's Google Ads connector reads Google 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 Google Ads: accounts, campaigns with budgets, campaign performance for a date range, ad groups and ads, and search terms.
Reads
googleads_accountsList the Google Ads accounts the connection can see (id, name, currency, time zone, manager flag).googleads_campaignsCampaigns in an account with status, channel type (SEARCH, PERFORMANCE_MAX, DISPLAY, VIDEO, SHOPPING…), bidding strategy and daily budget.googleads_performanceCampaign performance for a date range (default: last 7 days, ending yesterday): spend, impressions, clicks, CTR, average CPC, conversions…googleads_ad_groupsAd groups in a campaign (or across the account) with status, type and CPC bid; with include_ads, the ads in them (type, status, final URLs…googleads_search_termsSearch terms report: the actual queries that triggered Search ads in a date range (default last 30 days) with impressions, clicks…
Connect it
First connect Google Ads on Dashboard → Connections, then add Memtro to your client once. The Google 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 Google 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
- › How much did we spend on Google Ads last week and what did it convert?
- › Which search terms wasted the most budget this month?
- › List our paused campaigns and their budgets
- › Show the headlines in the Brand Search ad group
Questions
- Is this an official Google Ads MCP server?
- No. It is Memtro's MCP server with Memtro's Google Ads connector behind it: the connector reads Google Ads through its API with the credentials you connect on Dashboard → Connections, and Google 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 Google Ads?
- Not yet. Today every Google 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.