Skip to main content
Two Muse products, two answers. Muse Code is Meta’s coding agent. It already loads remote MCP servers from ~/.config/muse/settings.json over streamable HTTP. That is the path that works today. The Muse app (the personal agent in the Muse app and WhatsApp) has Connectors, including custom connectors built from API details Muse walks you through. That is not a paste-an-MCP-URL flow. First-class MCP for the Muse app is coming soon. Do not paste the PostQueen MCP URL into Muse Settings → Connectors expecting it to work like Claude.
You need your PostQueen API key first. In app.postqueen.ai, open Settings → API Keys and click Reveal.

Muse Code

1

Edit Muse Code settings

Add this to ~/.config/muse/settings.json. Restart Muse Code after saving.
2

Or pass the key as a header

If you prefer a bare /mcp URL, put the key in Authorization:
3

Confirm

Ask Muse Code to list your PostQueen channels. Your account names come back when it calls integrationList.
Your API key grants full access to your PostQueen workspace: treat it like a password. Keep ~/.config/muse/settings.json private. If the key leaks, regenerate it in Settings → API Keys and update the file.

Muse app (coming soon)

Settings → Connectors in the consumer Muse app can attach catalog apps (Gmail, calendar). Custom connectors there collect API information, not an MCP server URL. We will add paste-URL steps here when Meta ships that. Until then, use Muse Code above, or any other MCP client.

Self-hosted

On a self-hosted instance, replace https://api.postqueen.ai with your NEXT_PUBLIC_BACKEND_URL, for example https://postqueen.example.com/api/mcp/YOUR_API_KEY. Your reverse proxy has to forward /mcp and stream the response: MCP on a self-hosted install.

Next steps

Talk to her from Muse

What works today in Muse Code, and what the Muse app is waiting on

MCP tools

All 14 tools Muse Code discovers on connect