gsc

Google Search Console MCP Server - Connect Google Search Console to Claude, Cursor, and other MCP clients.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio appsyogi-com-gsc-mcp-server npx -y @appsyogi/gsc-mcp-server run \
  --env GSC_SCOPES="https://www.googleapis.com/auth/webmasters https://www.googleapis.com/auth/urlinspection" \
  --env GSC_CLIENT_ID="your-google-client-id" \
  --env GSC_OAUTH_PORT="optional-port-for local OAuth redirect" \
  --env GSC_CLIENT_SECRET="your-google-client-secret" \
  --env GSC_REFRESH_TOKEN="optional-refresh-token-if-known"

How to use

This MCP server provides a bridge between Google Search Console data and MCP clients such as Claude, Cursor, and other agents. It exposes tools to query search performance, inspect URLs, manage sitemaps, and export data for further analysis. The server supports read-only operations by default and can be configured for full access with additional scopes to submit sitemaps and perform URL inspections. To start using it, install the package globally, configure OAuth credentials, and run the MCP server using the included CLI. Clients connect via standard MCP protocols and can invoke tools like search analytics queries, sitemap management, URL inspection, and SEO opportunity analyses. The server also includes a caching layer (SQLite) to speed up repeated queries and minimize API quota usage.

How to install

Prerequisites:

Node.js (LTS) and npm installed on your system
Internet access to install packages

Installation steps:

Install the MCP server globally via npm:

npm install -g @appsyogi/gsc-mcp-server

Prepare Google Cloud OAuth credentials as described in the README (client ID/secret or a service account) and ensure the OAuth consent screen is configured for test users if applicable.
Initialize credentials (interactive or via service account) using the CLI as documented in the repository:

gsc-mcp init

Start the MCP server for MCP clients:

gsc-mcp run

If you need HTTP-based debugging, you can run:

gsc-mcp run --http 3333

Notes:

Ensure environment variables for OAuth (CLIENT_ID, CLIENT_SECRET) are set if you’re not using interactive init.
The server stores tokens in the OS keychain when available.
Use gsc-mcp doctor to verify connectivity before running the server in production.

Additional notes

Tips and notes:

The server defaults to readonly scopes; use --scope full during init if you need sitemap submission or URL inspection capabilities.
For MCP client integration (Claude/Cursor), configure the client with the gsc-mcp command and appropriate args as shown in the README (e.g., npx with -y to install and run).
If you encounter OAuth token issues, re-run gsc-mcp init to refresh credentials and tokens; tokens are stored securely in the OS keychain.
The available tools include: searchanalytics.query, report.comparePeriods, sitemaps.list/get/submit/delete, urlInspection.inspect/batchInspect, opportunities.lowCtrHighPos, cannibalization, weeklySummary, and export.csv/export.json.
Be mindful of API quotas; the server includes automatic retries and query caching to reduce API calls.

Related MCP Servers

obsidian -tools

612

Add Obsidian integrations like semantic search and custom Templater prompts to Claude or any MCP client.

mcp

Octopus Deploy Official MCP Server

furi

CLI & API for MCP management

mcp -arangodb

This is a TypeScript-based MCP server that provides database interaction capabilities through ArangoDB. It implements core database operations and allows seamless integration with ArangoDB through MCP tools. You can use it wih Claude app and also extension for VSCode that works with mcp like Cline!

mcp-bundler

Is the MCP configuration too complicated? You can easily share your own simplified setup!

CodeRAG

Advanced graph-based code analysis for AI-assisted software development