·7 min read·
Meta Muse
Agents
Guide

Connect Google Search Console to Meta Muse

Connect Google Search Console to Meta Muse: ask Muse for a Custom Connector to our MCP URL, sign in with Google, then query your real clicks and rankings.

To connect Google Search Console to Meta Muse, open a Muse chat and ask it to create a Custom Connector for the remote MCP server https://mcpsearchconsole.com/mcp, then sign in with Google when Muse asks. If the sign-in doesn't complete, generate a setup token on your account page and hand it to Muse through its secure credential prompt. After that, Muse can read your real queries, pages, positions and index status and answer SEO questions from them.

Muse has no "add MCP server" form like Claude or ChatGPT. You describe the server in plain words and Muse builds the connector itself. That makes the first message matter more than usual, so the exact message is below, along with the fallback, the permission settings we'd use, and what we have not been able to confirm yet.

What Meta Muse is

Meta Muse is Meta's agent app, launched on 8 September 2026. It runs on iOS, Android, the web at muse.ai and inside WhatsApp, and at launch it is open to adults in the US only. It is an agent rather than a chat window: it plans multi-step tasks, connects to other services and asks for approval before sensitive actions. There is a free plan (a payment card is required), Power at $20 a month and Maximum at $100 a month. Built-in connectors live under Settings → Connectors; anything not in that list goes through a Custom Connector, which is how our Search Console MCP server gets in.

What Muse needs from an MCP server

  • A public HTTPS URL over streamable HTTP. Muse runs in Meta's cloud, so it cannot start a local stdio server or reach localhost. The open-source "clone a repo and run it on your laptop" Search Console servers are out. A hosted server is the only practical route, and https://mcpsearchconsole.com/mcp is one.
  • A connector you ask for in chat. Meta's help center says that for a service not in the Connector list, "you can ask Muse to create a Custom Connector." Muse then writes an MCP client, lists the server's tools, tests them and saves the result as a reusable skill that later conversations can use.
  • Credentials outside the chat. When a connector needs a key, Muse opens a secure credential prompt that is separate from the conversation. Anything you paste into the chat itself stays in your history, so tokens never go there.

Connect Google Search Console to Meta Muse, step by step

  1. Start a new Muse chat and paste this message as written:
Create a Custom Connector for a remote MCP server, then connect to it:
Name: Search Console
Transport: remote streamable HTTP
URL: https://mcpsearchconsole.com/mcp
Auth: OAuth
  1. Sign in with Google when Muse asks. Pick the Google account that has access to your Search Console properties and approve the read-only Search Console scope. You do not need a Google Cloud project or API key.
  2. Let Muse finish. It should list the tools it found (list_sites, search_analytics, search_insights, inspect_url and the rest) and save the connector as a skill.

Some guides also describe Settings → Connectors → Add custom connector, where you paste the URL. Others say that screen only lists Meta's built-in connectors. If you see the button, the URL above is all it needs. If you don't, the chat route is the one Meta documents.

Fallback: the setup token

OAuth inside the Muse app is reported to work, but with more back-and-forth than in Claude or ChatGPT, and we have not been able to run that hand-off ourselves. If the Google sign-in stalls or Muse says it can't authenticate:

  1. Sign in with Google here and click Generate setup token on your account page. Copy it straight away: it is shown once, and generating a new one replaces the old one.
  2. Ask Muse to change the connector's auth to a bearer token. When the secure credential prompt opens, enter Bearer <your token> as the Authorization value.
  3. Never paste the token into the chat. If you do by accident, generate a new one, which kills the old one.

OAuth first, token second. The token route works, but it is a static secret you now have to look after, while the OAuth route can be revoked from your Google account.

Set the connector's permissions

In Muse's settings a connector can be read-only, require approval for every action, or be allowed to act. Most of what this server does only reads, but a few tools change something, and those are the ones to keep behind approval:

  • submit_sitemap and delete_sitemap change the sitemaps registered for your property in Google. They only work after you grant the optional write permission yourself from your account page; by default the connector is read-only toward Google.
  • add_note saves a note on your account here (never in Google). On a Team plan the whole team sees it, so an agent writing notes unprompted is worth a look first.

Our setup: approval on for the whole connector at first, then allow the read tools once you trust what Muse does with them.

Check it works

First promptUse the Search Console connector to list my properties, then give me clicks, impressions, CTR and average position for the first one over the last 28 days.

