Kive vs Google Tag Manager MCP Server
A side-by-side look at the Kive 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 Kive 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.
Which MCP server should you choose?
Choose Google Tag Manager MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_SERVICE_ACCOUNT_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Kive | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | None listed | GOOGLE_SERVICE_ACCOUNT_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 236 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Kive | View Google Tag Manager MCP Server |
Tools & capabilities
Kive tools
No tool names declared yet. Check the project README from the listing page.
Google Tag Manager MCP Server 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.
Kive
No confirmed install command for Kive yet — follow the setup steps linked from its listing page rather than a guessed package name.
Google Tag Manager MCP Server
{
"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"
}
}
}
}