home / mcp / gsc mcp server

GSC MCP Server

Provides Google Search Console data access via MCP clients, enabling search analytics, opportunities, sitemaps, URL inspection, and exports.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "appsyogi-com-gsc-mcp-server": {
      "command": "gsc-mcp",
      "args": [
        "run"
      ],
      "env": {
        "GSC_CLIENT_ID": "YOUR_CLIENT_ID",
        "GSC_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

You can connect Google Search Console data to MCP clients like Claude, Cursor, and VS Code Copilot using the GSC MCP Server. It lets you query search analytics, manage sitemaps, inspect URLs, and generate SEO-related insights, all through MCP-compatible clients.

How to use

Set up the MCP server and connect your MCP clients to start querying Google Search Console data. Use OAuth or a service account to authorize access, then run the MCP server from your preferred client configuration. Use the server to fetch search analytics, identify SEO opportunities, manage sitemaps, and inspect URL indexing status when you have the required scope.

How to install

Prerequisites you need before installing include Node.js and npm. You will install the MCP server globally, initialize credentials, verify your setup, and then start the server for MCP clients.

# Install globally
npm install -g @appsyogi/gsc-mcp-server

# Set up OAuth credentials
gsc-mcp init

# Verify setup
gsc-mcp doctor

# Start the server (for MCP clients)
gsc-mcp run

Additional configuration and usage notes

Configure how you connect MCP clients to the server. You can set up different client integrations (Claude Desktop, VS Code Copilot, Cursor) to run the MCP server as part of their workflow.

If you prefer to use a service account, you can initialize with a service account key instead of interactive OAuth. The server will use the service account to access Google Search Console data.

Configuration examples for MCP clients

Claude Desktop configuration uses the local MCP runner to start the server in MCP mode.

{
  "mcpServers": {
    "gsc": {
      "command": "gsc-mcp",
      "args": ["run"]
    }
  }
}

VS Code Copilot configuration

Add an MCP server entry so Copilot can route queries through the GSC MCP Server.

{
  "servers": {
    "gsc": {
      "command": "gsc-mcp",
      "args": ["run"],
      "type": "stdio"
    }
  }
}

Cursor configuration

If you use Cursor, connect by running the MCP server via npx with the run command.

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": ["-y", "@appsyogi/gsc-mcp-server", "run"]
    }
  }
}

Available tools

searchanalytics.query

Query search performance data with configurable dimensions and filters.

report.comparePeriods

Compare two time periods to reveal changes in performance.

sitemaps.list

List all sitemaps for a property.

sitemaps.get

Get details about a specific sitemap.

sitemaps.submit

Submit a sitemap for a property.

sitemaps.delete

Delete a sitemap from a property.

urlInspection.inspect

Inspect a single URL for indexing status.

urlInspection.batchInspect

Inspect multiple URLs in one operation.

opportunities.lowCtrHighPos

Identify quick-win keywords with high position but low CTR.

opportunities.cannibalization

Detect keyword cannibalization issues across pages.

report.weeklySummary

Generate a weekly performance summary.

export.csv

Export data as CSV.

export.json

Export data as JSON.