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. No Sprites account yet? The sign-in Muse opens is where you create one.
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.
Which MCP servers Muse can reach
Muse builds its connector on a cloud VM, so what matters is whether the server is reachable from there and how it authenticates. Five transport shapes and three auth shapes, and how each fares.
Transport
Authentication
Muse and MCP, answered
How is this different from adding an MCP server in Claude or ChatGPT?
Claude and ChatGPT have a connector panel where you paste a URL into a form. Muse’s Settings › Connectors lists only built-in connectors and takes no URL, so the same job is done in the conversation: you describe the server and Muse builds the integration itself. The endpoint is identical in all three cases — what differs is whether you fill in a field or write a sentence.
What kind of MCP server works with Muse?
A remote one, hosted, reachable over HTTPS and speaking streamable HTTP. Local stdio servers are the common failure: they work in a desktop client running on the same machine and are invisible to Muse, which runs in Meta’s cloud. If a server only has install instructions and no URL, it is the wrong shape for this.
Which MCP URL do I give Muse for marketing tools?
https://mcp.sprites.ai/mcp — the Sprites connector. There is one endpoint and every client uses it. Every OAuth grant is bound to exactly that address, so a variant of it is refused before consent rather than failing later in a way that is hard to debug.
What does authentication look like?
Muse asks what the server expects and stores credentials in a secure store it cannot read back. A static bearer token or API-key header fits that flow directly. An OAuth service works through a browser hop but, by early testers’ accounts, takes more back-and-forth — worth knowing before you start rather than halfway through.
Can I run my own MCP server for ad platforms?
Yes, and for a single analyst reading one account it is a legitimate choice. What it costs is the part that is invisible at the start: a developer token, OAuth credentials per platform, refresh handling, rate limits, and a host that stays up. The tradeoff is real rather than rhetorical, and it turns on whether anyone other than you depends on it.
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
Where is the MCP settings screen in Muse?
Nowhere. Settings › Connectors exists, but it lists Meta’s built-in connectors and has no field for a server URL — the most common confusion about Muse and MCP. You ask for a Custom Connector in the chat and Muse guides you through it.
Does Muse support local MCP servers?
No. Muse runs in Meta’s cloud and cannot reach a server on your computer. A stdio server must be installable in its environment, and a localhost URL will not resolve.
Is the Sprites MCP server official for Muse?
The Sprites endpoint is a standard remote MCP server, which any client speaking the protocol can use — that is the point of an open protocol. Sprites is not an official Meta integration, and no custom connector is: Meta does not review them.
What is MCP, in one sentence?
An open protocol that lets an AI client call tools published by a server it did not ship with, so the client holds the conversation and the server holds the capabilities.
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.