Morning check
Did any of my sites lose more than 20% of clicks this week?
One line answer across every site.
Gemini CLI can talk to MCP servers, but Search Console needs a Google Cloud project and credentials before any server can read it. LopeBase skips that: connect with Google once, run one command, and Gemini CLI can read your search data.
Read only access to Search Console. Nothing to paste into settings.json.
One question, one tool call, and an answer built on your own Search Console numbers.
Which queries gained the most clicks this week across my sites?
read_sourcegsc-acmetop_queries
| query | clicks | impr. | pos. |
|---|---|---|---|
| free invoice generator | 318 | 7,240 | 4.1 |
| invoice number format | 122 | 2,980 | 3.6 |
| acme invoices | 97 | 140 | 1.0 |
free invoice generator leads with 318 clicks from position 4. It is your biggest non brand search; the page behind it is worth keeping fresh.
Skip creating a project, enabling the API, and downloading credentials. Connect with Google in LopeBase does it.
Every Search Console property you connect is ready, so Gemini CLI can compare them in one answer.
Type /mcp and LopeBase is listed with its tools. If something is wrong, it says so there.
Three steps. The first is the same for every app; the rest is specific to Gemini CLI.
Connect Search Console to LopeBase. Start free, add your site, press Connect with Google, and pick the Search Console property. Domain and URL prefix properties both work. Google is only asked for read access.
Run npx lopebase in your project folder. It signs this computer in and registers LopeBase with Gemini CLI, so you never paste a token into settings.json.
Start Gemini CLI and check. Type /mcp to see LopeBase and its tools listed, then ask your question.
$ npx lopebase
Works on macOS, Linux, and Windows with Node 18 or later. The same command can also set up Claude Code, Codex, opencode, or Cursor Agent if you use more than one.
Short, scriptable asks suit a terminal. Run them while you work.
Did any of my sites lose more than 20% of clicks this week?
One line answer across every site.
Show daily clicks for 'invoice template' and 'invoice generator' over the last 90 days.
Pass the searches you name and get their daily history.
List searches at position 8 to 20 with over 200 impressions.
The fastest pages to improve.
Which searches does /features show up for?
Know what a page earns before you change it.
Seven datasets per site, read live from Search Console when you ask. Rankings and clicks cover the last 28 days, and tracked searches up to 90.
More on each dataset: Search Console MCP. Connecting in the console: the Search Console connector.
LopeBase is not the only route. Here is how it compares with the usual one.
| Topic | A community MCP server | LopeBase |
|---|---|---|
| Setup | A Google Cloud project, the API turned on, credentials, and an entry in settings.json. | npx lopebase and Connect with Google. |
| Credentials | A key file path in your settings. | Kept by LopeBase, encrypted. Gemini CLI never sees it. |
| Several sites | Depends on how access is set up for each. | Every connected property, each by name. |
| More than search | Search Console only. | GA4, Bing, PostHog, and revenue on the same server. |
| Best when | You want to run and change the server yourself. | You want it working in a few minutes. |
Something else? Contact us.
With Gemini CLI's own MCP settings, using the command npx lopebase mcp. That command forwards to LopeBase with your saved sign in, so no token goes in settings.json.
Yes. Add a server named lopebase whose command is npx lopebase mcp, after signing in once with npx lopebase login.
No. This is for Gemini CLI in your terminal. LopeBase works in any client that can add a remote MCP server with sign in.
Only the one time Connect with Google screen, which asks for read access to Search Console.
That is Search Console itself. Google publishes search data with a delay of about two days.
Free for one product. No card. Agent access is on every plan.