Can I check why a specific page isn't appearing in Google?

Yes. Use the `inspect_url` tool to run a live inspection on the URL. The AI will return the index status and highlight any errors, such as 'Noindex detected' or mobile usability issues.

How do I find out my top performing keywords?

You can ask the AI to `query_search_analytics` with the dimension set to 'query'. It will return your top keywords based on clicks and impressions for the requested date range.

Can I submit a new XML sitemap through this integration?

Absolutely! Use the `submit_sitemap` tool, provide your site URL and the path to your sitemap (e.g., 'https://example.com/sitemap.xml'). Google will schedule it for processing.

Google Search Console MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Google Search Console
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Google Search Console and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "google-search-console": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Google Search Console MCP Server

Connect your Google Search Console to your AI agent and take control of your technical SEO. Use natural language to query search traffic data, inspect URLs for indexing errors, and manage your sitemaps across all your verified web properties.

GitHub Copilot Agent mode brings Google Search Console data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Search Analytics — Query clicks, impressions, CTR, and position data by date, country, device, or specific queries
URL Inspection — Instantly check if a specific page on your site is indexed by Google and identify any mobile usability or indexing errors
Sitemap Management — List all submitted sitemaps, verify their status, and submit new ones directly from the chat
Site Management — View all your verified properties and add or remove sites from your Search Console account

The Google Search Console MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Google Search Console to VS Code Copilot via MCP

Follow these steps to integrate the Google Search Console MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Google Search Console

Ask Copilot: "Using Google Search Console, help me..." — 10 tools available

Why Use VS Code Copilot with the Google Search Console MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Google Search Console through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Google Search Console + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Google Search Console MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Google Search Console MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Google Search Console to VS Code Copilot via MCP:

add_site

Add a site to Search Console

delete_site

Remove a site from Search Console

delete_sitemap

Delete a submitted sitemap

get_site

Get details for a specific site

get_sitemap

Get details about a specific sitemap

inspect_url

Inspect the index status of a specific URL

list_sitemaps

List submitted sitemaps for a site

list_sites

List verified sites in Search Console

query_search_analytics

Query search traffic data

submit_sitemap

Submit a new sitemap

Example Prompts for Google Search Console in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Google Search Console immediately.

"Check if https://mysite.com/new-post is indexed by Google."

"What were the top 5 search queries for our site last week?"

"Submit our new sitemap at https://mysite.com/sitemap-products.xml to Search Console."

Troubleshooting Google Search Console MCP Server with VS Code Copilot

Common issues when connecting Google Search Console to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Google Search Console + VS Code Copilot FAQ

Common questions about integrating Google Search Console MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.