What are Meta Muse connectors?
Muse connectors are the integrations that let Meta’s Muse agent reach a service outside itself. Some are built by Meta with a provider and appear in the app; the rest are Custom Connectors, which you create by asking Muse to build one and giving it a public HTTPS endpoint. Meta does not review custom connectors, so the trust question is about the service on the other end rather than about Muse.
Every built-in connector, and what is missing
39 built-in connectors are live. The ones with a marketing job are in bold; the ones a marketer goes looking for — ad platforms, analytics, Search Console — are in the Sprites box, because none of them is built in.
- 1
Built-in
Settings › Connectors › Connect, or say “connect my Gmail”. Facebook, Instagram and Threads connect themselves if they share your Accounts Center.
ReviewedBuilt by Meta with the provider
ReachesGoogle Workspace, Outlook, Notion, Shopify Catalog, Spotify, OpenTable and the rest of the directory.
No ad platforms - 2
Directory
A developer submits a connector through Meta’s connector platform. Once approved, it appears in the list beside the built-ins.
ReviewedMeta checks function, security and legal terms, and tests it end to end
ReachesOpened to developers in September 2026 — over 1,500 applications in the first week. No ad platform has been listed yet.
No ad platforms - 3
Custom
Ask Muse in the conversation to create a Custom Connector and give it an entry point — an MCP server URL, or API docs it can read.
ReviewedNot reviewed. Meta says to grant access with caution
ReachesAnything with a public, hosted endpoint — including every ad platform behind Sprites.
Reaches ad accounts
Add with Sprites
- Google Ads
- Meta Ads Manager
- TikTok Ads
- LinkedIn Ads
- Reddit Ads
- Google Analytics 4
- Search Console
- Shopify Admin
None of these is built into Muse. One custom connector to Sprites adds every one.
Meta6
- FacebookReads saved content and context. Connected automatically; does not post.
- InstagramReads saved posts and context. Connected automatically; does not post.
- Threads
- Messenger
- Instagram & Threads messages
- Meta CatalogProduct catalog context — not Ads Manager, and not a campaign.
Google9
- GmailClient threads, sends a report as a draft.
- Google Calendar
- Google Contacts
- Google Tasks
- Google DocsBriefs and write-ups land here.
- Google Drive
- Google SheetsWhere a weekly ad report is written to.
- Google SlidesClient decks from a report.
- Google Forms
Microsoft3
- Outlook Mail
- Outlook Calendar
- Outlook Contacts
Work7
- NotionContent calendars and campaign briefs.
- Granola
- Calendly
- Telegram
- Tailscale
- GitHubAnnounced
- BoxAnnounced
Commerce8
- Shopify CatalogProduct data. Not the store’s orders, and not its ads.
- Shopify Checkout
- Link by Stripe
- Plaid
- Printify
- Shop PayAnnounced
- PayPalAnnounced
- 1PasswordAnnounced
Retail10
- WalmartAnnounced
- Best BuyAnnounced
- WayfairAnnounced
- SephoraAnnounced
- UltaAnnounced
- GapAnnounced
- American Eagle OutfittersAnnounced
- DICK’S Sporting GoodsAnnounced
- FanaticsAnnounced
- Michael KorsAnnounced
Life8
- OpenTable
- Ticketmaster
- Duffel
- Spotify
- Philips Hue
- Tessie
- ExpediaAnnounced
- InstacartAnnounced
Health5
- Apple Health
- Function Health
- HealthEx
- Withings
- Peloton
Meta Muse Connectors, answered
How do you add a connector to Muse?
Depends which kind. A built-in connector is added from Settings › Connectors, or by saying “connect my Gmail”. A Custom Connector has no settings form: you ask Muse in the conversation to create one, name the service and give it an entry point — an MCP server URL or API docs it can read. Muse builds the integration, tests it, and saves it as a reusable skill.
What can a Muse connector actually do?
Whatever the service behind it exposes. Muse reaches the endpoint, reads the tools it publishes and calls them when a request needs one. Through Sprites that means reading Google Ads, Meta Ads, Microsoft Ads, LinkedIn, TikTok, Reddit, GA4, Search Console and Shopify, and proposing changes to them — with every write held for your approval rather than applied by the agent.
Is there a connector for Google Ads or Meta Ads?
Not one Meta ships. Muse has no built-in connection to any advertising platform, and it cannot create an ad account it has never been given access to. A custom connector pointed at a marketing service is the route, and one connector covers every channel that service reaches rather than needing one per platform.
What does a Muse connector need technically?
A public HTTPS endpoint that speaks streamable HTTP. A server running on your own laptop is unreachable from Meta’s cloud, so localhost will not work. Static bearer tokens and API-key headers fit Muse’s secure credential prompt directly; an OAuth sign-in works but, by early testers’ accounts, takes more back-and-forth.
Are Muse connectors safe?
Meta does not review custom connectors, so safety is a property of the service you point Muse at rather than of the connector mechanism. The questions worth asking are whether it can act without you, whether it keeps a record of what it did, and whether revoking access actually stops it. Sprites answers those with an approval on every write, a log against the account and a grant whose revocation fails the very next call closed.
The message that connects it
A custom connector has no settings form — Settings › Connectors only lists Meta’s built-ins. Paste this into any Muse conversation and it builds the integration, tests it, and saves it as a skill.
Build a custom connector to Sprites, my marketing operator.
Its MCP server is https://mcp.sprites.ai/mcp — a hosted, public HTTPS endpoint that speaks streamable HTTP. Connect to it, sign in when it asks, then list every tool it gives you and show me the results.
Once it works, save it as a reusable skill called "Sprites" so I can ask you about my ads and my site from any conversation.Muse: Connected to Sprites. I can see your ad accounts, analytics and site. Ask me anything about them — I’ll bring changes back for you to approve before anything is applied.
What one connector reaches
Every channel below runs through the same endpoint and the same grant. Connect a platform once inside Sprites and the agent never touches a credential for it.
Where this stands
The same plain statement the main guide makes, because it belongs on every page that tells someone to paste something.
Live today
- The Sprites connector is live at https://mcp.sprites.ai/mcp, over streamable HTTP with OAuth.
- Thirteen other AI clients are connected to it today, with setup we have verified in each.
- Every channel below is reachable through that one endpoint right now.
Not verified yet
- Muse builds custom connectors from a hosted URL, which is exactly the shape we publish — but we have not yet walked a Muse setup end to end ourselves, so the message above is not a verified guide.
- Early testers report that an OAuth sign-in takes more back-and-forth in Muse than a static API key does. Sprites signs in with OAuth, and we are testing that handoff now.
Common questions
How many connectors does Muse have?
39 built-in connectors are live, with 17 more announced — most of them named at Meta’s September 23, 2026 Connect keynote, on top of the connector platform Meta opened to developers the same week. The number that matters for marketing is unchanged: none of them is an ad platform, and any service with a public MCP endpoint is reachable through one custom connector anyway.
What did Meta add to Muse’s connector list at Connect 2026?
Ten shopping connectors — Walmart, Best Buy, American Eagle Outfitters, DICK’S Sporting Goods, Fanatics, Gap, Michael Kors, Sephora, Ulta and Wayfair — plus GitHub and Box for work, Shop Pay alongside PayPal for checkout, and Expedia for travel, which Meta calls “coming soon.” Every one of them is commerce or productivity, and none of them is an advertising platform.
Can I remove a Muse connector?
Yes. You decide what a connection can see and do when you create it, and you can withdraw it. With Sprites the grant is revocable from either side, and the next tool call after a revoke fails rather than running on a cached credential.
Do Muse connectors cost anything?
Custom connectors consume Muse’s standard usage allowance alongside everything else it does. The service on the other end has its own pricing; Sprites is a paid product with a trial, and the connector itself is not charged separately.
Can Muse build a connector to any API?
Muse can try, given a public specification it can read without logging in. A hosted MCP server is the shortest path because Muse already knows the protocol and the transport, so there is nothing for it to infer. An OpenAPI document also works; an undocumented private API does not.
Give your agent something worth asking about
Connect your ad accounts to Sprites once. Muse, Claude, ChatGPT or any other client that speaks the protocol reads them from there — and every change waits for you.