The Murkuz MCP server gives Claude, ChatGPT, Cursor and any other MCP client the Search Console, Analytics and Bing Webmaster data for every site you connect. Paste one URL, sign in once, and ask in your own words.
Server URL
https://murkuz.com/mcpRemote server, streamable HTTP, OAuth 2.0 sign-in. Nothing to install.
Updated
What it is
The Murkuz MCP server is a hosted Model Context Protocol server that connects AI assistants to your own Google Search Console, Google Analytics 4 and Bing Webmaster Tools data. You connect those accounts to Murkuz once. Your agent then calls Murkuz tools to read clicks, impressions, positions, sessions and conversions for every site on your account.
We hand over the rows, not our opinion of them. You are already paying for a model that reads a table better than a summariser would, and it can follow up, cross-reference and change its mind. You never type a tool name. You ask, and your agent picks.
“MCP (Model Context Protocol) is an open-source standard for connecting AI applications to external systems.”
A long answer says how many rows exist and how to ask for the next page, instead of quietly cutting at fifty.
Each response carries which property it came from, which window it covers, and how fresh the data is.
A source that is not connected says so, rather than reporting zero traffic and letting you draw the wrong conclusion.
Setup
To set up the Murkuz MCP, connect your properties in the Murkuz app, then add https://murkuz.com/mcp to your AI client and sign in. Connecting means signing in with Google, picking your Search Console and Analytics properties, and pasting a Bing Webmaster API key if you use Bing.
claude.ai, Claude Desktop and the mobile apps
https://murkuz.com/mcpThe terminal and IDE extensions
/mcp, pick murkuz and choose Authenticate.claude mcp add --transport http --scope user murkuz https://murkuz.com/mcpA custom connector in developer mode
https://murkuz.com/mcpmcp.json, or the MCP section of Cursor's settings
{
"mcpServers": {
"murkuz": {
"url": "https://murkuz.com/mcp",
"headers": {
"Authorization": "Bearer sk_live_your_key_here"
}
}
}
}Perplexity, agents, and anything that speaks remote MCP
https://murkuz.com/mcpStuck on a step? The Help Center covers the common snags, such as a property that does not appear after Google sign-in.
Access and permissions
The Murkuz MCP server can read your connected Search Console, Analytics and Bing data, and it can submit a sitemap to Google when you ask. That is the whole list. It works through the official APIs, with the permissions you already hold, over an MCP OAuth sign-in.
Your client signs in with OAuth 2.0 on a Murkuz page you can see. It receives a token for your Murkuz account and never sees your Google password.
Murkuz cannot see a property you have not connected, and every answer names the property, the date window and how fresh the data is.
It asks Google to recrawl a sitemap you already publish, and only when you ask for it. Nothing edits your pages, your Search Console settings or your Analytics.
8 research tools look outside your accounts and use research credits. Your agent can check the balance first, so a sweep is priced before it runs.
Remove Murkuz from your client to cut the agent off. Revoke Murkuz from your Google Account permissions to cut Murkuz off from Google as well.
“https://www.googleapis.com/auth/webmasters: Read/write access. https://www.googleapis.com/auth/webmasters.readonly: Read-only access.”
| Source | Access asked for | What Murkuz does with it |
|---|---|---|
| Google Search Console | Read and write Reads performance, index status and sitemaps. Writes only through Submit_Sitemap, because Google has no narrower permission that allows a sitemap submission. | Reads performance, index status and sitemaps. Writes only through Submit_Sitemap, because Google has no narrower permission that allows a sitemap submission. |
| Google Analytics 4 | Read-only Reads sessions, engagement and conversions per page, and joins them to Search Console. | Reads sessions, engagement and conversions per page, and joins them to Search Console. |
| Bing Webmaster Tools | API key you paste once Reads your Bing clicks, impressions and positions for every verified site on that account. | Reads your Bing clicks, impressions and positions for every verified site on that account. |
The whole surface
The Murkuz MCP server has 32 tools in 7 groups, and 24 of them never cost a credit because they read your own accounts. Every account gets the same 32 tools. What a plan changes is which sources you can connect and how much research you can run, never which tools you get.
What is connected, and how fresh it is. Where an agent starts before it asks anything else.
My_SitesSite_DetailsData_Sync_StatusYour own Google Search Console data, read live from Google on every call. Never metered.
Search_AnalyticsKeyword_RankingsInspect_URLLive_Quick_WinsLive_CTR_OpportunitiesLive_Traffic_DropsLive_Content_DecayLive_CannibalizationThe other two sources, on their own terms. Also your own data, also never metered.
Site_AnalyticsBing_Search_PerformanceThe questions neither tool can answer alone, because the answer needs both sides of the visit.
Page_Search_To_BehaviourOpportunity_MatrixSearch_To_RevenueLanding_Page_DiagnosisTraffic_Health_CheckThe reason the connector is worth having when you run more than one property. One question, every site.
All_Sites_OverviewPortfolio_ComparisonRead and change what Google has been told to crawl.
List_SitemapsSubmit_SitemapSEO_InsightsThe only group that looks outside your own accounts, so the only group that costs credits. Nothing here runs without your say.
My_Data_CreditsKeyword_MetricsKeyword_IdeasSERP_SnapshotCompetitor_GapBing_Keyword_MetricsBing_Keyword_IdeasBing_Keywords_For_URLBing_Site_KeywordsIn practice
Once the Murkuz MCP is connected, you ask in plain English and your agent picks the tool that answers. Copy any of these. The chip under each one is the tool your agent will reach for.
“Give me a health check across all my sites.”
All_Sites_Overview“Where am I sitting just off page one?”
Live_Quick_Wins“What dropped this month compared with last month?”
Live_Traffic_Drops“Which search terms end in revenue, not just visits?”
Search_To_Revenue“Are two of my pages fighting over the same query?”
Live_Cannibalization“What are my top Bing queries this quarter?”
Bing_Search_Performance“Is this page indexed, and which URL did Google pick as canonical?”
Inspect_URL“Submit my new sitemap to Search Console.”
Submit_SitemapQuestions
It is a hosted Model Context Protocol server at https://murkuz.com/mcp. It connects Claude, ChatGPT, Cursor and any other MCP client to your own Google Search Console, Google Analytics 4 and Bing Webmaster Tools data, so you can ask about every site you run in plain words and get real rows back.
https://murkuz.com/mcp. It is the same URL in every client and for every site on your account. Clients that sign in with OAuth need nothing else. Clients that only accept a header use a Murkuz API key you create in the app.
No. Murkuz is a remote server over streamable HTTP, so there is nothing to download, no package to install and no local process to keep running. You add the URL to your client and sign in.
Claude on the web, desktop and mobile, Claude Code, ChatGPT through a developer mode connector, Cursor, Perplexity, and any other client that supports remote MCP servers. Every client gets the same 32 tools.
One tool writes: Submit_Sitemap, which asks Google to recrawl a sitemap you already publish, and only when you ask. The other 31 tools read. Murkuz does not edit pages, change Search Console settings or touch your Analytics configuration.
No. You sign in with Google inside Murkuz and pick the Search Console and Analytics properties to connect. Bing Webmaster Tools is the one exception: you paste a Bing API key once, and it covers every verified site on that Bing account.
32 tools in 7 groups. 24 read your own accounts and never cost a credit. The 8 research tools look outside your accounts and use research credits. The full list, with an example question for each, is on the Murkuz MCP tool reference.
Yes. One connector covers every site on your Murkuz account, and All_Sites_Overview answers about all of them in a single question. How many sites you can connect depends on your plan.
Remove Murkuz from your client's connector or MCP settings. That stops the agent reaching the server and leaves your connected properties untouched. To remove Murkuz's access to Google itself, revoke it from your Google Account permissions page.
Sign in with Google, pick your properties, and paste https://murkuz.com/mcp into the client you already use. Every site you run, through one connector.