Rank pages by business value
Join Search Console clicks with GA4 conversions by page and rank pages by signups per click.
Puts content work where it pays.
top_pageslanding_pages
Agents and MCP
One MCP server for all your SEO data.
An MCP server for one API covers one tool. LopeBase connects Search Console, Bing, and your analytics tool for every product you run, then gives your agent two tools to read all of it. The interesting questions sit between the tools: which rankings bring buyers, and which only bring visitors.
Free for one product. Read-only connections, read-only agent access.
Questions one tool cannot answer
Your agent reads Search Console and your analytics side by side and joins them by page.
Which pages rank well but bring no signups?
read_sourcegsc-acmetop_pages
read_sourcega4-acmelanding_pagesgoal: sign_up
| page | clicks | pos. | converted |
|---|---|---|---|
| /blog/invoice-template | 3,102 | 3.1 | 4 |
| /blog/late-payment-email | 1,288 | 5.6 | 2 |
| /pricing | 611 | 2.4 | 143 |
| /compare/freshbooks | 402 | 6.8 | 38 |
Two posts bring nearly 4,400 search clicks a month and six signups. They answer the search well but never point to the product. Adding a template download that needs an account is the likely fix.
Every source, same shape
Search Console and Bing share field names, and so do GA4, Plausible, and PostHog, so your agent compares them without translating.
Every site, one connection list
list_sources shows every connected site and dataset in your workspace.
From finding to fixing
next_article_topic and submit_draft turn search gaps into drafts in your review queue.
What your agent gets
Two read tools cover every source. The rest are there when your agent needs them.
- list_sourcesEvery connected search and analytics source, with its datasets and fields.
- read_sourceRows from one dataset, with optional filters like a goal event or a list of searches.
- query_metricA single headline number, the same one the console shows, like pageviews_7d.
- get_digestThis week against last week for every product, plus what needs attention.
- next_article_topicThe best unused topic from Search Console quick wins and your keywords.
- submit_draftAn article from your agent, through the same checks, into your review queue.
Workflows across tools
Each of these needs at least two sources. That is the point.
Find Google and Bing differences
Which searches do well on Google and badly on Bing?
Often a title or a missing Bing verification.
search_queriestop_queries
Check that search clicks arrive
Do Search Console clicks roughly match organic sessions in analytics this month?
A big gap can mean a tag missing from some pages.
search_performancetraffic_sources
Run a portfolio SEO review
For each of my sites, give me one search to target and one page to fix this week.
Every site you run, in one pass.
search_queriestop_pages
Write what search is asking for
Find a search we show up for but have no page about, then write that page in our voice.
From the gap to a reviewed draft in one session.
page_queriesnext_article_topicsubmit_draft
Measure a rewrite
We rewrote the invoice template post on the 1st. How have its searches moved since?
Daily history for the searches that page targets.
queries_daily
Set it up in a few minutes
- 01
Connect your sources. Start free, add a product, and connect Search Console, Bing, and your analytics tool. Google, Bing, and Cloudflare connect in one click.
- 02
In a terminal agent, run
npx lopebasein a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent. - 03
In a chat app or editor, add the remote MCP server
https://app.lopebase.com/api/mcpand sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Prefer to stay in the terminal? npx lopebase lets your agent do the connecting, and it asks you only for what needs a person.
Good to know
- Read only, both waysEvery connection only reads your tools. Nothing an agent does through LopeBase changes Search Console, Bing, or your analytics.
- Aggregates onlyAgents get counts, rates, and positions. No visitor or customer records reach an agent through these tools.
- Each tool's own limits applySearch Console lags about two days; Bing's link index is smaller; Cloudflare counts visits, not people.
- On the recordAnything an agent changes, like connecting a source, is in the audit log under the person who issued its token.
SEO MCP questions
Something else? Email us.
Why not run a separate MCP server for each tool?
You can. But each one needs its own keys, runs on your machine, and returns its own shapes. LopeBase connects each tool once, works for every site, and gives your agent one way to read all of them.
Which agents does it work with?
Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent through npx lopebase, and any client that can add a remote MCP server with sign-in.
Does it work for agencies with client sites?
Yes. Each client site is a product with its own sources. Plans scale by how many products you run.
What does it cost?
Free for one product, with agent access included. Paid plans add products; see pricing.
Can my agent publish changes to my site?
Only through your review queue. Articles from submit_draft go through the same checks as LopeBase's own and wait for approval unless you turn on Autopilot.
Give your agent every number it needs for SEO.
EmDashFree for one product. No card. Agent access is on every plan.