Meta Muse Connectors
Meta Muse is Meta's personal AI agent app, launched in September 2026 and built on the Muse Spark models. It does tasks through connectors. There are three ways to connect an MCP server to the Muse family.
No custom MCP setting in the Muse app (yet). The consumer Muse app uses Meta's own connector catalog. To use any MCP server today, use Muse Code, or submit your server to the catalog.
Connectors in the Muse App
In the Muse app, open Connectors to turn on services from Meta's catalog. Muse can also build a custom connector for you from a service's own API. These custom connectors do not use MCP.
Add an MCP Server to Muse Code
Muse Code, Meta's coding agent, supports MCP servers fully. Declare them in the mcp_servers block of ~/.config/muse/settings.json.
A remote server:
{
"mcp_servers": {
"my-server": {
"url": "https://example.com/mcp"
}
}
}A local stdio server:
{
"mcp_servers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"]
}
}
}Keep any keys that are already in the file, such as schema_version. Restart Muse Code to load the tools.
MCP tools are not sandboxed. A stdio server runs as a normal process outside the Muse Code sandbox. Approval prompts still apply, but only add servers you trust.
Submit Your Server as a Muse Connector
If you run an MCP server, you can offer it to all Muse users. Go to muse.ai/platform and fill in the three-step form: describe the product, give the technical details (your MCP server URL or API), then confirm and submit. Meta reviews it before it shows in the catalog.
Find Servers to Add
Browse the MCP server directory and filter by the streamable-http or sse transport. Each remote server page has a Muse tab under Add as a Connector with the exact URL to copy.