Google Search Console MCP vs Citedy Seo Agent

In-depth architectural comparison of the Google Search Console MCP and Citedy Seo Agent 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.

Which MCP Server Should You Choose?

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.

Explore Google Search Console MCP Details

Choose Citedy Seo Agent when:

• You need dedicated capabilities in the Marketing domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• You have access to required keys: CITEDY_API_KEY.
• Primary tools included: Auto-publish articles and adaptations to LinkedIn, X, Facebook, Reddit, Instagram, YouTube Shorts,…, Deep SEO scanning with AI-powered recommendations, Generate AI illustrations and voice-over narrations for articles.

Feature & Specification Comparison

Specification	Google Search Console MCP acamolese Marketing	Citedy Seo Agent Citedy Marketing
Summary	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.	Full-stack AI marketing toolkit with 41 MCP tools. Scout X/Reddit trends, analyze competitors, find content gaps, generate SEO articles in 55 languages with AI illustrations and voice-over, create social adaptations for 9 platforms, generate AI avatar videos with subtitles, ingest any URL (YouTube, PDF, audio), create lead magnets, and run content autopilot.
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "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"
      }
    }
  }
}

{
  "mcpServers": {
    "citedy-citedy-seo-agent": {
      "command": "npx",
      "args": [
        "-y",
        "openskills"
      ],
      "env": {
        "CITEDY_API_KEY": "YOUR_CITEDY_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons