The short version
- →Muse is a consumer AI agent. Advertisers are not its audience and it has no Ads Manager access.
- →Meta opened developer connectors on 18 September. That is the only route by which ad data could reach it.
- →Connector access is a waitlist, and whether you can reuse an existing MCP server is undocumented.
- →If you want to ask an agent about your ad spend today, a client that speaks MCP does it now — no waitlist.
1. What Muse is
Muse is Meta’s personal AI agent, announced in September 2026. It is described as a secure, private agent that proactively helps with people’s goals and suggests ideas, built to work for billions of people with no technical experience required.
What separates it from a chatbot is that it acts. Muse can open a browser, fill out forms, send an email, book travel, negotiate on someone’s behalf and check out with Link. It remembers preferences and makes suggestions unprompted. It runs on iOS, Android, muse.ai and inside WhatsApp, with AI glasses coming, and it is rolling out in the US on free and subscription tiers.
On 18 September Meta opened Muse to developer-built connectors. A connector turns an existing API into tools Meta AI can call: you register REST endpoints through a guided UI or MCP onboarding, connect user accounts with OAuth, and test before launch. No new SDK, no separate app. Spots are limited and developers are selected in waves.
2. What it cannot do on its own
Muse is built for personal tasks, and the gaps for a marketer follow directly from that. Five things it does not do:
It has no ad-account access
There is no native Ads Manager connection and no advertiser-facing controls. Muse cannot read your campaigns, and nothing in the product suggests it is meant to.
It is deliberately walled off from Meta’s ad systems
Meta states that Muse does not share a person’s conversations or the data in their virtual machine with Meta’s ad systems. That is a privacy commitment to users, and it also tells you which direction the product faces.
The connector programme is gated
Access is a waitlist with limited spots, and Meta selects developers in waves based on readiness and alignment. You cannot simply ship a connector this week.
Reusing an existing MCP server is undocumented
MCP appears among the connector development tools, but Meta does not say whether you can point Muse at an MCP server you already run or whether a connector must be registered separately. Anyone telling you definitively is guessing.
Marketing is not a named use case
The suitable services Meta lists are fitness, productivity, entertainment and smart home. Advertising is neither named nor prohibited, which means nobody yet knows how an ads connector would be reviewed.
Taken together: Muse is a capable agent pointed at consumer life. Getting it to answer a question about your CPA is a connector problem, and the connector door has only just opened a crack.
3. Where GoMarble comes into the picture
Muse is missing one thing that matters here: a path to your ad accounts. GoMarble already is that path for other agents, which makes the gap concrete rather than theoretical.
| Piece | Muse supplies | GoMarble supplies |
|---|---|---|
| The conversation | Agent, planner, executor | — |
| Ad-platform data | — | Meta, Google, TikTok, LinkedIn, Bing, Shopify, GA4, Klaviyo |
| Analysis of that data | — | Root-cause analysis, creative analysis |
| Changes in the account | — | Agents execute, gated on approval |
| The bridge between them | Connector programme (waitlisted) | Existing API + MCP servers |
The honest position is that the bottom row is the whole story, and it is not finished. Meta’s connector model wants an API it can call on a user’s behalf, which is a shape GoMarble already has. Whether that becomes a Muse connector depends on programme access and on how Meta reviews an advertising service — neither of which is settled.
To be clear about what exists today: GoMarble has no Muse connector, and we are not claiming a place in the programme. What we do have is the same capability working now through clients that speak MCP.
4. What you can do
Worth separating sharply, because most coverage of Muse does not.
Works today, no waitlist
If the goal is asking an agent about your ad performance in plain language, that already works — just not in Muse. Point a client that supports MCP at GoMarble’s hosted servers and you can ask why ROAS moved last week, which creatives are fatiguing, where budget is constrained, or what a search-term report is hiding. GoMarble AI Agents can then execute the change with approval. Muse Image in Advantage+ is the other thing available now, and it is creative generation rather than analysis.
Becomes possible if connector access lands
If an ads connector is approved and the scopes allow it, the interesting part is not new capability but new surface. Muse lives in WhatsApp and on a phone, which is a materially different place to check an account from than a dashboard — a question about yesterday’s spend answered in a thread, an alert you can reply to. That is a genuine shift in where paid-media work happens, and it is contingent on decisions Meta has not published.
What we would not do is promise it. Connector review for an advertising service is untested, the scopes are unstated, and building on an undocumented MCP path would be guesswork dressed up as a roadmap.
5. Why Muse is not yet the most useful tool for marketers
Muse is a consumer agent that has just started accepting connectors. For a paid-media team in September 2026, that adds up to very little you can act on:
It cannot reach your accounts
- No native Ads Manager connection and no advertiser controls
- Explicitly separated from Meta’s ad systems by design
- Connector access is waitlisted and selected in waves
- Whether an existing MCP server can be reused is undocumented
It is pointed at consumer life, not ad ops
- Named suitable services are fitness, productivity, entertainment, smart home
- Advertising is neither listed nor banned, so review outcomes are unknown
- Rolling out in the US only at launch
And the thing it would give you already exists
- Conversational access to ad data works now through clients that support MCP
- Execution with an approval gate works now
- What Muse would add is reach — WhatsApp, phone, glasses — not capability
None of this makes Muse unimportant. An agent with hundreds of millions of users that can act on someone’s behalf is a genuinely significant surface, and the connector programme is the thing to watch. But watching is the correct verb this quarter. Nothing about Muse changes what you should do to your accounts today.
FAQ
What is Meta Muse?
Can Muse manage my Meta Ads account?
What are Muse connectors?
Can I point Muse at an existing MCP server?
Is Muse available to advertisers now?
Does GoMarble have a Muse connector?
Is Muse the same as Muse Image?
What should a marketer do about Muse today?
Sources & methodology
Muse’s capabilities, availability, privacy position and the connector programme were reviewed on 28 September 2026 against Meta’s own announcement and developer documentation, linked below. Muse and the connector programme are both new and changing; connector scopes and review criteria for an advertising service are not published, and this page does not speculate about them. GoMarble has no Muse connector today.
- Muse announcement: about.fb.com — Introducing Muse
- Connector documentation: dev.meta.ai/products/connectors
- GoMarble MCP servers: gomarble.ai/ai-tools/mcp/
Read next
Same question, different model
Jev for paid media →
A decision model with the opposite problem — no interface at all, but genuinely useful for high-volume text judgment.
Available today
Ads MCP servers for Meta and Google →
The route that works now — conversational access to ad data through clients that already speak MCP.
Talk to your ad data without waiting for a connector.
GoMarble reads Meta, Google, TikTok and Shopify, explains what changed, and executes the fix with your approval. Connect in one click.