Can Meta Muse run my outreach?

What Muse actually is

Muse is Meta's personal AI agent, announced in September 2026. In Meta's own description it "doesn't just answer questions, it actually does the work" — it is pitched at everyday errands rather than at running business software. Meta says it is rolling out in the US on iOS, Android and muse.ai, with AI glasses coming later.

The interesting part, for our purposes, is how it does things. Meta says Muse runs on a dedicated secure computer with its own browser, and that it "can open a browser, fill out forms, and negotiate on their behalf." People choose which apps Muse connects to and exactly how much access each one gets. Meta names payment and login integrations specifically — Link built by Stripe, with Shop Pay and 1Password support described as coming.

So Muse is genuinely an agent that acts. It just acts through a browser and a short list of integrations Meta chose, rather than through an open catalogue that other companies can join.

Why WarmySender is not a Muse connector

Because there is nowhere to be one. Meta's announcement of Muse makes no mention of MCP, a plugin system, a developer platform, or a third-party connector marketplace, and we could not find one documented anywhere else. There is no submission form, no directory, no approval queue. This is not a case of us not having got round to it.

It is worth being precise about a thing that is easy to misread. Meta does publish something MCP-shaped: Meta Ads AI Connectors include an Ads MCP server that, in Meta's words, exposes Meta business surfaces to third-party AI clients and works with any MCP-compatible agent. That is Meta running a server that you add into your own agent — the exact opposite of Meta hosting other companies' tools inside Muse. Seeing "Meta" and "MCP" in the same sentence does not mean Muse can reach WarmySender.

The unsupported path, described honestly

There is one thing worth mentioning, clearly labelled. Reporting on the Muse launch — press coverage, not Meta's own documentation — describes Muse being able to work with a service that has no built-in connector by using a public API with credentials the person supplies, and falling back to the browser where there is no API. WarmySender does have a public API, and you can create a key for it yourself in Settings → API Keys.

We are telling you that because you would find it anyway, not because we recommend it. Some honest caveats:

• We have not tested it. We make no claim that it works, and we cannot support it if it does not.
• It is a manual arrangement, not an integration. Nothing about it is documented by Meta as a supported way to reach a service like ours, so it can change without notice.
• It means handing a key to a consumer assistant. If you try it at all, create a read-only key so the agent can look at your workspace without changing anything, and delete it in Settings → API Keys the moment you are done.

The reassuring part is that even in that scenario the safety story does not change, because it is enforced on our side rather than the agent's. See below.

Muse and Muse Code are different products

This trips people up constantly, so: they share a name and almost nothing else.

• Muse is the consumer personal agent described above — phone, web, its own secure browser, errands. No connector platform we can join.
• Muse Code is Meta's terminal coding agent, installed from the terminal on your own machine. It reads the servers it can reach from a settings file you control, which means you can point it at WarmySender without anybody's catalogue being involved.

Muse Code is the one that works today, and we tested it: with the WarmySender block in its settings file, Muse Code really does reach our server when it starts up. To be straight about the limits of that test — we confirmed the connection, not a completed job. We had no key to hand and did not mint one, so we have never run a WarmySender tool from inside Muse Code and we do not claim to have. The tools themselves are the same 78 that every other connected agent uses against https://warmysender.com/mcp every day.

Setup is in Connect WarmySender to Muse Code, and the day-to-day workflow is in Run cold email outreach with Meta Muse Code.

What to use instead, today

If the goal is "an agent runs my outreach", you already have several routes that are set up in about a minute each: Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent — plus any other agent that speaks MCP, Muse Code included. Point it at https://warmysender.com/mcp, authorise it with a sign-in or a key depending on what the agent supports, and describe what you want.

Which AI agents can run outreach compares them app by app and plan by plan, and Connect an AI agent gives you a one-paste setup block for each.

Whichever agent you use, the limits are ours, not the agent's

Your agent never sends a message, DM or invite itself, and it can never raise a limit. Creating or launching a campaign only writes it down and hands it to WarmySender's scheduler, which paces every email and every LinkedIn, Instagram and WhatsApp action inside safe daily caps and the gradual ramp — the same protections the app uses, whether a human or an agent pressed go. Email verification shares the same allowance and pacing. And connecting or disconnecting your accounts stays in the app — your mailbox and social logins never pass through an agent or a chat log.

That is why we can be relaxed about which agent you point at us and firm about what it can do. The guardrails are not a setting inside the agent that a clever prompt could talk round; they are enforced by the thing that actually does the sending. Account safety always comes first.

Frequently asked questions

Can Meta Muse run my WarmySender campaigns?

Not through any supported integration. Meta has not documented a connector platform, a plugin store, a developer directory or MCP support for Muse, so there is no way for us to register WarmySender as something Muse can reach, and nothing for you to install. The terminal agent Muse Code is a different product and does connect — that is the path we support.

Is WarmySender a built-in Muse connector?

No. Meta chose Muse's built-in integrations and there is no published route for another company to be added to that list. If that changes and Meta documents one, we will be in the queue on day one and this page will say so.

Could I connect Muse myself with a WarmySender API key?

Possibly, and we would rather explain it than pretend it does not exist. Press coverage of the Muse launch describes Muse working with services that have a public API by using credentials the person supplies, and WarmySender does have a public API with keys you create in Settings → API Keys. But that is reporting, not Meta documentation, we have not tested it, and we cannot support it. If you experiment, use a read-only key and delete it afterwards.

What is the difference between Muse and Muse Code?

They are separate products that share a name. Muse is Meta's consumer personal agent — phone, web and its own secure browser, aimed at everyday tasks. Muse Code is Meta's terminal coding agent, installed on your own machine, which reads the servers it can reach from a settings file you control. That settings file is exactly why Muse Code can reach WarmySender and Muse cannot: no catalogue has to let you in.

Have you tested Muse Code with WarmySender?

The connection, yes. With the WarmySender block in its settings file, Muse Code reaches our server when it starts up and reports back on the key it was given. We have not run a WarmySender tool call from inside Muse Code ourselves — we had no key and did not create one — so we do not claim a completed job. The tools are the same ones every other connected agent uses daily.

If an agent did connect, could it send emails on my behalf?

No, and that is true of every agent, connected any way at all. No agent sends a message, DM or invite itself and none can raise a limit. Launching a campaign hands it to WarmySender's scheduler, which paces every send inside safe daily caps and the gradual ramp. Connecting and disconnecting accounts stays in the app.

Related reading

• Connect WarmySender to Muse Code — the three-step setup for the Meta agent that does connect
• Run cold email outreach with Meta Muse Code — the prompts, channel by channel
• Which AI agents can run outreach — the per-app, per-plan comparison
• What your AI agent can and cannot do with cold email — the capability matrix
• Connect an AI agent — one-paste setup for every supported agent
• The WarmySender MCP server — the full tool reference