How to Connect Google Search Console to Claude with MCP

The direct answer

To connect Google Search Console to Claude, connect the property in Foglift, then add https://mcp.foglift.io/api/mcp as a Claude custom connector. The Google connection uses read-only OAuth. Claude authorizes separately through Foglift OAuth, then calls get_search_console for queries, pages, clicks, impressions, CTR, average position, and Contested Demand.

This hosted path removes the infrastructure work from the setup. You do not create a Google Cloud project, service account, client secret, or JSON key. Foglift operates the Google OAuth client and MCP server; you choose which verified property the connected agent may read.

Before you start

• The Google account must have access to a verified Search Console property. Google requires an authenticated user with the appropriate property permission for Search Analytics requests.
• Search Console connections work on every Foglift plan. A new account-scoped MCP connection requires Launch or higher, starting at $49 per month.
• Anthropic documents remote custom connectors for Claude Free, Pro, Max, Team, and Enterprise. Free accounts are limited to one custom connector. Team and Enterprise owners must add the connector for the organization before members connect it.

Step 1: Connect Google Search Console

1. Open Foglift Search Console and choose Connect Google Search Console.
2. Sign in with the Google account that can read the property. Review and approve the read-only Search Console permission.
3. Select the verified property that matches the brand workspace.
4. Confirm that the Queries and Pages views return the expected property. Keep Google and Bing evidence separate when both providers are connected.

Google's Search Analytics API returns top rows rather than promising every row in the property. The metrics exposed by get_search_console retain their Search Console meaning. Impressions or clicks do not prove that an AI answer mentioned or cited the page.

Step 2: Add the hosted MCP server to Claude

1. In Claude, open Customize > Connectors.
2. Select + Add, then Add custom connector.
3. Name the connector Foglift.
4. Paste https://mcp.foglift.io/api/mcp as the remote MCP server URL and continue.
5. Review the authentication settings Claude detects, choose the sign-in flow, and finish adding the connector.
6. Complete the Foglift authorization page. In a conversation, use the lower-left + menu, open Connectors, and enable the new connection.

On Team and Enterprise, an Owner or Primary Owner starts in Organization settings > Connectors, selects Add > Custom > Web, and enters the same URL. Members then open Customize > Connectors and select Connect.

https://mcp.foglift.io/api/mcp

Step 3: Verify the account and ask for data

Start with identity, then request evidence. This prevents an agent from silently reading the wrong default brand when an account contains multiple workspaces.

Use the connected Foglift MCP tools.

1. Call whoami and show the account, plan, and default brand.
2. Call get_search_console for Google queries over the last 28 days.
3. Return query, clicks, impressions, CTR, and average position.
4. Keep Search Console metrics separate from AI mentions, citations, referrals,
   and crawler requests.

Useful follow-up questions include “Which pages gained impressions but lost clicks?” and “Which Search Console queries have demand but weak stored AI visibility?” The second question uses Contested Demand. It does not start a new AI Visibility Check.

What Claude can and cannot read

The tool is intentionally narrow. It does not expose Google URL Inspection, sitemap submission, property management, or write operations. Use Search Console itself for those jobs.

Use the same connection in ChatGPT, Claude Code, or Cursor

ChatGPT

OpenAI's current custom MCP path is ChatGPT Plugins > + > Add custom MCP server. Enter https://mcp.foglift.io/api/mcp, configure authentication, review the risk notice, and create the plugin. Workspace permissions and security restrictions can limit who may add or use a custom server. Start the first conversation with whoami.

Claude Code

Claude Code recommends HTTP for remote MCP servers. Add the hosted endpoint, then run /mcp inside Claude Code to complete OAuth and inspect the connection.

claude mcp add --transport http foglift https://mcp.foglift.io/api/mcp

# Then, inside Claude Code:
/mcp

Cursor

Foglift's documented Cursor path currently uses the local npm MCP server with a Launch or higher API key. Keep the key out of source control, add the server in Cursor's MCP settings, restart Cursor, and call whoami. The connected Search Console property stays in Foglift.

{
  "mcpServers": {
    "foglift": {
      "command": "npx",
      "args": ["-y", "foglift-mcp"],
      "env": { "FOGLIFT_API_KEY": "sk_fog_..." }
    }
  }
}

Plan and pricing boundary

Connecting Google Search Console is available on Free, Launch, Growth, and Enterprise. New account-scoped MCP access begins on Launch at $49 per month with monthly billing and no sales call. Launch includes three brands, three team members, five-engine monitoring up to daily, 50 API requests per day, 1,000 API requests per month, and developer access through REST API, CLI, and MCP.

Review the current plan limits or open the Google Search Console MCP server specification for the exact provider, request, and evidence boundaries.

Primary sources

• Anthropic: Get started with custom connectors using remote MCP. Current individual and organization setup paths, plan availability, enablement, and remote-network boundary.
• Anthropic: Connect Claude Code to tools via MCP. Remote HTTP setup, OAuth login, verification, and server scopes.
• OpenAI: Add a custom MCP server. Current ChatGPT plugin setup, authentication options, supported protocols, and security warning.
• Google: Search Analytics query reference. Search performance fields, dimensions, authorization scopes, and top-row completeness boundary.
• Google: Authorize Search Console API requests. OAuth requirements and the webmasters.readonly scope.

Google Search Console and Claude FAQ

Fundamentals: Learn about GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) (the two frameworks for optimizing your content for AI search engines).