drak-mcp

AI assistant access to your marketing platforms, via open-source MCP servers.

What it is

drak-mcp is a set of open-source Model Context Protocol (MCP) servers published by Drak Marketing. They let Claude Desktop, Claude Code, and other MCP-compatible AI assistants securely query and manage marketing platforms on your behalf — Google Ads, Google Analytics 4, Google Search Console, Google Tag Manager, Meta Ads, Bing Ads, and more.

Each MCP runs locally on your own computer. The OAuth credentials you grant stay on your machine. Drak Marketing never sees your tokens or your marketing data.

Who uses it

Internal Drak Marketing staff managing client accounts, plus the teams at our client organizations who want to run reports and workflows through their own AI assistants. The code is open-source under the MIT license — anyone may install and use it independently.

Google APIs and OAuth scopes used

The MCP servers below request specific OAuth scopes from your Google account when you first authorize them. Each scope is scoped to exactly what the MCP needs — no broad Google-wide permissions.

mcp-google-ads

Read campaign, keyword, and search-term performance; create campaigns, ad groups, and ads; manage budgets and bids. Safe by default — all mutations are created PAUSED.

Scopes: https://www.googleapis.com/auth/adwords

npm package →

mcp-ga4

Run standard and realtime reports, list and create custom dimensions and metrics, inspect data streams.

Scopes: https://www.googleapis.com/auth/analytics.readonly

npm package →

mcp-google-gsc

Query Search Console search analytics, list verified sites, inspect URL indexing status.

Scopes: https://www.googleapis.com/auth/webmasters.readonly, https://www.googleapis.com/auth/webmasters

npm package →

neon-one-gtm

List tags, triggers, and variables in Google Tag Manager containers; create GA4 tags; preview and publish container versions.

Scopes: https://www.googleapis.com/auth/tagmanager.readonly, https://www.googleapis.com/auth/tagmanager.edit.containers, https://www.googleapis.com/auth/tagmanager.publish

npm package →

How authorization works

  1. You run the setup command for the MCP you want (e.g. npx mcp-google-ads-auth).
  2. Your browser opens to Google's standard OAuth consent screen. You review the requested scopes and the "drak_mcp" app name, then approve.
  3. Google issues a refresh token scoped to your account. The MCP stores it locally on your own computer under ~/Library/Preferences/ (macOS) or %APPDATA% (Windows).
  4. From that point on, Claude Desktop can query the platform through the MCP. All API calls happen locally between your machine and Google.

How to revoke access

At any time you can revoke the OAuth grant from your Google account at myaccount.google.com/permissions. Look for "drak_mcp" and click "Remove access". You can also delete the local credentials file to clear stored tokens.

Source code

All MCP servers are published open-source under MIT license at github.com/mharnett and on npm. You can audit exactly what the code does before granting OAuth access.

Privacy

Because all data flows stay on your local machine and between your machine and Google, Drak Marketing never receives your marketing data or OAuth tokens. See our full privacy policy for details, including the dedicated section covering drak-mcp OAuth handling.

Contact

Questions about drak-mcp, security concerns, or verification requests? Email mark@drakmarketing.com.