Search Console MCP server

Your Search Console data, in Claude and ChatGPT

A hosted, read-only MCP server for Google Search Console, Google Analytics and Bing Webmaster Tools. Paste one URL into your AI assistant, sign in, and ask about clicks, indexing and drops in plain English.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

What it is

An MCP server lets an AI assistant call tools on your behalf. DirectoryLens runs one at https://directorylens.com/mcp. Add that URL to Claude, ChatGPT, Claude Code, Cursor or any app that supports remote MCP servers, sign in once, and the assistant can read your Google Search Console data, plus Google Analytics and Bing Webmaster Tools if you linked them.

It is hosted, so there is nothing to install, no Google Cloud project to create and no API key to paste. It is read-only: the assistant can read reports, and it cannot change your site, your Search Console settings or anything in DirectoryLens except two things you ask for: starting a URL inspection run, and noting that you requested indexing for a URL.

Questions it answers well: “Which page types lost clicks in the last 28 days, and since when?” · “Which of my priority pages are crawled but not indexed?” · “What should I ask Google to index first?” · “Show searches where I rank 5 to 20 and my title is missing the words people use.” · “Are two of my pages competing for the same search?” · “How does Bing compare with Google this month?”

Set it up in about two minutes

  1. Connect Search Console to DirectoryLens. Sign in with Google, pick your Search Console properties. DirectoryLens imports the 16 months Google keeps and syncs every day after that. The 5-day trial includes the MCP server.
  2. Add the server to your assistant. Use the URL https://directorylens.com/mcp:
    • Claude (claude.ai, Desktop and mobile): Settings > Connectors > Add custom connector, paste the URL, then Connect. On Team and Enterprise plans an owner adds it first in Admin settings.
    • ChatGPT: turn on developer mode in Settings (not every plan has it), create a connector with the URL and choose OAuth.
    • Claude Code: run the command below, then /mcp to sign in.
    • Cursor, VS Code and others: add a remote (HTTP) MCP server with the URL. Apps without OAuth sign-in can use a personal access token as an Authorization: Bearer header; you create one on your workspace page.
  3. Approve access on the DirectoryLens page that opens. The assistant then sees the same sites you do, nothing more. Disconnect it from your workspace page at any time; it loses access at once.
claude mcp add --transport http directorylens https://directorylens.com/mcp

The 31 tools

Every tool returns the same shape: the site, the date range, the data source, the units, notes on anything left out, and the data. Dates default to the 28 days ending on the last day Google has finalized, compared with the 28 days before, so the assistant does not compare a half-counted day with a full one.

GroupToolsWhat the assistant can do
Sites and performancelist_sites, portfolio_overview, site_overview, search_queries, search_pages, page_type_scorecard, query_type_breakdownClicks, impressions, CTR and position by site, search, page and page type, with the change against the previous period
Indexingindexing_status, index_coverage_by_page_type, inspect_urls, url_index_history, request_indexing_queue, log_indexing_requestShare of each page type Google has indexed, per-URL inspections through Google’s URL Inspection API, and which pages to ask Google to index first
Growthnear_miss_keywords, new_queries, opportunities, ctr_benchmark, keyword_cannibalization, coverage_matrix, listing_gapsSearches just off page one, new searches, pages clicked less than their position should earn, two pages competing, and (for directories) category × city demand without a page
Problemscontent_decay, recovery_scorecard, thin_pages, risk_signals, url_migration_check, alertsTraffic drops with the day they started, recovery after an update, pages Google never shows, quality signals and redirect checks after a URL change
Visitors and listingsengagement, bing_performance, listings, listing_report, category_city_rollupsGoogle Analytics contact clicks and AI-assistant referrals, Bing next to Google, and each listing’s searches, visits and contacts

Directory-only tools (listings, coverage, rollups, risk signals, search intent) answer for sites set up as directories. Every other tool works on any website.

Hosted vs open-source Search Console MCP servers

There are good open-source Search Console MCP servers on GitHub. They are a thin layer over Google’s API: you create a Google Cloud project, enable the Search Console API, set up OAuth or a service account, run the server on your machine, and the assistant queries Google live. That is the right choice if you want full control and only need raw numbers.

DirectoryLens answers different questions, because it keeps and works on the data before the assistant asks:

Open-source serverDirectoryLens
SetupGoogle Cloud project, OAuth client, local installPaste one URL, sign in
HistoryWhat Google keeps: 16 months16 months on connect, then every day it stores, past Google’s limit
Page typesNot built in; the assistant sees URLsRules group URLs into listing, city, category and other page types
IndexingLive URL Inspection calls, one URL at a timeDaily inspections spread over every page type, with estimates and alerts
Other sourcesSearch Console onlySearch Console, Google Analytics 4 and Bing Webmaster Tools
AccessYour Google token on your machineRead-only OAuth; your Google tokens never reach the assistant

Privacy

The assistant reads reports through DirectoryLens with your access, and its provider receives what it reads under that provider’s own terms. DirectoryLens never gives the assistant your Google tokens, stores only hashes of the access tokens it issues, and you can disconnect any assistant from your workspace page. See the privacy policy.

Questions

Is there an MCP server for Google Search Console?

Yes. Google does not run one, but there are open-source servers you host yourself and hosted ones like DirectoryLens at https://directorylens.com/mcp, which needs no Google Cloud project or API key.

Can the AI assistant change my Search Console or my site?

No. Access to Google is read-only. Inside DirectoryLens an assistant can only start a URL inspection run and note that you requested indexing for a URL, so DirectoryLens can track how long it takes.

Does it work with ChatGPT?

Yes, through a custom connector with OAuth sign-in. ChatGPT needs developer mode for custom connectors, and not every ChatGPT plan has it.

Does it work for sites that are not directories?

Yes. Set the site up as a regular website and every tool except the directory-only ones (listings, category and city coverage, rollups, risk signals, search intent) works.

What does it cost?

The MCP server is included in every DirectoryLens plan, starting at $29.99 a month, with a free 5-day trial (no card needed). See pricing.

How far back can the assistant see?

Everything DirectoryLens has stored: the 16 months Google keeps when you connect, then every day after that, so history grows past Google’s 16-month limit.

Ask your AI about your search traffic.

Connect Search Console, add one URL to your assistant, and ask your first question in a couple of minutes.

Explore the live demo →

5 days free · no card needed · ends on its own