Ask Claude about your Search Console data
Search Console holds the only record of what people typed before they arrived, and its interface makes that record almost unusable: a thousand rows, no way to ask a follow-up, and an export that loses the filter you spent ten minutes building. A google search console mcp server changes the shape of that work. Instead of clicking through the Performance report, you ask a question in plain language, and the assistant runs the query, reads the rows, and answers — then answers the next question against the same data without you fetching it again.
The connector URL
https://api.mevnix.com/mcp
The same URL for every source. Add it once in Claude; it carries whichever accounts you have connected.
What Search Console can actually tell you
The Performance report is four numbers — clicks, impressions, CTR and average position — sliced by query, page, country and device. The interesting part is the slicing, and it is the part the interface is worst at. Mevnix exposes query and page as dimensions you can combine, with filters that take contains, equals and regular expressions, so "which URL owns the queries containing a competitor's name" is one request rather than a morning. Two details matter and neither is obvious from the interface. Position is an average across every impression, so a query at 17 is often a page-two result that ranked well twice, not a stable seventeenth. And Search Console data runs two to three days behind, so Mevnix pulls the end of every range back by three days rather than letting incomplete days drag every average down — a difference you notice most when comparing this week to last.
What Claude does with it that a report does not
A dashboard answers the question it was built to answer. The value of putting Search Console behind an assistant is the second question: you see forty queries sitting between positions 11 and 20, you ask which pages they land on, you ask which of those pages already mention the phrasing and which do not, and you get to a list of edits without opening a spreadsheet. Claude can also hold more than one shape of the data at once — it will pull a three-month range and a fourteen-day range and tell you which queries appear in the first and have vanished from the second, which is a regression check that no standard report produces because the rows you care about are the ones that are missing.
Why this pair specifically
SEO work is the one marketing task where the analysis genuinely is the deliverable. Nobody needs a chart of impressions; they need to know which page to rewrite and what to put in it — and the second half of that is writing, which is already why this audience has Claude open. Connecting Search Console closes the loop that used to run through a CSV: the assistant that reads the position data is the one that drafts the title tag, and it can check its own work a fortnight later against the same source. That is a workflow, not a feature, and it is the one we built this connector for before we built anything else.
What that looks like
Which queries am I ranking on page 2 for, where a small push gets me to page 1?
| Query | Impressions | Position |
|---|---|---|
| local seo services | 480 | 13 |
| local seo agency | 214 | 19 |
| seo services for local business | 96 | 38 |
An illustrative example — the shape, not a customer's data — and it is a marketing agency's own site rather than a client's, because the first Search Console property most people connect here is their own. One intent, three ways of typing it, three very different positions, all landing on one page. The top row is a fortnight of work away from page one; the bottom row says that page never uses that phrasing at all. Neither finding surfaces in the Performance report, because sorted by impressions these three rows are nowhere near each other.
Setting it up
- Connect Google
Sign in to Mevnix and connect your Google account. One consent screen covers Search Console and Analytics; you pick which properties are readable afterwards, and nothing is exposed until you do.
- Add the connector to Claude
In Claude, add a custom connector and paste the Mevnix URL. Claude sends you back here to approve the request. There is no Google Cloud project to create, no API to enable, no service-account JSON to download, and nothing running on your machine.
- Ask
That is the whole of what it takes to connect Search Console to Claude. Name the property in your first question if you have more than one — otherwise Mevnix resolves it for you when there is only one to pick.
Free covers one source of each type. $9/month removes the limits, for as many clients as you like — see pricing.
Questions
- Do I need a Google Cloud project?
- No. That requirement comes from running a gsc mcp server yourself, where you have to create a project, enable the Search Console API and hand the process a credential file. Mevnix is hosted and already registered with Google, so connecting is an OAuth consent screen and nothing else — no terminal, no local process, no key on disk.
- Does it work with domain properties?
- Yes. Domain properties, written sc-domain:example.com, and URL-prefix properties both work, and a domain property is usually the better one to expose because it covers every subdomain and protocol variant at once rather than splitting your numbers across four separate entries.
- Can it change anything in Search Console?
- No. Mevnix requests read scopes only, so submitting a sitemap, requesting indexing or removing a URL are not things it is able to do even if asked. You can see every AI client that has been authorized on the Authorized apps page and revoke any of them immediately.
- Which properties can it see?
- Only the ones you pick. Domain properties (sc-domain:) and URL-prefix properties both work. On the free plan you can expose one property; Pro removes that limit, including across separate clients.
- How fresh is the data?
- As fresh as Search Console itself, which is two to three days behind for everyone. Mevnix caches responses for six hours on top of that, because re-fetching rows that cannot have changed only burns quota. Cached answers carry the time they were fetched.