Setup
Two consent screens and one URL
About three minutes, most of it waiting on Google's consent screen. Nothing here runs on your machine, and nothing here asks for a password.
- 01
Connect your properties
Sign in with Google for Search Console, and again for Analytics: they are two separate grants. After each one, Murkuz lists the properties your own account can already see and you pick the one it should read. Bing Webmaster Tools is a third connection, with a key you generate in Bing Webmaster Tools rather than a sign-in.
Read-only, through the official APIs, with your own permissions, and revocable from your Google account at any time. Murkuz never asks for a password and cannot see a property you have not connected.
- 02
Add Murkuz as a connector
Paste one URL into Claude or ChatGPT and approve the connection. Any other MCP client works the same way, because it is a remote MCP server rather than something that runs on your machine.
Nothing to install, no API key to rotate, no local server to keep running. One connector covers every site on the account, not one per property.
- 03
Ask, and stop logging in
That is the whole setup. Your agent reads the tool list on connection and picks what fits the question, so you ask in your own words and never type a tool name.
The web app is there to change what is connected. Most people do not open it again.
Free connects Google Search Console for one site. Every paid plan connects all three sources. Either way the connector is the same one, and so is the tool list.
In practice
A question goes in. Rows come back.
Every other tool in this category runs the analysis on its own servers and shows you the conclusion. Murkuz's job is the plumbing: real rows, filtered, sorted and paginated, with the window and the source attached.
What you type
“Which pages lost the most clicks in the last 28 days, and which queries did they lose?”
Your words. No tool name, no date syntax, no export.
What your agent picks
Live_Traffic_Drops
One of 32 tools it can see. It chose that one from the question, and it can follow up with a second call if your next sentence needs one.
What comes back
blog.your-store.com, 1 Aug to 28 Aug against the 28 days before it. 41 pages moved. The top row lost 312 clicks, mostly on two queries.
Real rows out of your own property, filtered and sorted, not a paragraph of our opinion about them.
What is attached to it
The property, the window, how fresh the data is, how many rows exist and how to ask for the next page.
So the model can check its own footing, and so can you.
The figures above are shaped like a plausible answer on a made-up domain. They are not anyone's data.
The whole surface
7 groups, 32 tools
The groups differ on one thing: where the numbers come from. 6 of them read accounts you already own. One buys data from outside them, and it is the only one with a cost next to it.
Your sites
3What is connected, and how fresh it is. Where an agent starts before it asks anything else.
Search Console
8Your own Google Search Console data, read live from Google on every call. Never metered.
Analytics and Bing
2The other two sources, on their own terms. Also your own data, also never metered.
Search Console crossed with Analytics
5The questions neither tool can answer alone, because the answer needs both sides of the visit.
Across every site at once
2The reason the connector is worth having when you run more than one property. One question, every site.
Indexing
3Read and change what Google has been told to crawl.
Research
9The only group that looks outside your own accounts, so the only group that costs credits. Nothing here runs without your say.
No tool is withheld from a lower plan. Every account, Free included, is handed the same 32. What a plan changes is how many of them have a connected source to answer from: 16 answer on Free, which connects Search Console alone, and all 32 answer on any paid plan, which connects all three sources and includes research credits.
Read the full tool referenceWhat costs anything
Reading your own data is free. Buying data is not.
Your Search Console, Analytics and Bing numbers come out of your own accounts, so serving them costs us nothing and we never meter them, on any plan, with no date-range cap. 24 of the 32 tools never cost a credit.
The 8 calls that spend credits
Keyword volume, difficulty, competitor rankings and SERP snapshots are not in your accounts. We have to buy them, so they are the one thing with a number next to them.
Keyword_Metrics2 creditsKeyword_Ideas2 creditsSERP_Snapshot1 creditCompetitor_Gap3 creditsBing_Keyword_Metrics9 creditsBing_Keyword_Ideas9 creditsBing_Keywords_For_URL9 creditsBing_Site_Keywords9 credits
Figures are the default request shape. Asking for more rows costs more, and the tool reports what it spent in its own response.
How the meter behaves
- One credit is one cent of what the underlying data costs us. There is no per-call markup, and the whole rate card is published, so your agent can price a sweep before it runs one.
- A repeat of a call someone ran recently is served from cache and costs nothing. A call that fails or comes back empty is refunded.
- Bing research is dearer than its Google equivalent because the provider bills a flat fee per Bing lookup, whatever the payload. Asking for fewer keywords does not make it cheaper.
- Run out and only research pauses. Everything reading your own Search Console, Analytics and Bing data keeps working, because it was never metered in the first place.
- Free holds no research credits, so the 8 metered calls return a reason instead of numbers, as do the 8 that need Analytics or Bing connected. How many credits each paid plan grants is on the pricing page.
Built for more than one site
Add a site next month. It is simply there.
Search Console shows you one property per view, and most tools in this category are built and priced the same way. The connector is scoped to your account instead, so the roster is one question.
If you run one site, this is a convenience. If you run twelve, it is the reason to bother.
One question, every property
All_Sites_Overview and Portfolio_Comparison take the whole account, so a roster question is one call and one answer rather than a dozen exports joined in a spreadsheet.
One connector, not one per site
You add Murkuz to Claude once. Connect a site next month and it is simply there in the next question, with nothing to reconfigure on the agent side.
Sites are the only fence
Reading any connected site is unmetered on every plan. How many you can connect is the thing a plan changes, and that number lives on the pricing page.
The honesty contract
An answer you cannot check is not an answer.
A model will reason from whatever it is handed and sound certain either way. So every response the connector returns is shaped to be checkable, and the things Murkuz does not do are said out loud.
Paginated, not truncated
A long answer says how many rows exist and how to ask for the next page, instead of quietly cutting at fifty and letting the model reason from a slice.
Sourced, every time
Each response carries which property it came from, which window, and how fresh the data is. Nothing arrives without its provenance.
Never a fabricated zero
A source that is not connected says so. It returns a reason explaining what is missing, rather than a zero that would read as bad news about your site.
Reads, and one write you ask for
Murkuz does not write your content, publish it, or change your pages. The only call that changes anything at Google is Submit_Sitemap, and only when you ask for it.
Before you connect
The questions people ask first
No. Murkuz is a remote MCP server. You paste one URL into Claude or ChatGPT and approve the connection, which means there is no package to install, no API key to rotate and no local process to keep running.
About three minutes, most of it waiting on Google's consent screen. Search Console and Analytics are two separate Google grants, Bing Webmaster is a key you paste, and then one connector URL and you are done with the web app.
Reads run through the official Google and Bing APIs with your own permissions, and you can revoke them from your own account at any time. Of the 32 tools, the only one that changes anything at Google is Submit_Sitemap, and it runs only when you ask for it.
No. You ask a question in your own words and your agent picks the tool that fits. The tool reference exists so you know what the question can be, not so you can type a tool name.
The tool returns a reason explaining what is not connected, rather than a zero that would read as bad news about your site. On Free, which connects Search Console alone, 16 of the 32 tools answer with numbers and the rest answer with that reason.
Claude and ChatGPT as a connector, and any other MCP client as an MCP server. The tool surface is identical in all of them, because it is the same server.