Search Console MCP vs X402 API

A side-by-side look at the Search Console MCP and X402 API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Search Console MCP logoSearch Console MCPMarketing · Local subprocess (stdio)An MCP server to interact with Google Search Console and Bing Webmasters.71GreatAuth: oauth 2.0X402 API logoX402 APIMarketing · Local subprocess (stdio)AI API for marketing, content and outreach. 22 endpoints. Pay with USDC on Base via x402.33EmergingAuth: not declared

Verdict: choose Search Console MCP for marketing work as a local process; choose X402 API for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Search Console MCP logoChoose Search Console MCP 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 want tools like get_started, sites_list, sites_manage.
Explore Search Console MCP

X402 API logoChoose X402 API when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
Explore X402 API

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSearch Console MCP logoSearch Console MCPX402 API logoX402 API
CategoryMarketingMarketing
Quality signal71/100 · Great33/100 · Emerging
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthOAuth 2.0Not declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3060
Directory activity 4 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools25Not listed

Tools & capabilities

Search Console MCP tools 25

  • get_startedStart here. Returns a complete map of this server's capabilities, active platforms, and recommended workflows. Call this once at the beginning of any session.
  • sites_listList verified web properties across Google Search Console, Bing Webmaster Tools, or GA4.
  • sites_manageAdd or delete a web property from Google Search Console or Bing Webmaster Tools.
  • accounts_manageManage Google Search Console service accounts and site permissions.
  • sitemaps_listList submitted XML sitemaps and status for a site.
  • sitemaps_submitSubmit a new XML sitemap to Google Search Console and/or Bing Webmaster Tools.
  • sitemaps_deleteDelete a sitemap from Google Search Console or Bing Webmaster Tools.
  • analytics_queryUnified search performance query replacing single-dimension tools. Supports queries, pages, countries, devices, and search appearances.
  • analytics_comparePeriod-over-period search performance comparisons, trends, and traffic drop attributions.
  • analytics_anomaliesDetect search traffic anomalies across Google and Bing.
  • analytics_advancedGoogle Analytics 4 (GA4) e-commerce, realtime metrics, user behavior, and conversion funnels.
  • genai_query_insightsDetect likely generative-AI / AI-Mode / conversational fanout queries across Google and Bing. Because neither search engine exposes generative-AI citation data via its public API yet, this matches heuristic patterns (prompt verbs, follow-ups, conversational phrasing) on regular query-level performance data; it is an undercount, not an official report.
  • +13 more on the listing page

X402 API 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.

Search Console MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "saurabhsharma2u-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}

X402 API

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "x402-api-2": {
      "command": "uvx",
      "args": [
        "x402"
      ]
    }
  }
}

Frequently asked questions

Search Console MCP is categorized under Marketing and uses a local stdio subprocess. X402 API belongs to Marketing and uses a local stdio subprocess. Pick Search Console MCP for marketing work and X402 API 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.

Search Console MCP is listed as free. Auth: oauth 2.0. X402 API has no declared pricing — check the project's own site. 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 saurabhsharma2u-search-console-mcp and x402-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Search Console MCP has a quality signal of 71/100 (Great) with 4 views, 0 installs and 306 GitHub stars. X402 API has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.