Muse should call list_sites, then search_analytics, and come back with your properties named exactly as Search Console names them (sc-domain:example.com or https://example.com/), then four totals for the 28 days ending about two days ago. Search Console data trails by roughly two days, so an empty "yesterday" is normal. Listing properties is free; the performance query counts as one data pull.

Prompts to try in Muse

Each one works as written. Replace the property with yours, or let Muse pick it from list_sites.

Striking-distance keywordsRun search_insights with the striking_distance recipe on sc-domain:example.com for the last 28 days. Group the queries by page and tell me which three pages to improve first, and why.
What droppedCall list_notes first for context, then use search_insights with the movers recipe to compare the last 28 days with the 28 days before. For the five pages that lost the most clicks, say whether the drop came from position, CTR or demand.
Index checkPull my ten most-clicked pages from search_analytics, run inspect_url on each, and check list_sitemaps for errors. Only report pages that are not indexed or whose Google-selected canonical differs from mine.
Technical sweepOn example.com, run check_redirects, check_robots, check_tls and check_dns, then page_speed on the homepage. Tell me only what needs fixing.
Low-CTR titlesUse search_insights with the low_ctr recipe and draft a better title tag and meta description for the top five pages. Do not save anything, just show me the drafts.

The last line of that prompt is deliberate. Muse is an agent and will take the next step if it thinks you want it; when you only want an answer, say so.

Limits

  • US-only, adults-only at launch. Some guides mention Canada too. If Muse isn't open in your country, nothing on our side changes that.
  • The OAuth hand-off is unconfirmed. We have not run the Muse sign-in end to end, and reports call it fiddly. The setup token exists for exactly this case.
  • No Meta review. Meta doesn't review custom connectors, and this server is not an official Muse connector. It works with Meta Muse the same way it works with any client that speaks remote MCP; Meta has not reviewed or endorsed it.
  • Two meters. Muse counts custom connector use against the same usage meter as everything else on your Muse plan. On our side, the free plan allows 15 data pulls a day and 40 a month on one Search Console property. Listing properties, notes and the DNS, redirect, robots.txt and TLS checks never count. Solo (€4.99 a month) removes the pull caps and covers 5 properties; Team (€29.99 a month) has no property limit. Details on the pricing page.
  • Read-only toward Google by default. It cannot edit your site, change Search Console settings or request indexing. The only writes to Google are the two sitemap tools, after you opt in.
  • Search Console's own limits apply. Data lags about two days, anonymized queries are hidden, and history goes back 16 months.

Using Muse Code instead?

Muse Code, Meta's terminal agent, is a separate product with a normal config file. Add the server to the mcpServers block in ~/.config/muse/settings.json (the file needs "schema_version": 1) as a streamable HTTP server with the URL above, then run muse mcp login with the name you gave it to sign in with Google over OAuth.

Also available for Claude, ChatGPT, Grok, Cursor, Claude Code, Codex and Mistral.

Troubleshooting

Muse says it can't reach the server

Check the path: it is /mcp, not the home page. Then check the transport in your message says streamable HTTP. If Muse asked whether the server runs over stdio, the answer is no.

The Google sign-in opens but Muse never finishes connecting

Use the setup token route above. The token stands in for the sign-in you already completed in your own browser.

FAQ

Can I connect Google Search Console to Meta Muse?

Yes, as a Custom Connector. Ask Muse in chat to create one for the remote MCP server https://mcpsearchconsole.com/mcp and sign in with Google, or use a setup token through the secure credential prompt.

Is there a Meta Muse MCP setting?

Not a manual one in the app, as far as current guides describe. Muse builds the MCP client itself when you ask for a Custom Connector. Muse Code is different and reads servers from its settings file.

Can Muse change my site or my Search Console settings?

No. The connection is read-only toward Google unless you grant the optional sitemap write permission, and even then it can only submit or remove sitemaps. Keep approval on for those tools in Muse.

Does Google Search Console have an official MCP?

We could not find one from Google. Third-party servers use the public Search Console API; our best hosted Google Search Console MCP servers page compares the hosted ones, which are the only kind Muse can use.

Go further

If your team also works in other assistants, the Claude guide, ChatGPT guide and Grok guide cover the same server there. For recurring checks rather than one-off questions, scheduled SEO checks shows the prompts we run every week, and the use-case library has a page for each prompt above.

Ready to put your search data in your AI?

Set up the Search Console MCP, free

Free plan included. See pricing