LinkBit MCP vs Google Tag Manager MCP Server
A side-by-side look at the LinkBit MCP 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 LinkBit MCP for marketing work as a local process; 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 LinkBit MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APP_URL, API_KEY. - You want tools like
shorten_url, shorten_urls, list_links.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 77/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | APP_URLAPI_KEY | GOOGLE_SERVICE_ACCOUNT_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 0 | 231 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View LinkBit MCP | View Google Tag Manager MCP Server |
Tools & capabilities
LinkBit MCP tools 9
shorten_urlExisting `utm_*` on the URL are not overwritten; `#fragment` is keptshorten_urlsBulk createlist_linksNewest firstupdate_linkPATCHdisable_linkStops redirects. `destructiveHint: truedelete_linkPermanent. `destructiveHint: trueget_qrsvg, `color`, `logo`, `printget_link_statsCountries, devices, referrers, dailyget_analyticsAccount overview
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.
LinkBit MCP
{
"mcpServers": {
"linkbit-mcp": {
"command": "npx",
"args": [
"-y",
"linkbit-mcp"
],
"env": {
"APP_URL": "YOUR_APP_URL_HERE",
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
LinkBit MCP is categorized under Marketing and uses a local stdio subprocess. Google Tag Manager MCP Server belongs to Marketing and uses a local stdio subprocess. Pick LinkBit MCP for marketing work and Google Tag Manager MCP Server 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.
LinkBit MCP has no declared pricing — check the project's own site. Google Tag Manager MCP Server is listed as free. Auth: oauth 2.0. 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 linkbit-mcp and stape-io-google-tag-manager-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LinkBit MCP has a quality signal of 77/100 (Great) with 1 views, 0 installs and 0 GitHub stars. Google Tag Manager MCP Server has 61/100 (Good) with 4 views, 0 installs and 231 GitHub stars.