TOOLKITS

Toolkits: what lets an agent reach your accounts

Skills tell an agent how to think; these give it something to read. Six MCP servers and plugins that connect to Google Analytics, Google Ads, Search Console, a browser and two marketing operating systems.

Six toolkits, three of them official

Stars and licences as of 11 September 2026. What each one connects to, what it can change, and what it needs are on its page.

Google Analytics MCP officialGoogle’s own MCP server for GA4: seven read-only tools over the Admin and Data APIs, so an agent can run reports on your property without a CSV export.Google read-only (analytics.readonly scope)
Google Ads MCP officialGoogle’s official MCP server for the Google Ads API: three query tools and four reference resources, gated by a developer token and OAuth, with a YAML file to switch tools off.Google query only (GAQL search); no mutate service exposed
claude-adsA Claude Code plugin for paid-media operations across twelve ad platforms: read-only by default, drafts changes it does not apply, and requires six gates before any live mutation.Daniel Agrici read-only by default; writes only through the six-gate approval path; no permanent deletion
Digital Marketing ProAn open-source marketing operating system as a plugin: 163 skills, 24 agents, a 12-part engagement flow, eight HTTP connectors that fire real API calls behind a typed approval gate, and an empty .mcp.json you fill yourself.Indranil Banerjee plan-only for most skills; execution skills are approval-gated
Search Console MCPGoogle Search Console, Bing Webmaster Tools, GA4 and AdSense behind one MCP server: 21 tools, of which 16 read and 5 change your property. Set up with one npx command and an OAuth window.Saurabh Sharma 16 read tools; 5 write tools (add or delete a site, submit or delete a sitemap, submit or remove URLs) with no approval gate
Playwright MCP officialMicrosoft’s official browser server for agents: 71 tools over a real Chromium, driven by the accessibility tree rather than screenshots, so an SEO skill can render a page the way a crawler cannot.Microsoft full browser control; read-only is a matter of what you ask

Before you connect one

What every toolkit here has in common, and which ones write

Five of the six connect to an account you own; Playwright drives a browser and needs none. Three of the six are official (two from Google, one from Microsoft); the other three are community projects with public code, an MIT licence and a documented safety model. Each page says what the toolkit reads, what it can change, and what it needs before you connect it.

Four of the six can change something. claude-ads writes only through an approval path you see; Digital Marketing Pro’s execution skills are approval-gated; Playwright drives a real browser and does whatever you ask of it. Search Console MCP is the one to read carefully: it is described almost everywhere as read-only, yet five of its twenty-one tools add or delete a site, submit or delete a sitemap, or submit and remove URLs, with no confirmation step in the server. Its page names the five to keep away from a careless prompt.

Questions

Questions people ask before installing

Do I need a toolkit to use the skills?

No. Every skill on this site runs without one. A toolkit turns "paste me your export" into "read my account".

Which one first?

Google Analytics MCP if you want an agent to answer questions about traffic; Google Ads MCP if you run Google Ads; Playwright MCP if a skill you use needs to render pages.

Where do the credentials live?

On your machine: environment variables, a credentials file you point at, or the OS keychain. None of the six stores them in the repository, and their READMEs say so.