Google Ads MCP vs Hitkeep
A side-by-side look at the Google Ads MCP and Hitkeep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Ads MCP for marketing work as a local process; choose Hitkeep for marketing. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_LOGIN_CUSTOMER_ID, GOOGLE_ADS_REDIRECT_URI, GOOGLE_ADS_PRIVACY_MODE, GOOGLE_ADS_ALLOW_MUTATIONS, GOOGLE_ADS_TOKEN_PATH.
Choose Hitkeep when
- You need dedicated capabilities in the Marketing domain.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 41/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | GOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_ID |
Tools & capabilities
Google Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
Hitkeep tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Ads MCP
{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_GOOGLE_ADS_DEVELOPER_TOKEN_HERE",
"GOOGLE_ADS_CLIENT_ID": "YOUR_GOOGLE_ADS_CLIENT_ID_HERE",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_GOOGLE_ADS_CLIENT_SECRET_HERE",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID_HERE",
"GOOGLE_ADS_REDIRECT_URI": "YOUR_GOOGLE_ADS_REDIRECT_URI_HERE",
"GOOGLE_ADS_PRIVACY_MODE": "YOUR_GOOGLE_ADS_PRIVACY_MODE_HERE",
"GOOGLE_ADS_ALLOW_MUTATIONS": "YOUR_GOOGLE_ADS_ALLOW_MUTATIONS_HERE",
"GOOGLE_ADS_TOKEN_PATH": "YOUR_GOOGLE_ADS_TOKEN_PATH_HERE"
}
}
}
}
Hitkeep
No confirmed install command for Hitkeep yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Google Ads MCP is categorized under Marketing and uses a local stdio subprocess. Hitkeep belongs to Marketing and uses an install path we have not confirmed yet. Pick Google Ads MCP for marketing work and Hitkeep for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Hitkeep has no confirmed install command yet — follow its own setup instructions.
Google Ads MCP has no declared pricing — check the project's own site. Hitkeep is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-ads-mcp and pascalebeier-hitkeep as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Ads MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars. Hitkeep has 49/100 (Fair) with 2 views, 0 installs and 93 GitHub stars.