GSC MCP Server
Provides tools for interacting with Google Search Console, enabling AI agents to manage properties, analyze search performance, inspect URLs, and manage sitemaps.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GSC MCP Serverget search analytics for last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GSC MCP Server
Google Search Console MCP Server — a TypeScript Model Context Protocol server that provides tools for interacting with the Google Search Console API through AI assistants like Claude Desktop.
This is a TypeScript port of the mcp-gsc Python server, fully compatible with the MCP specification.
Features
21 MCP Tools covering all aspects of Google Search Console
Dual Authentication — OAuth 2.0 (browser login) and Service Account
Cross-platform — Windows, macOS, Linux
STDIO and SSE transport support
Zero-config fallbacks — sensible defaults for all settings
Safety-first — destructive operations disabled by default
Related MCP server: gsc-mcp
Tools Overview
Category | Tool | Description |
Auth |
| Log out and re-login with a different Google account |
Properties |
| List all GSC sites you have access to |
| Get verification and ownership info for a site | |
| Add a new property (destructive — disabled by default) | |
| Remove a property (destructive — disabled by default) | |
Analytics |
| Top queries/pages with clicks, impressions, CTR, position |
| Summary + daily trend for a time period | |
| Compare performance between two date ranges | |
| Queries driving traffic to a specific page | |
| Advanced filtering, sorting, and pagination | |
URL Inspection |
| Detailed crawl/index/rich-result status for a URL |
| Inspect up to 10 URLs at once | |
| Check multiple URLs for indexing problems | |
Sitemaps |
| List all sitemaps for a site |
| Detailed sitemap info with errors and warnings | |
| Detailed info for a specific sitemap | |
| Submit or resubmit a sitemap | |
| Remove a sitemap (destructive — disabled by default) | |
| All-in-one: list, details, submit, delete | |
Info |
| List all tools, auth status, and getting started guide |
Prerequisites
Node.js 18+ (LTS recommended)
A Google Cloud project with the Search Console API enabled
At least one authentication method set up (see below)
Installation
# Clone the repository
git clone <repo-url> gsc-mcp
cd gsc-mcp
# Install dependencies
npm install
# Build
npm run buildAuthentication Setup
You must configure one of two authentication methods:
Option 1: OAuth 2.0 (Recommended)
Best for individual users. Opens a browser window for Google login.
Create a Google Cloud project at console.cloud.google.com
Enable the Google Search Console API
Create OAuth 2.0 Client ID credentials (Desktop application type)
Download the client secrets JSON file
Set the environment variable:
# Windows (PowerShell)
$env:GSC_OAUTH_CLIENT_SECRETS_FILE = "C:\path\to\client_secrets.json"
# macOS / Linux
export GSC_OAUTH_CLIENT_SECRETS_FILE="/path/to/client_secrets.json"Or place the file as client_secrets.json in the project source directory.
On first use, the server will automatically open your browser for authentication. No manual token management needed.
Option 2: Service Account
Best for server/automation use cases.
Create a service account in your Google Cloud project
Download the JSON key file
Add the service account email as a user in GSC for each property
# Windows (PowerShell)
$env:GSC_CREDENTIALS_PATH = "C:\path\to\service_account_credentials.json"
# macOS / Linux
export GSC_CREDENTIALS_PATH="/path/to/service_account_credentials.json"Claude Desktop Configuration
Edit claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"gsc": {
"command": "node",
"args": [
"C:\\path\\to\\gsc-mcp\\build\\index.js"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "C:\\path\\to\\client_secrets.json"
}
}
}
}For macOS/Linux, use forward slashes and the export-style environment configuration.
Restart Claude Desktop after saving. You should see the hammer icon in the input box.
Environment Variables
Variable | Default | Description |
| (none) | Absolute path to OAuth client secrets JSON |
| (none) | Absolute path to service account credentials JSON |
|
| Set to |
|
| Set to |
|
|
|
| Platform default | Override config directory for token storage |
|
|
|
|
| Host to bind when using SSE transport |
|
| Port to bind when using SSE transport |
Running with SSE Transport
# Windows (PowerShell)
$env:MCP_TRANSPORT = "sse"
$env:MCP_HOST = "0.0.0.0"
$env:MCP_PORT = "3001"
npm run start
# macOS / Linux
MCP_TRANSPORT=sse MCP_HOST=0.0.0.0 MCP_PORT=3001 npm run startDevelopment
# Install dependencies
npm install
# Build TypeScript
npm run build
# Run (stdio)
npm run startProject Structure
gsc-mcp/
├── src/
│ ├── index.ts # MCP server entry point + all 21 tool registrations
│ └── auth.ts # Google authentication (OAuth 2.0 + Service Account)
├── build/ # Compiled JavaScript output
├── package.json
└── tsconfig.jsonCredits
Original Python MCP-GSC server created by Amin Foroutan.
License
ISC
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GuodongDai2113/gsc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server