A Search Console MCP connection gives Claude Code search evidence to accompany its route and sitemap analysis. This is useful when an exported site contains a page but Google reports a different index state. Start by verifying the property, then relate sitemap status and selected URL results to the repository's intended output.
What do you need before connecting?
Use Claude Code installed on the computer where you will run these commands. Its CLI supports remote HTTP MCP servers and browser OAuth. This route registers an explicit user-scoped server for use across your projects; project-scoped team configuration is a separate choice. You do not need to run a local Google API server.
- A Google login with access to the Search Console property you intend to query.
- A LoomaScale account with Google Search Console connected; a GA4 connection does not grant Search Console access.
- The exact property returned by discovery: a domain property such as sc-domain:example.com or a URL-prefix property such as https://www.example.com/.
How do you connect Claude Code to GSC?
1. Connect GSC in LoomaScale
Create or sign in to your LoomaScale account, then open Connections. Choose Google Search Console, sign in with the Google email that has access to the required data, and review the requested permissions. Signing in to LoomaScale with Google is not a substitute for connecting this data source. You can connect this service without connecting an advertising account.
2. Register the remote MCP server in Claude Code
Run this command in your system terminal, outside a Claude Code conversation. User scope makes the connection available across your projects. The URL selects this Google service's tools.
claude mcp add --transport http --scope user loomascale-gsc https://api.loomascale.com/mcp/gscIf you already use the full LoomaScale agent plugin, check its tools before adding a second connection. The plugin route is documented in the Claude Code setup guide; this article uses direct MCP setup.
3. Authenticate from Claude Code's MCP menu
Open Claude Code and enter /mcp. Select loomascale-gsc and complete its authentication flow in the browser. Use the LoomaScale account with your Google source connected. Return to Claude Code and confirm the server is connected. You can inspect the saved server from the system terminal with claude mcp get loomascale-gsc or claude mcp list. A successful add command saves configuration; it does not prove that the Google account lookup succeeded.
4. Verify access with an actual account lookup
Use LoomaScale to call gsc_list_sites. List my Search Console properties with their exact site URLs and permission levels. Ask me which property to use. Do not guess a domain or submit anything to Google.
Match the returned property to the site you manage. A domain property and a URL-prefix property can cover different URL sets, so keep the exact returned identifier. After selection, request a small performance report with explicit dates and search type. Check the actual tool result before interpreting a table: an explanation of Search Console without a tool call is not a connection test.
How do you review a sitemap issue with Claude Code?
Ask for the submitted sitemap's status and the code that generates its URLs. Pick a few representative affected URLs rather than treating the sitemap's status as proof that every page is indexed. If you have a built export, compare its canonical paths with the source configuration before proposing changes.
Use LoomaScale with my selected Search Console property. List submitted sitemaps with their processing state, errors and warnings. Read this repository's sitemap and route-generation code without edits. Ask me to choose up to five affected URLs and inspect their stored index status. Compare intended URLs, canonical paths and Google's findings. Propose one focused follow-up and list missing evidence. Do not submit a sitemap or change files.
A sitemap accepted by Google is a discovery signal, not an indexing guarantee for every included URL. The repository can show intent; the built files and served responses show what ships. Keep those evidence layers separate from Google's historical inspection. If a repair is needed, verify the generated artifact before treating a source change as complete.
Which MCP endpoint does this guide use?
https://api.loomascale.com/mcp/gscThe service-specific endpoint exposes GSC tools and LoomaScale account helpers. The full directory plugin or connector uses https://api.loomascale.com/mcp and can reach all sources you separately connect. Choose the full connection for work across services; use the specific endpoint when you want this source's tool set. An endpoint choice limits exposed tools, not the Google roles your login holds.
What can Claude Code read or change in GSC?
LoomaScale's Search Console tools retrieve organic clicks, impressions, CTR, average position, query and page opportunities, sitemap status and Google's indexed URL-inspection result. When you ask in chat, they can also submit, resubmit or delete a sitemap and add or remove a property in your Search Console list; removing a property needs explicit confirmation, and an added property stays unverified until you verify it in Search Console. They cannot request indexing or change a website's content. Connections made before November 16, 2026 need a reconnect to grant the write permission. Performance rows describe Google Search visibility, while GA4 sessions describe measured visits. Google's Search Analytics API returns leading rows within its limits and does not guarantee every data row; a missing query is not proof that it received no searches.
Why is the connection or data missing?
If the server needs authentication, open /mcp and sign in again. If tools are missing, check claude mcp list, the source endpoint, and whether an organization policy restricts the server. Restart the session after a configuration change if needed. A Claude web connector and an explicit CLI server can overlap; check the active tools before adding duplicate connections.
For a missing site, check the connected Google email and Search Console access. For unexpected totals, keep the same property, dates, filters and search type as the interface you compare with. Recent data may be incomplete; name the period you used. URL Inspection reports Google's stored index view, rather than a new browser crawl of the current page. A successful connection does not improve rankings or cause a page to be indexed.
Related connection guides and official references
Use GSC in another assistant
- How to Connect ChatGPT to GSC
- How to Connect Claude to GSC
- How to Connect Codex to GSC
- How to Connect Grok Build to GSC
Connect another Google source to Claude Code
Official setup references
- Anthropic's Claude Code MCP, scopes and authentication guide
- Google's Search Analytics query documentation
Setup references checked on November 12, 2026. Menu labels and workspace policies can change; use the linked vendor guidance for your account. For LoomaScale's supported workflows, see the documentation hub.
