Hitkeep vs Google Ads MCP
A side-by-side look at the Hitkeep and Google Ads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hitkeep for marketing work; choose Google Ads MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hitkeep when
- You need dedicated capabilities in the Marketing domain.
- Its auth model fits you: API key required.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed |
Tools & capabilities
Hitkeep tools
No tool names declared yet. Check the project README from the listing page.
Google Ads MCP 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.
Hitkeep
No confirmed install command for Hitkeep yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}
Frequently asked questions
Hitkeep is categorized under Marketing and uses an install path we have not confirmed yet. Google Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Hitkeep for marketing work and Google Ads MCP 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.
Hitkeep is listed as free. Auth: api key required. Google Ads MCP has no declared pricing — check the project's own site. 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 pascalebeier-hitkeep and google-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hitkeep has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 93 GitHub stars. Google Ads MCP has 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.