What is the key difference between Seo Tools MCP and Google Tag Manager MCP Server?

Seo Tools MCP belongs to the Marketing category with local stdio execution, while Google Tag Manager MCP Server belongs to the Marketing category with local stdio execution.

How do I install Seo Tools MCP or Google Tag Manager MCP Server in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Seo Tools MCP and Google Tag Manager MCP Server free or paid?

Seo Tools MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Google Tag Manager MCP Server operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Seo Tools MCP lists 11 tools with 5 views and 3 GitHub stars. Google Tag Manager MCP Server lists 5 tools with 2 views and 212 GitHub stars.

Can I use both Seo Tools MCP and Google Tag Manager MCP Server together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Seo Tools MCP vs Google Tag Manager MCP Server

In-depth architectural comparison of the Seo Tools MCP and Google Tag Manager MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Seo Tools MCP

Marketing · Local stdio

Quality: 65/100 (Great) | Auth: API Key required

Google Tag Manager MCP Server

Marketing · Local stdio

Quality: 60/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Seo Tools MCP if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Seo Tools MCP when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Primary tools included: xmlstock_auth_status, xmlstock_set_credentials, xmlstock_serp.

Explore Seo Tools MCP Details

Choose Google Tag Manager MCP Server when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY, WORKER_HOST, HOSTED_DOMAIN.
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.

Feature & Specification Comparison

Specification	Seo Tools MCP antohins Marketing	Google Tag Manager MCP Server stape-io Marketing
Summary	Five read-only SEO servers for the Google/Yandex (RU/CIS) market: SERP (XMLStock), Yandex Wordstat, Google Search Console (Search Analytics + URL Inspection), Yandex.Webmaster, and Yandex.Metrica. 38 tools, multi-account, OAuth with auto-refresh. Install: npx -y seo-tools-mcp-.	This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Category & Scope

Tools & Capabilities Breakdown

Seo Tools MCP Tools (11)

xmlstock_auth_status

Статус авторизации xmlstock: какие ключи заданы (маскированно), каких не хватает, как их получить. ВЫЗЫВАТЬ ПЕРВЫМ в начале работы с xmlstock. Если чего-то нет — запросить значения у пользователя и сохранить через xmlstock_set_credentials.

xmlstock_set_credentials

Сохранить ключи xmlstock в /home/user/.config/seo-tools-mcp/.env (права 600) и применить сразу, без перезапуска сервера. Передавать только обновляемые поля. account — сохранить в именованный профиль (мультиаккаунт). Значения даёт пользователь; в ответе они маскируются.

xmlstock_serp

Слепок выдачи Google/Yandex через XMLStock (ПЛАТНО за запрос). Возвращает { found, truncated (true = выдача кончилась раньше запрошенного depth), count, results: [{ position, url, title, snippet, text_bolds (подсветки hlword) }], serp_features: { featured_snippet, paa (только Google), related, sitelinks_top1, packs } }. Пустая выдача (код 15) ТАРИФИЦИРУЕТСЯ и помечается { results: [], empty: true, note }. depth>10 добирается пагинацией (каждая страница — отдельный платный запрос; у yandex_xml — до 100/страница). region: ОДИН регион (название или числовой id Яндекса) — работает для ВСЕХ движков. ОГРАНИЧЕНИЕ ИСТОЧНИКА: device=mobile отдаёт только позиции и сниппеты — без hlword/PAA/related; подсветки и SERP-фичи снимать с desktop. engine=yandex_xml — ОФИЦИАЛЬНЫЙ Яндекс XML (легальный API, тариф дороже: от 24 ₽/1000): groupby до 100 работает — до 100 результатов за ОДИН платный запрос (depth до 1000), hlword-подсветки на любых устройствах, статистика «найдено»: found (по запросу), found_docs (документов), found_human (строкой); в results доп. поля id/modtime/saved_copy_url/is_local. Отличие от yandex (live): SERP-фичей/packs нет — чистая органика; device/searchDomain/lang/l10n/period/exactQuery/includeAds/includeSimilar не применимы; safeSearch маппится в filter (strict/moderate/none).

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Seo Tools MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "antohins-seo-tools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-xmlstock"
      ]
    }
  }
}

Google Tag Manager MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "stape-io-google-tag-manager-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "google-tag-manager-mcp-server"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "COOKIE_ENCRYPTION_KEY": "YOUR_COOKIE_ENCRYPTION_KEY_HERE",
        "WORKER_HOST": "YOUR_WORKER_HOST_HERE",
        "HOSTED_DOMAIN": "YOUR_HOSTED_DOMAIN_HERE"
      }
    }
  }
}

Frequently Asked Questions

Seo Tools MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Seo Tools MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.

More alternatives to Seo Tools MCP More alternatives to Google Tag Manager MCP Server Marketing category hub