Muse (Meta)

Connect Muse, Meta's personal AI agent, to SealGate. Muse has no MCP settings page, so you ask it in chat to build a Custom Connector for the gateway and approve the sign-in.

Muse is Meta's personal AI agent, launched on September 8, 2026 and powered by Meta's Muse Spark models. It runs in the Muse app on iOS and Android, on Mac, on the web at muse.ai, and inside WhatsApp (Meta's product page). This page is about that agent. It is not about the band, the Muse meditation headband, or Meta's separate Muse Code terminal agent, which has its own section below.

You connect Muse to SealGate once. After that, Muse can call every tool your gateway exposes, including your messaging apps, and SealGate checks each call against your policies and logs it.

How Muse connects to outside tools

Muse reaches services in three ways, and only one of them fits SealGate:

Path	Who builds it	Use it for SealGate?
Built-in connectors (Settings > Connectors)	Meta, with launch partners such as Gmail, Google Calendar and Spotify	No. Meta curates this list and there is no way to add to it.
Custom Connectors	Muse writes the code itself, on its own cloud computer	Yes. This is how you add SealGate.
Browser	Muse drives a browser on its cloud computer	No. It is slower and breaks when a site changes.

Muse has no "add MCP server" setting. You won't find a field for a server URL in Settings. You ask Muse in chat to create a Custom Connector, and it builds an MCP client for the gateway on its cloud computer, tests it, and saves it as a reusable skill (Meta Help Center: Connectors).

Muse runs on a Linux virtual machine in Meta's cloud, not on your phone or laptop. Like ChatGPT and Grok, it can only reach an MCP server that is on the public internet, so you give it SealGate's public gateway, https://mcp.sealgate.ai/mcp. A localhost address from the SealGate desktop app will not work.

Before you start

A Muse account. At launch Muse is available to adults in the US, and Meta asks for a payment card even on the free tier.
A SealGate account at dashboard.sealgate.ai.
Optional: the messaging connector, if you want Muse to work with WhatsApp, iMessage, Telegram and other chat apps. See Connect Muse to your messaging apps.

1. Ask Muse to build the SealGate connector

Open a new Muse chat (in the app, on the web at muse.ai, or on Mac) and paste this message as-is:

Create a Custom Connector for a new remote MCP server, then connect to it:

- Name: sealgate
- Transport: remote streamable HTTP
- URL: https://mcp.sealgate.ai/mcp
- Auth: OAuth (sign in when prompted - there is no API key to paste)

Then list its tools and call the sealgate builtin_whoami tool to confirm the connection works. Save the connection as a reusable skill.

This is the same message the SealGate dashboard gives you when you choose Muse on the Connect Agent page. There, it already has your deployment's gateway host filled in. If you self-host SealGate or use the demo environment, copy it from the dashboard rather than using mcp.sealgate.ai.

Muse may reply with a few questions before it starts. The answers are:

Is it HTTP or stdio? HTTP. Specifically, streamable HTTP at the URL above.
Does it need auth? Yes, OAuth. There is no API key or header to enter.

Muse shows a SealGate sign-in link. Open it, sign in with your SealGate account, and approve access. SealGate issues Muse a token tied to your user, so every call Muse makes is attributed to you in the dashboard. Your SealGate API key never appears in the Muse chat.

If Muse can't finish the OAuth sign-in and asks for a key instead, give it your personal connection URL (https://mcp.sealgate.ai/mcp/<your-api-key>/, from Settings > Get MCP URL in the SealGate dashboard). Only enter it in Muse's secure credential prompt, never in the chat itself. Muse stores what you type in the credential prompt outside the agent's own runtime, while anything you type in the chat stays in your conversation history. Treat that URL like a password.

3. Check the connection

When the sign-in finishes, Muse lists SealGate's tools and calls builtin_whoami. The reply should include your SealGate email and organization. To confirm from the SealGate side, open Sessions in the dashboard. The call should appear there within a few seconds.

Muse saves the connector as a skill, so you don't have to set it up again. Start a new chat and ask "What tools does the sealgate skill have?" to confirm Muse still finds it.

4. Choose how much Muse may do on its own

Muse and SealGate each have their own approval step, and together they give you two layers of control:

In Muse: a separate agent called Sentinel checks every connector action. Under Muse Settings, you can make the SealGate connector read-only, require approval for every action, or allow it. When Muse asks for approval, you can grant it for one action, one task, a time window, or permanently. For anything that sends a message, keep approval on.
In SealGate: Access Control Levels and policies decide which tools Muse can call at all, and every call is logged.

Connect Muse to your messaging apps

SealGate's messaging connector bridges WhatsApp, iMessage, Telegram, LinkedIn, Signal, Instagram, Messenger, X, Discord and LINE through the Beeper desktop app on your own computer. A small daemon then tunnels it to the gateway, so Muse can reach it from Meta's cloud. Setup and a worked example for each network:

WhatsApp · iMessage · Telegram · LinkedIn · Signal · Instagram · Messenger · X · Discord · LINE

After the connector is approved, you don't change anything in Muse. The messaging tools show up behind the same SealGate skill. Try:

Using the sealgate skill, summarize my unread messages and draft replies for me to approve before anything is sent.

Muse Code (the terminal agent)

Muse Code, Meta's coding agent for the terminal and CI, does support MCP servers directly. Add SealGate as a streamable_http server in the mcp_servers block of its settings file, with the URL https://mcp.sealgate.ai/mcp. Then sign in:

muse mcp login sealgate

In a Muse Code session, run /mcp to see SealGate's tools. If you already set SealGate up in Claude Code or Codex, Muse Code's /migrate skill can import that server config for you. Meta documents the settings format in the Muse Code docs.

Troubleshooting

Muse says it can't add MCP servers. Muse has no settings page for them, and it sometimes says so before offering another route. Tell it to build a Custom Connector that acts as an MCP client, and paste the message from step 1 again.
Muse tries to connect to localhost or 127.0.0.1. It can't reach your machine. Use the public gateway URL https://mcp.sealgate.ai/mcp.
The skill works but the messaging tools are missing. The messaging connector isn't running or isn't approved yet. Make sure the Beeper desktop app is open and signed in on your computer, then check the connector's status in the SealGate dashboard.
Calls show up in SealGate but are blocked. That is your policy doing its job. The block reason is in the dashboard's Sessions view. Change the tool's Access Control Level or the policy if the block was not what you wanted.

Muse FAQ

Does SealGate work in the Muse mobile app?

Yes. Muse builds the connector on its cloud computer, not on your device, so once it is saved as a skill it works everywhere you use Muse: the iOS and Android apps, the web at muse.ai, Mac, and inside WhatsApp. The one exception is the messaging connector, which needs your computer switched on with the Beeper desktop app running, because that is where your chats are bridged from.

Which Muse plan supports custom connectors?

Meta doesn't list Custom Connectors as a paid feature, so you can build the SealGate connector on Muse's free tier. Connector calls count against Muse's usage meter like everything else Muse does. If you run daily inbox triage, the Power ($20/month) or Maximum ($100/month) plans give you more room. Plans and limits change quickly, so check Meta's Help Center for the current details.

Does Meta review the SealGate connector?

No. Meta says it doesn't review custom connectors, so you are trusting the service directly. With SealGate, what Muse can reach is decided by your SealGate policies and Access Control Levels. Every call is logged, and message content passes through without being stored.