Meta Muse Connectors, answered
How do you add a connector to Muse?
There is no connector settings screen in Muse. Meta’s guidance is to ask Muse in the conversation to build a Custom Connector, name the service and give it an entry point — an MCP server URL, an OpenAPI document or a package name. Muse builds the integration itself, tests it, and saves it as a reusable skill you can call in any later conversation.
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, 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 credential store directly; an OAuth service can take more back-and-forth, which Meta notes in its own guidance.
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
Muse has no connector settings screen. Ask it in the conversation and it builds the integration itself, 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.
- Meta notes that an OAuth service can take more back-and-forth in Muse than a static API key does. We are testing that handoff now.
Common questions
How many connectors does Muse have?
Meta ships a set of built-in connectors and opened the connector platform to developers in September 2026, so the built-in list changes. The number that matters for marketing is different: any service publishing a public MCP endpoint can be reached through one custom connector, whether or not it appears on a list.
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.