Agents and MCP

Search Console, inside your agent.

Connect Google Search Console to LopeBase once, and any agent that speaks MCP can read your queries, pages, clicks, and positions for every site you run. Ask in plain words where you are close to page one, which titles lose clicks, and what to write next.

Connect with Google in one click. LopeBase only asks Google for read access, and agents only get read access from LopeBase.

Ask it like you would ask a person

Your agent picks the dataset, reads the rows, and works out the answer. No exports, no spreadsheets, no copying numbers between windows.

agent · Search Console, acme.com

Which searches are we close to page one for, but not there yet?

read_sourcegsc-acmesearch_querieslimit 1000

queryimpr.clickspos.
invoice template for freelancers4,8126111.4
send invoice from gmail2,140199.8
late payment email1,9773312.6
recurring invoice app1,305814.1

Four searches get real impressions from positions 9 to 14. invoice template for freelancers is the biggest: one stronger page could move it onto page one. Want me to check which page ranks for it?

Every query, not just the top ten

search_queries returns up to a thousand queries from the last 28 days, with impressions, clicks, CTR, and average position for each.

Page and query together

page_queries shows which searches each page appears for, so an agent can tell when two pages compete for the same search.

Daily history for what you track

queries_daily gives 90 days of daily numbers for the searches you name, so a drop has a date.

What your agent can read

Seven datasets per site, read live from Search Console when the agent asks. Domain and URL prefix properties both work.

  • search_performanceThe site's last 7 days in one row: clicks, impressions, click-through rate, and average position.clicks · impressions · ctr · position
  • top_queriesThe top searches from the last 7 days, for a quick look at what is bringing people in right now.query · clicks · impressions · ctr · position
  • search_queriesEvery search over 28 days, up to 1,000 rows. The one to use for finding wins.query · clicks · impressions · ctr · position
  • top_pagesEach page's clicks and position over 28 days, up to 1,000 pages.page · clicks · impressions · ctr · position
  • page_queriesWhich searches each page shows up for over 28 days, up to 1,000 pairs.page · query · clicks · impressions · position
  • daily_searchOne row per day for the last 28 days, for the trend.day · clicks · impressions · position
  • queries_daily90 days of daily numbers for searches you name. Pass them as filters: { queries: [...] }.query · day · clicks · impressions · position

Workflows worth stealing

Each one is a single ask. Paste it into your agent as written, or change the numbers to suit your site.

Find striking distance searches

List searches where we average position 8 to 20 with at least 200 impressions, biggest first.

The searches where one better page pays off fastest.

search_queries

Fix titles that lose the click

Which pages rank in the top 5 but get under 2% CTR? Draft a better title and description for each.

A page can rank well and still be skipped. Your agent reads the page in your repo and rewrites the snippet.

top_pagespage_queries

Spot pages competing with each other

Find searches where two or more of our pages both show up, and tell me which one to keep.

Two pages splitting one search often both rank worse than one page would.

page_queries

Date a drop

Clicks fell this month. Which searches lost the most, and on what day did it start?

Read the trend, then the daily history for the searches that moved.

daily_searchqueries_daily

Plan the next article

Pick the next article topic for acme and write it in our voice.

next_article_topic starts from Search Console quick wins and skips what you already wrote. submit_draft sends the article to your review queue.

next_article_topicsubmit_draft

Check every site at once

Compare this week's clicks for all my sites and flag any that dropped.

Each site is its own connection, so one ask covers them all.

search_performance

Set it up in a few minutes

  1. 01

    Connect Search Console. Start free, press Connect with Google, and pick the property for each product.

  2. 02

    In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.

  3. 03

    In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.

An agent can also connect Search Console for you: connect_source checks the connection before it saves it.

Good to know

  • Search Console lags about two daysGoogle publishes search data with a delay, so the last day or two are often missing. That is the same in Search Console itself.
  • Up to 1,000 rows per askLarge sites get the top 1,000 queries or pages by clicks. Ask for a narrower list with queries_daily when you need one search exactly.
  • Nothing gets changedLopeBase never submits sitemaps, requests indexing, or changes settings. Agents read; they cannot write to Search Console.
  • One token, one workspaceAn agent's token only reads the workspace that issued it. Revoke it in Settings and it stops on the next request.

Search Console MCP questions

Something else? Email us.

Do I need to set up a Google Cloud project or service account?

No. Connect with Google signs you in and asks for read access to Search Console. A service account still works if you prefer one.

Which agents can use it?

Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent through npx lopebase, and any chat app or editor that can add a remote MCP server with sign-in, such as Claude.

Can my agent see more than one site?

Yes. Each Search Console property you connect is its own connection, and list_sources shows them all, so one question can cover every site.

Does the agent see my Google password or token?

No. Your Google connection stays encrypted in LopeBase. The agent gets rows of search data and never the key that fetched them.

How is this different from exporting to a spreadsheet?

The agent reads current numbers when you ask, picks the right cut of the data, and can act on it in the same session, like rewriting a title in your code.

Give your agent your search data.

Free for one product. No card. Agent access is on every plan.