A side-by-side look at the Hitkeep and Google Tag Manager MCP Server 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 Tag Manager MCP Server for marketing as a local process. You can also run both side by side in one mcpServers block.
GOOGLE_SERVICE_ACCOUNT_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | GOOGLE_SERVICE_ACCOUNT_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 93 | 227 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hitkeep | View Google Tag Manager MCP Server |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Hitkeep yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"stape-io-google-tag-manager-mcp-server": {
"command": "npx",
"args": [
"-y",
"google-tag-manager-mcp-server"
],
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_HERE"
}
}
}
}