MCP Servers vs Muse Connectors: What's the Difference?

An MCP server is a generic way to expose tools to any AI client. A Muse connector is Muse's own unit of integration: code and credentials that let the Muse agent talk to one service, either reviewed by Meta and listed in the directory, or written by Muse for a single user. The two overlap because a Muse custom connector can be pointed at a remote MCP server, but they are not the same thing, and a connector does not have to be MCP at all.

If you already run an MCP server, you can probably reach Muse users today without Meta's approval. If you want to be in the directory, that is a separate review process.

What an MCP server is

The Model Context Protocol is an open protocol for describing tools, resources and prompts so that any compatible AI client can call them. You write one server and many clients can use it. It says nothing about who reviews your server, where credentials live, or whether the user approved a purchase. Those are the client's job.

What a Muse connector is

Meta's help page describes three kinds of Muse connectors (Meta help):

• Meta product connectors. Facebook, Instagram and Threads connect automatically through Accounts Center.
• Directory connectors. Built by partners, reviewed by Meta and listed in Muse. Launch examples include Gmail, Google Calendar, Plaid, Stripe Link, OpenTable, Ticketmaster and Duffel (PostFast's sourced list).
• Custom connectors. You ask Muse to connect to a service it does not list, it retrieves the API information, and it stores your credentials securely. Meta does not review these.

Connectors can be set to read-only, and Muse asks before important actions like sending email. A connector is the code plus credentials; a skill is the saved instructions for using it (Parallel).

Can Muse use an MCP server?

Yes, through the custom connector path, with caveats. According to Parallel's write-up, Muse reaches outside services three ways when writing a custom connector:

• MCP servers. Remote servers over streamable HTTP are "the easy case," and Muse uses the official MCP SDK to connect.
• REST APIs. Muse needs the OpenAPI document or the docs page.
• CLIs. A CLI on npm or PyPI works because the VM can install packages.

Postiz documents the MCP route end to end: paste the MCP setup prompt with the Postiz endpoint, approve a sign-in link, and Muse lists your channels. It then chains the server's tools (integrationList, integrationSchema, schedulePostTool) to schedule a post (Postiz). That is an OAuth flow. Parallel is more cautious, saying bearer tokens and API-key headers fit the credential store directly while OAuth-only services "may still work through Muse's browser, but expect more back and forth."

Meta's own help page does not mention MCP. Treat MCP support as observed behavior, not a documented contract.

Why local MCP servers don't work out of the box

Your Muse agent runs in a cloud VM. An MCP server on localhost on your laptop is unreachable from it (Parallel). Builders have solved this with tunnels:

• Muse Mac Connector exposes an authenticated tool set from a menu-bar app over a Cloudflare tunnel.
• muse-fileapi serves whitelisted directories over Cloudflare Tunnel with two-phase writes and an audit log.
• A homelab setup joins the Muse VM to a Tailscale network instead.

Muse for Mac now covers some of this natively, with per-app Off, Read only, and Read and interact controls for Mail, Calendar, Notes, Reminders and iMessage (Meta help).

MCP servers vs Muse connectors, side by side

	MCP server	Muse directory connector	Muse custom connector
Who builds it	Anyone	A partner, then Meta reviews	Muse, for one user
Reviewed by Meta	No	Yes: functional, security, legal, end-to-end tests	No
Works outside Muse	Yes, any MCP client	No	No
Discovery	You share the URL	Listed in Muse's directory	Only the user who made it
Credentials	Up to the server and client	Handled by Muse	Muse's secure store, surrogate tokens
Payments	Not specified by the protocol	Stripe Link via the platform	Not documented

Sources for the directory column: muse.ai/platform and CellCog.

Builders who ship both

The practical answer from the catalog is to write one MCP server and wrap it for Muse. Several builds do exactly that:

• Change Verifier is both a Muse connector and an MCP server that runs seven checks on vendor bank-account changes and returns clear, review or block.
• Barbaros MCP hosts read-only MCP connectors built for the Muse connector platform.
• Dowser is a read-only MCP connector that surfaces settlements, recalls and expiring points.
• Threadwell Slack bridges to Slack's official MCP server through a local OAuth bridge, and was submitted to the platform with a full submission pack.
• A phone-number MCP gives a Muse agent inbound and outbound calling.

Others skip MCP and go straight to OpenAPI. The HVAC and plumbing connector ships an OpenAPI spec plus llms.txt rules. The AstroxNetwork template generates routes, OpenAPI and llms.txt from one registry. The Cloudflare Workers starter includes an OpenAPI spec, a SKILL.md template and a proof checklist.

What about Muse Code?

Muse Code, the terminal coding agent, is a different client. It works with MCP servers the way other coding CLIs do. oh-my-musecode installs an MCP server as part of its bundle, the muse-code-acp adapter passes MCP servers through from Zed or VS Code, and the Muse Code handbook has notes on running an MCP fleet. Connectors are a Muse agent concept; MCP is how you extend Muse Code.

Which should you build?

• You want to reach Muse users this week: ship a remote MCP server or a clean OpenAPI spec with bearer-token auth, and publish a setup prompt, as Postiz and AdaptlyPost did.
• You want to be listed and able to take payments: apply at muse.ai/platform. As of September 18 there was no SDK, API spec, developer terms or published revenue share (CellCog), so expect some waiting.
• You want every agent client, Muse included: MCP first, Muse wrapper second.

More on the review process in the developer platform overview.

Frequently asked questions

Does Muse support MCP?

Muse can connect to remote MCP servers when it builds a custom connector, according to builders and to Parallel's write-up, and Postiz documents an OAuth MCP flow working. Meta's help page does not mention MCP, so this is observed behavior rather than an official guarantee.

Can I connect a local MCP server to Muse?

Not directly, because the agent runs in a cloud VM that cannot reach your localhost. Builders use Cloudflare tunnels or Tailscale to expose a local service, or use Muse for Mac's built-in app permissions instead.

Are Muse custom connectors reviewed by Meta?

No. Meta states that it doesn't review custom connectors or how they use your information. Only directory connectors go through Meta's functional, security and legal review.

How do I get my connector into the Muse directory?

Submit it at muse.ai/platform, where Meta runs functional, security and legal review plus end-to-end testing before listing. Meta received more than 1,500 applications in under a week, and no review timeline has been published.