Getting started
Setup is three steps. Then you stop logging in.
About three minutes, most of it waiting on Google's consent screen. You connect your properties, paste one URL into Claude or ChatGPT, and ask your first question. There is nothing to install.
What you need first
Three things, and you probably have all three already. Nothing here asks for a Google Cloud project, a server or a credit card.
A Murkuz account
Free on one site, no card. Search Console only, which is enough to see what this feels like before you pay for anything.
A property you are verified on
Search Console offers the properties your Google account owns or has been added to. Analytics needs read access on the property you want.
Claude, ChatGPT or any MCP client
The same connector URL works in all of them. Murkuz is a remote MCP server, so there is nothing to install on your machine.
Setup
Three steps, in the order they have to happen
You cannot add the connector before there is an account, and you cannot get an answer before a property is connected. That is the only reason these are numbered.
- 01About two minutes
Connect your properties
Sign in with Google from your Murkuz account and pick the Search Console and Analytics properties you want. Bing Webmaster is a separate connection, and it takes a key rather than a sign-in.
- Google's consent screen is the slow part of the whole setup. It names Murkuz and lists the access in Google's own words before you agree to anything.
- Bing Webmaster issues one API key, under Settings and then API Access. Paste it into Murkuz once and it covers every property verified on that Bing account.
- Free connects Search Console on one site. Analytics and Bing Webmaster are refused at connect time until you are on a paid plan, and the refusal says so.
- 02About one minute
Add Murkuz as a connector
Paste one URL into Claude or ChatGPT and approve it. Any other MCP client takes the same URL as an MCP server. Nothing to install, and no local server to keep running.
- The URL is https://murkuz.com/mcp, and it is the same address for everyone. Your account is resolved by who signs in, not by the link.
- Approving opens a Murkuz sign-in. Enter your email, confirm the one-time code, and the window hands you back to your agent. If you are already signed in to Murkuz in that browser, it goes straight through.
- One connector covers every site on the account, not one per property.
- 03From here on
Ask, and stop logging in
That is the whole setup. Ask your questions in the window you already work in. The web app is there to change what is connected, and most people do not open it again.
- You never type a tool name. Your agent reads the list, picks what fits the question, and hands you back real rows from your own accounts.
- Every answer carries which property it came from, which window, and how fresh the numbers are.
- A long answer says how many rows exist and how to ask for the next page, instead of quietly cutting at fifty.
The connector URL, if you would rather copy it from here than from the app: https://murkuz.com/mcp
Access and trust
What Google asks for, and what it does not
The consent screen is the one place in this setup where you hand something over, so it is worth reading rather than clicking through. Everything below is what it grants.
- Analytics is read-only. Murkuz reads reports and cannot change a property, a data stream or a setting.
- Search Console covers reading your performance data and submitting a sitemap. That submission is the only change Murkuz can make at Google, and only when you ask for it.
- Murkuz never asks for a Google password. The token belongs to your Google account, and you can revoke it from your own third-party access settings at any time, without telling us.
- Murkuz cannot see a property you have not connected. Picking two properties out of nine grants access to two.
Bing Webmaster has no consent screen. It issues one API key from its own settings, you paste that key into Murkuz, and deleting the key ends the access. Everything on all three sources runs through the official APIs with your own permissions.
Built for more than one site
One connector, every site you run.
You approve Murkuz once in your agent, and that approval covers the whole account rather than one property. If you run one site, this is a convenience. If you run twelve, it is the reason to bother.
One approval, not one per site
Search Console shows you one property per view. The connector takes the whole account, so a roster question is one call and one answer.
New sites need no reconnection
Connect a property in the web app next month and it is simply there in the next question. Nothing to reconfigure on the agent side.
One site or all of them, same question
Ask about murkuz.com, or ask which of your sites grew fastest last quarter. The shape of the question does not change.
Plans differ on two things: how many sites you can connect, and how much external research you can run. Free and Solo both cover 1 site, because the first paid step connects Analytics and Bing Webmaster and puts a research budget behind them rather than buying properties. Sites are what the rungs above that buy, 3 of them or 10. See the caps and the credit grants on the pricing page.
Your first question
Ask in your own words. Your agent picks the tool.
A good first question names a site, a window and what you want ranked. “Which pages lost the most clicks in the last 28 days compared with the 28 before” beats “how is my SEO”. Your agent can follow up, so you do not have to get it right the first time.
Which sites do I have connected, and what is wired up on each?
See every site you have connected
My_SitesHow current is the Search Console data on my sites?
Check how fresh the numbers are
Data_Sync_StatusShow me clicks and impressions by query for the last 28 days.
Pull your raw Search Console numbers
Search_AnalyticsWhere am I sitting just off page one?
Find the keywords you are nearly ranking for
Live_Quick_WinsGive me a health check across all my sites.
Get every site you run in one answer
All_Sites_Overview
On Free, 16 of the 32 tools answer, because Search Console is the only source connected. The other 16 return a reason explaining what is not connected, rather than a zero that would read as bad news about your site. The whole list is on the tool reference.
If something is missing
The things that actually go wrong
Nearly all of them are a property that is verified somewhere else, or a source that is not connected yet. Neither is a broken setup.
Search Console only offers properties the Google account you signed in with is verified on. If the site was verified under a different account, sign in with that one, or have an owner add your account in Search Console first. Domain properties and URL-prefix properties are listed separately, so pick the one that actually holds the data you want.
You need at least read access on the GA4 property, and that is granted inside Analytics under property access management, not here. A property you can only reach through a different Google account will not appear until you connect with that account.
Only properties verified in Bing Webmaster Tools appear against the key. Verify the site in Bing first, then reconnect. One key covers every verified property on the account, so there is nothing to add per site.
That is deliberate, and it is the answer we prefer. A tool that cannot reach a source returns a reason explaining what is not connected, rather than a zero that would read as bad news about your site. Connect the source, or ask something the connected sources can answer.
No. One connector covers every site on the account. Add the property in the Murkuz web app and it is available in the next question, with no second approval in Claude or ChatGPT.
Yes. Any MCP client takes the same URL as an MCP server. The 32 tools are identical whichever client you use, and so is what each one costs.
No. There is a permanent Free plan instead: one site, Google Search Console, no card and no expiry. If you want to look before connecting anything at all, the Sandbox is a read-only demo account on sample data.
Revoke Murkuz from your own Google account's third-party access settings, or remove the connection in the Murkuz web app. Deleting the Bing key removes Bing access. Nothing keeps running on your machine afterwards, because nothing was installed on it.