What Muse can see
In GA4, Muse can list your properties and pull a traffic overview (sessions, users, page views, engagement), traffic by default channel group, acquisition by source, medium and campaign, top pages, landing pages with engagement and conversions, conversion events, ecommerce revenue and item performance, device and geographic breakdowns, new versus returning users, events, audiences and real-time active users. When the ready-made reports are not enough, it can run a custom report with any dimensions and metrics your property accepts, and list which ones those are. The GA4 MCP page covers the GA4 side in more detail.
In Search Console, Muse can list your sites and pull search analytics, top pages, top queries with clicks, impressions, CTR and average position, the queries behind a specific page, country, device and search-appearance breakdowns, a day-by-day trend, and a side-by-side comparison of two date ranges. It can also inspect a URL for indexing status, list sitemaps, and show URL coverage with a sample of indexed pages.
Connect it in 30 seconds
Muse has no connector settings screen, so there is nothing to click through. You send it one message that says where MCP Ads is. Muse replies with a sign-in link, you approve it, and Muse tests the tools and saves them for later conversations and scheduled checks.
Connect Google Analytics and Search Console under Connections in the MCP Ads dashboard. They share one Google sign-in with Google Ads, and each asks for its own permission.
If Muse asks for a credential instead of sending a link, create an API key in the MCP Ads dashboard under Connect MCP → API keys and paste it into Muse's secure credential prompt, not into the chat. If it asks for a client ID or client secret, leave both empty. MCP Ads is not in Muse's connector directory yet, so this message is the way in; the Muse setup page has the same steps.
Paste these lines into Muse as a single message:
- Add my MCP Ads connector: https://mcp-ads.com/mcp-slim
- Setup: standard MCP over streamable HTTP with OAuth. Send me the sign-in link and I will approve it. Keep one session (Mcp-Session-Id) for all calls.
- Skill: save one so every question about my ads, analytics or SEO goes through MCP Ads tools first.
- Once you are in, list my GA4 properties and Search Console sites, and tell me the landing page whose conversions fell most last month.
Checks worth scheduling
Both tools are mostly read-only, which makes them a good first place to let Muse run unattended. Give each check a threshold so a normal week produces a short note or none at all.
| Check | Source | Report only when (illustrative) |
|---|---|---|
| Traffic by channel | GA4 | A channel's sessions moved more than 20% week on week |
| Landing page conversion | GA4 | A top-10 landing page lost a third of its conversion rate |
| Page-two keywords | Search Console | Queries at position 5 to 15 with over 500 impressions |
| Ranking drops | Search Console | A query that brought clicks fell more than 3 positions |
| Indexing | Search Console | A key page is no longer reported as indexed |
Prompts that work
Name the property or site, give a date range, and say whether you want completed weeks.
- Show queries where we rank 5 to 15 with over 500 impressions, and which page to improve for each.
- Compare the last 28 days with the previous 28 in Search Console and list pages that lost the most clicks.
- Which GA4 landing pages had the most sessions and the lowest engagement rate last month?
- Break down last month's conversions by source, medium and campaign, and show which paid campaigns sent traffic that did not convert.
- Inspect our pricing page URL and tell me whether Google has it indexed.
- Every Monday at 9, compare last week with the week before in GA4 and Search Console and send me the three biggest changes.
- On the first of every month, list Search Console queries that moved onto page one and those that fell off it.
Traps in the data
GA4 and Search Console measure different things. Search Console counts clicks from Google search results; GA4 counts sessions on your site, and only for visitors whose browsers let it record them. The two will not match, and a scheduled check should compare each against its own history, not against the other.
Search Console data arrives a few days late, so the last day or two of any range looks low. Average position is an average across every query and country, so a page can "drop" because it started appearing for new, weaker queries. And leads that never visit your site, such as Meta instant-form leads, will never appear as GA4 conversions; judge those in the ad platform.
What it will not do, and honest limits
In this setup the GA4 tools only read. In Search Console, Muse can submit or remove a sitemap and nothing else; it cannot change your site. For site changes, Muse can prepare a list of pages and fixes for you or your developer. Changes on the ad platforms go through MCP Ads approval controls. Muse sees only the properties and sites your Google login can reach and that you connected in MCP Ads.
Every tool call counts against your Muse usage, and a query-level Search Console pull across a large site is several calls, so ask for the top rows you will act on. MCP Ads costs a free trial, then $49/month flat; see pricing. For a longer walkthrough, read Search Console with Claude; the same checks apply to Muse.
