What is the key difference between Seo Performance MCP and Google Search Console MCP?

Seo Performance MCP belongs to the Marketing category with local stdio execution, while Google Search Console MCP belongs to the Marketing category with local stdio execution.

How do I install Seo Performance MCP or Google Search Console MCP 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 Search Console MCP free or paid?

Seo Performance MCP operates under a Free / Open Source model (No auth required). Google Search Console MCP 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 Search Console MCP lists 17 tools with 2 views and 8 GitHub stars.

Can I use both Seo Performance MCP and Google Search Console MCP 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 Search Console MCP

In-depth architectural comparison of the Seo Performance MCP and Google Search Console MCP 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: 43/100 (Fair) | Auth: No auth required

Google Search Console MCP

Marketing · Local stdio

Quality: 64/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 Search Console MCP 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 Search Console MCP 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: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
Primary tools included: gsc_sites, gsc_site_details, gsc_query.

Feature & Specification Comparison

Specification	Seo Performance MCP AutomateLab-tech Marketing	Google Search Console MCP acamolese Marketing
Summary	Post-publish SEO performance MCP that unifies Google Search Console, Matomo, GA4, Clarity, and AI-citation signals per URL and emits a verdict (refresh / expand / merge / kill / doubledown / hold) per post with reason codes.	Google Search Console MCP server: query performance data, inspect URLs, check indexing, and generate brandable HTML SEO audit reports with a 30/60/90-day roadmap. Read-only OAuth scope, installable via uvx mcp-google-search-console.
Category & Scope

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

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 Search Console MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "acamolese-google-search-console-mcp": {
      "command": "uvx",
      "args": [
        "mcp-google-search-console"
      ],
      "env": {
        "GSC_CLIENT_ID": "YOUR_GSC_CLIENT_ID_HERE",
        "GSC_CLIENT_SECRET": "YOUR_GSC_CLIENT_SECRET_HERE",
        "GSC_REFRESH_TOKEN": "YOUR_GSC_REFRESH_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Seo Performance MCP More alternatives to Google Search Console MCP Marketing category hub Canonical compare URL