gsc-mcp-server
Provides tools to query Google Search Console for search performance data, list properties, and inspect URL indexing status.
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-serverList my Search Console properties"
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
MCP server for Google Search Console. Query search performance, list properties, and inspect URL indexing status from Cursor, Claude Desktop, or any MCP-compatible client.
Tools
Tool | Description |
| List Search Console properties accessible to your Google account |
| Query clicks, impressions, CTR, and position with dimensions and filters |
| Inspect a URL's index status, crawl state, and mobile usability |
Related MCP server: google-search-console-mcp-python
Prerequisites
Node.js 18+
A Google Cloud project with the Search Console API enabled
An OAuth 2.0 Desktop client (client ID + secret)
A Google account with access to the Search Console properties you want to query
Google Cloud setup
Go to Google Cloud Console.
Create or select a project.
Open APIs & Services → Library and enable Google Search Console API.
Open APIs & Services → Credentials → Create Credentials → OAuth client ID.
Application type: Desktop app.
Add
http://localhost:3336/callbackas an authorized redirect URI (if prompted).Copy the Client ID and Client secret.
Install and authenticate
Option A: From npm (after publish)
export GOOGLE_CLIENT_ID="your-client-id.apps.googleusercontent.com"
export GOOGLE_CLIENT_SECRET="your-client-secret"
npx gsc-mcp-authOption B: From source
git clone https://github.com/bykreth/gsc-mcp-server.git
cd gsc-mcp-server
npm install
cp .env.example .env
# Edit .env with your credentials, then:
export $(grep -v '^#' .env | xargs)
npm run authThe auth flow opens a browser on port 3336. Sign in with the Google account that has Search Console access. Tokens are saved to ~/.config/gsc-mcp/tokens.json by default (override with GSC_TOKEN_PATH).
MCP client configuration
Cursor
Add to ~/.cursor/mcp.json (merge with existing servers):
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "gsc-mcp-server"],
"env": {
"GOOGLE_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"GSC_TOKEN_PATH": "/Users/you/.config/gsc-mcp/tokens.json"
}
}
}
}For local development, point command at Node directly:
{
"mcpServers": {
"google-search-console": {
"command": "node",
"args": ["/absolute/path/to/gsc-mcp-server/src/index.js"],
"env": {
"GOOGLE_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
}
}
}
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (see examples/claude-desktop.json).
After changing MCP config, fully quit and restart your client so the server reloads tokens.
Example prompts
Once connected, you can ask your AI assistant:
"List my Search Console properties"
"What are the top 20 queries by clicks for https://example.com/ in the last 28 days?"
"Show me pages with the most impressions last week"
"Is https://example.com/blog/my-post indexed?"
Environment variables
Variable | Required | Description |
| Yes | OAuth 2.0 Desktop client ID |
| Yes | OAuth 2.0 Desktop client secret |
| No | Token file path (default: |
| No | Pre-fill email in the OAuth browser sign-in |
Troubleshooting
Symptom | Fix |
| Run |
No | Revoke the app at Google Account permissions, then re-run auth |
Port 3336 in use | Free the port or stop the conflicting process, then re-run auth |
| Confirm the signed-in Google account has access to the property in Search Console |
MCP client can't find | Use the full path to |
Related MCP servers
Google Analytics MCP — official GA4 server
DataForSEO MCP — official DataForSEO server
License
MIT
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
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/jlnkrth/gsc-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server