Meta Muse Email: Connect iCloud, Yahoo or Any IMAP Inbox

Meta Muse email works out of the box for one Gmail or one Outlook account, through the built-in connectors under Settings → Connectors. For anything else, iCloud, Yahoo, AOL, a work mailbox at OVH or IONOS, a second Gmail, you ask Muse to create a Custom Connector pointing at https://anymailmcp.com/mcp, sign in once, and Muse can search, read, draft, file and send from that inbox like any other tool. It takes a couple of minutes per mailbox.

Muse is Meta’s agent app, launched on September 8, 2026. It runs on iOS, Android, the web at muse.ai and inside WhatsApp, and it is aimed at doing things for you rather than chatting: booking, buying, sending. Email is the obvious place to point an agent like that, and it is also where the built-in list runs out first.

Which Meta Muse email connector covers your inbox

Meta does not publish a full connector list (it lives in the app and changes often), so this is what launch coverage and the in-app list show as of November 2026:

• Gmail and Google Calendar: built in. Reports say search and read are one permission and sending is a separate one.
• Outlook Mail, Outlook Calendar, Outlook Contacts: built in, as three separate connectors.
• Several accounts of the same kind: third-party guides report that each built-in connector holds a single account. Meta has not documented this either way, so check your own Connectors screen.
• Everything else: iCloud Mail, Yahoo, AOL, Zoho, Fastmail, GMX, OVH, Gandi, IONOS, Infomaniak, a cPanel box at your web host, any IMAP server. No built-in connector. These providers do not offer an OAuth sign-in for third-party apps, so there is nothing for Meta to plug into.

So if your whole life is one Gmail, use Meta’s connector and stop here. anymail earns its place for the last bullet: iCloud and Yahoo with an app password, a domain mailbox with its normal login, a second or third Gmail, and the CalDAV calendar and contacts that come with iCloud, Yahoo, Fastmail and most hosts. All of them sit behind one connector, and every tool takes a mailbox argument so Muse knows which inbox you mean.

For Outlook, use Muse’s own Outlook Mail connector. anymail does not connect Outlook.com, Hotmail or Microsoft 365 mailboxes today: Microsoft only allows OAuth for IMAP, and our Microsoft sign-in is not open yet.

Connect your email to Meta Muse with a custom connector

Muse runs in Meta’s cloud, so it can only reach MCP servers on a public HTTPS URL over streamable HTTP. Local and stdio servers do not work. anymail is hosted, so there is nothing to tunnel.

1. Ask Muse in a chat. Meta’s help center says that for a service not in the Connector list, you ask Muse to create a Custom Connector. This works in the app, on the web and in WhatsApp. Paste this message:

   Create a Custom Connector for a remote MCP server, then connect to it:
   Name: Anymail
   Transport: remote streamable HTTP
   URL: https://anymailmcp.com/mcp
   Auth: OAuth

2. Sign in when Muse asks. Muse opens our sign-in: your email, a magic link, then the mailbox you want to add. Server settings are detected from your address and the login is checked live against your provider.
3. Let Muse list the tools. Muse reads the server’s tool list, tries them, and saves the connector so later conversations can use it without setup.

Some guides also describe Settings → Connectors → Add custom connector, where you paste the same URL. Others say that screen only lists Meta’s own connectors. If you see the button, it is the same connector; if not, the chat route is the one Meta documents.

What to type at the sign-in depends on the provider:

• iCloud (@icloud.com, @me.com, @mac.com): an app-specific password from account.apple.com, never your Apple ID password. Steps in Can ChatGPT read my iCloud Mail?, which apply to Muse unchanged.
• Yahoo: a Yahoo app password. See connecting Yahoo Mail.
• OVH and other hosts: the mailbox password you already use in Thunderbird or on your phone. The OVH walkthrough explains why that is the only key that exists.
• A second Gmail: a Google app password. The trade-offs are in Gmail MCP options.
• Anything else on IMAP: if auto-detection misses, enter the hosts by hand. The IMAP guide covers the usual ports.

Nothing in this setup goes in the chat itself. Muse keeps chat history, so a password pasted there stays there. The sign-in is OAuth: credentials go on our page, Muse only gets a token.

