Give Meta Muse your real Google Search Console data. The GSC Wizard connector lets Muse answer SEO questions from actual clicks, impressions, average position and CTR, and run ranking, decay and cannibalization analysis for you, instead of guessing from the open web.
MCP server URL: https://mcp.gscwizard.com/mcp
The short answer
Three steps, about three minutes:
https://mcp.gscwizard.com/mcp.After that, ask Muse about your site in plain language: “which pages lost clicks this month?” is answered from Search Console, not from a guess.
GSC Wizard has been submitted to the Muse Connector platform, where Meta reviews every directory connector for functional, security and legal requirements before it appears in the Muse connector list. Meta is onboarding its first developers in waves, so the one-tap directory version is not live yet. You do not have to wait for it: Muse can build a custom connector from our MCP server today, and that is exactly what the steps below do. When the directory listing goes live, this page will be updated with the one-tap route.
Muse is Meta’s personal AI agent, launched in September 2026 on iOS, Android, Mac and the web at muse.ai. Each Muse agent runs on its own cloud machine, with a second agent called Sentinel checking everything that leaves it for the internet.
A connector links Muse to an app or service so the agent gains a new ability, such as reading a calendar or sending an email. There are two kinds. Directory connectors are submitted by developers through the Muse Connector platform and reviewed by Meta. Custom connectors are ones Muse builds for you on request: you give it an MCP server URL or API docs, it writes and tests the integration, and saves it as a skill it can reuse in later conversations.
Out of the box, Muse can search the web, but it cannot see your Search Console account. Ask it why traffic dropped and the best it can do is speculate. With the Search Console SEO connector it reads the same data you see in Search Console, across every property you have connected, and answers with numbers.
There is no settings screen for custom connectors in Muse: you ask for one in a normal conversation. GSC Wizard is a hosted MCP server, so there is nothing to install or run on your side.
Sign in at tool.gscwizard.com with Google and connect the Search Console properties you want Muse to read. The connector only ever sees properties already connected to your account.
Go to Account → API keys and create a key with the read only scope. Copy the gscw_live_… value: it is shown once.
Open Muse on your phone, Mac or at muse.ai and paste the prompt below. It names the service, gives Muse the MCP server URL https://mcp.gscwizard.com/mcp, and says what you want to be able to do.
Muse asks whether the server uses HTTP or stdio and how it authenticates, then opens its secure credential prompt. Paste the key there, never in the chat.
Muse calls each tool once to check it works and saves the integration as a skill. Start with “list my Search Console properties” to confirm it is reading the account you expect.
Paste this into Muse
Build a custom integration to GSC Wizard, my Google Search Console
analytics service. Its MCP server URL is https://mcp.gscwizard.com/mcp
(remote HTTP, Bearer token auth). I want you to be able to answer SEO
questions about my websites from real Search Console data: clicks,
impressions, CTR, average position, ranking changes, decaying pages,
keyword cannibalization and URL indexing status.
Rules: always state the date range you used, treat a lower average
position as better, and never call a write tool unless I ask for it.When Muse asks how the server is reached, the answer is remote HTTP (not stdio), authenticated with a Bearer token in the Authorization header.
Never paste the key into the chat itself. Wait for Muse’s secure credential prompt. Keys entered there go to a credential store outside the agent, and Sentinel swaps in the real key only when a request leaves Muse’s machine, so the agent never sees it. A key typed into a message is just text in your conversation history.
In Claude, ChatGPT and Grok the GSC Wizard connector signs you in with OAuth: a browser window, a consent screen, done. A Muse custom connector is built by an agent running on a cloud machine, and a static bearer token fits its credential store much more cleanly than a browser redirect. So for Muse you create a key once and hand it over through the credential prompt.
That is also the safer setup. Keys carry a scope: a read-only key physically cannot call a write tool, whatever the agent decides to try. Keys are shown once, can be revoked at any time under Account → API keys, and every write made with a read-and-write key is audit-logged.
The connector exposes the full GSC Wizard MCP. These are the ones Muse reaches for most in SEO conversations.
list_sites
Every Search Console property connected to your account, so Muse picks the right one.
get_site_summary
Clicks, impressions, CTR and position for a period, compared with the one before.
query_top_queries / query_top_pages
Your best-performing queries and landing pages, with full metrics.
get_ranking_changes
Queries and pages that gained or lost the most, ranked by click impact.
find_decaying_content
Pages losing traffic over time, diagnosed, with refresh candidates first.
analyze_cannibalization
Queries where several of your pages compete, triaged by severity.
analyze_ctr_curve
Your own CTR per position, to spot titles and snippets that underperform.
score_opportunities
Near-page-one queries ranked by estimated click upside.
inspect_url / bulk_inspect_urls
Google’s live index status for a URL or a batch of them.
The same connector also covers Bing Webmaster data and GA4. For the analytics side, see the Google Analytics Muse connector.
Every analysis runs server-side, so Muse reads a finished result instead of doing arithmetic over raw rows.
Check the URL first: it is https://mcp.gscwizard.com/mcp, with the /mcp path; the bare domain serves the documentation site, not the protocol. A 401 means the key was not sent or was revoked: ask Muse to re-enter the credential through the secure prompt. If tools answer with “not configured”, the property is not connected in GSC Wizard yet: add it there and ask again. Custom connectors count against the same Muse usage allowance as everything else you do in Muse.
The Muse connector uses the same MCP server as every other assistant, so one GSC Wizard account covers all of them.
Sessions, key events, revenue and AI referral traffic from GA4, in Muse.
Read the guideAdd a custom connector in the Claude app, or one command in Claude Code.
Read the guideThe App Store app, a custom developer-mode connector, or the Responses API.
Read the guideThe endpoint, both auth modes, and copy-paste configs for every client.
Read the guideSee also the Google Search Console MCP overview, the GA4 MCP, the Grok guide, and our roundup of the best SEO MCP servers.
Yes. GSC Wizard works with Muse today as a custom connector: ask Muse to build an integration to https://mcp.gscwizard.com/mcp and hand it a GSC Wizard API key through the secure credential prompt. GSC Wizard has also been submitted to the Muse Connector platform directory, which Meta is opening to developers in waves.
No. Muse’s launch connectors cover things like Gmail, Google Calendar, Google Docs and Outlook, but not Search Console. Without a connector Muse can only search the web, so it cannot see your own clicks, impressions or rankings.
Muse builds custom connectors itself from a cloud machine and stores credentials in a secure store, which fits a static bearer token. Your Google sign-in stays with GSC Wizard; Muse only ever holds a GSC Wizard key, which you can scope to read-only and revoke at any time.
Not with a read-only key. A read key physically cannot call a write tool, such as submitting a sitemap or sending URLs to IndexNow. If you create a read-and-write key instead, every write is audit-logged.
No. Reads come from a data warehouse holding the full row set, so there is no 1,000-row export cap and no API paging. The data lags Search Console by roughly two days, and each response says which date it is complete through.
GSC Wizard has a free plan, and the MCP is included. On the Muse side, custom connectors use the same usage allowance as anything else you do in Muse.
Everywhere Muse runs: iOS, Android, Mac and the web at muse.ai. The connector is saved to your Muse account as a skill, so you set it up once.
Connect your properties, create a read-only key, and ask Muse about your rankings in plain language.
Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.