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, chosen for connecting to accounts you already own.
Six toolkits, three of them official
Stars and licences read on 11 September 2026. What each one connects to, what it can change, and what it needs are on the 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 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.
- 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.
- 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.
- 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.
- 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.
How we chose
The rule, and what it excluded
The rule was: it connects to your own account, and it is read-only or every write is gated by an approval you can see. 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.
One of the six failed half the rule when we measured it. Search Console MCP is described everywhere as read-only; 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. It stays on the shelf because the sixteen read tools are the best Search Console access an agent has today, and its page says exactly which tools to keep away from a careless prompt.
Excluded by the rule: hosted MCP servers that route your account through a vendor’s cloud, a Meta Ads server that exposed unsupervised delete tools, vendor skill packs that only work with that vendor’s paid product, and a dead official CRM server.
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.