Permissions: keep approval on for anything that sends, moves or deletes

There are two layers, and you want both.

In Muse, each connector can be read-only, require approval for every action, or be allowed to run. My setting: allow the read tools (search_emails, read_email, get_thread, list_events), and keep approval on for send_email, forward_email, move_email, delete_email and delete_event. Muse is built to act, and an agent that books dinner without asking is fine. One that files your boss’s email into Trash without asking is not.

On our side, each mailbox has an access level that the model cannot change from the chat:

• Read: search, read, threads, attachments, calendars. Nothing changes in your mailbox.
• Read & organize: adds drafts, moving, flagging, labels, folders and calendar events. No sending, no permanent deletion.
• Full: everything, including send_email and delete_email.

For the first week, Read & organize is the right call. Muse writes replies with create_draft, they land in your real Drafts folder threaded under the original message, and you press Send from your usual mail app. More on that workflow in drafting replies with an assistant; it applies to Muse as is.

Prompts that work in Muse

Name the mailbox when you have more than one. Each prompt below says roughly which tools it calls, so you know what to approve.

Expect one search_emails per mailbox, a read_email for each message worth opening, and one list_events. No approvals needed if read tools are allowed.

Bigger jobs have their own guides: IMAP basics, CalDAV calendars, and inbox watches if you want new mail to drive a task instead of a question.

Muse Code, briefly

Muse Code, Meta’s terminal agent, is a separate product with its own config. It reads ~/.config/muse/settings.json (with "schema_version": 1), supports streamable HTTP servers, and runs the OAuth sign-in with muse mcp login <server>. Add https://anymailmcp.com/mcp as a server there and log in once; the tools are the same.

Limits, honestly

• Muse is US-only for now, adults only. Some guides mention Canada; Meta’s launch coverage says US. If Muse is not available where you are, this setup is not either.
• We have not run the Muse sign-in end to end ourselves. The connector is standard remote MCP with OAuth, and it works in Claude, ChatGPT, Grok and Cursor. OAuth inside Muse is reported to work with more back-and-forth than other clients. If the sign-in does not complete, there is no API key fallback: anymail connects through OAuth only. Write to contact@anymailmcp.com and tell us where it stopped.
• Meta does not review custom connectors, and anymail is not an official Muse listing. “Works with Meta Muse” means it speaks the protocol Muse speaks, not that Meta vetted it. Add only servers you trust, ours included, and keep the access levels tight.
• Two meters. Custom connectors count against Muse’s usage meter like everything else (free, Power at $20 a month, Maximum at $100 a month). On our side the free tier is one mailbox and 15 calls a day (45 a week, 150 a month), which the morning sweep above can use in one go on a busy inbox. Solo is 4.99 € a month (excl. VAT) for unlimited calls and up to 5 mailboxes; Team is 29.99 € a month for everyone on your company domain.
• No Google Calendar through us. Google’s CalDAV only accepts OAuth, so a Gmail added with an app password gets mail only. Muse’s own Google Calendar connector covers it.
• Your provider’s limits apply. IMAP connection caps and SMTP sending limits are set by Apple, Yahoo or your host. A bulk move of thousands of messages can hit them; ask Muse to work in batches.
• Search is live IMAP. Nothing is indexed on our side, so a body search is only as good as your server’s. If it comes back empty, ask by sender, subject or date range.

Pick your provider below for the exact sign-in details, then paste the message above into Muse.

Frequently asked

Can I keep Meta’s Gmail connector and add anymail too? Yes. They are separate connectors with separate tool names. A common setup keeps the main Gmail on Meta’s connector and puts iCloud, Yahoo or a domain mailbox on anymail.

Is my mail copied anywhere? Not by us. Each tool call opens a live connection to your provider; we store your encrypted login (AES-256-GCM) and a usage counter. Muse may keep what it read in its own chat history and memory, so ask it to forget anything sensitive.

How do I cut access? Disconnect the mailbox from your anymail profile, remove the connector in Muse, or revoke the app password at your provider. Any one of them stops access on the spot.