RankControl vs Google Tag Manager MCP Server
A side-by-side look at the RankControl 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 RankControl 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 RankControl when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
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 | 56/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Paid service | Free |
| Required env vars | None listed | GOOGLE_SERVICE_ACCOUNT_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 236 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View RankControl | View Google Tag Manager MCP Server |
Tools & capabilities
RankControl 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.
RankControl
{
"mcpServers": {
"rankcontrol": {
"command": "npx",
"args": [
"-y",
"rankcontrol"
]
}
}
}
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
RankControl 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 RankControl 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.
RankControl is listed as a paid service. Auth: oauth 2.0. 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 rankcontrol 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, RankControl has a quality signal of 56/100 (Good) with 3 views, 0 installs and 5 GitHub stars. Google Tag Manager MCP Server has 61/100 (Good) with 5 views, 0 installs and 236 GitHub stars.