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

Seo Performance 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 Performance 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 Performance MCP and Google Tag Manager MCP Server free or paid?

Seo Performance MCP operates under a Free / Open Source model (No auth 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 Performance MCP lists 9 tools with 3 views and 2 GitHub stars. Google Tag Manager MCP Server lists 6 tools with 2 views and 223 GitHub stars.

Can I use both Seo Performance 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 Performance MCP vs Google Tag Manager MCP Server

In-depth architectural comparison of the Seo Performance 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 Performance MCP

Marketing · Local stdio

Quality: 59/100 (Good) | Auth: No auth required

Google Tag Manager MCP Server

Marketing · Local stdio

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

Verdict Summary: Choose Seo Performance 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 Performance MCP when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: posts_list, posts_snapshot, posts_decay_curve.

Explore Seo Performance 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_SERVICE_ACCOUNT_KEY.
Primary tools included: 18 Google Tag Manager MCP tools, Hosted remote HTTP server, Built-in Google OAuth for hosted use.

Feature & Specification Comparison

Specification	Seo Performance MCP AutomateLab-tech Marketing	Google Tag Manager MCP Server stape-io Marketing
Summary
Category & Scope	Marketing	Marketing

Tools & Capabilities Breakdown

Seo Performance MCP Tools (9)

posts_list

Discover posts via an XML sitemap (POSTS_SITEMAP_URL or the sitemap_url arg), a JSON override list (POSTS_LIST), or - if configured - the Ghost Admin API. Pass an explicit urls[] to skip discovery entirely. Returns metadata: url, title, published_at, age_days, tags. Filter by minimum age or published-after date. When to use: discover which URLs are eligible for snapshot / verdict / cohort analysis. Works with any CMS that exposes a sitemap.

posts_snapshot

Pull a 30/60/90-day snapshot across every configured signal source for one post: GSC clicks/impressions/CTR/position + top queries, Matomo visits + dwell, GA4 pageviews, Clarity scroll/rage clicks, AI-citation counts. Each source is best-effort: if its env vars are missing the field is omitted. Returns whatever is available. Read-only. No third-party writes. Optionally persists to the local DuckDB cache when persist=true.

posts_decay_curve

Bucket GSC clicks/impressions/avg-position into ~weekly windows for the last N weeks (default 12) and classify the trend: decay / plateau / growth. Underpins the verdict engine's decay rules. Read-only GSC query.

posts_verdict

Run the rule-based verdict engine on a single post: combine snapshot + decay curve and emit a verdict with reason codes and a 0-1 confidence score. Reason codes are deterministic. The mapping reasons -> verdict lives in src/verdict/rules.ts and can be inspected. Reporting only - does NOT mutate anything. To act on the verdict, hand the brief to a writer or to an AI rewrite tool.

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 Performance MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "automatelab-tech-seo-performance-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/seo-performance-mcp"
      ]
    }
  }
}

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_SERVICE_ACCOUNT_KEY": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Seo Performance 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 Performance MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.

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