Meta Muse MCP connector
Meta Muse MCP connector for Shopify, Meta Ads and 100+ tools
Ask Muse in chat to add one URL, or add it to Muse Code's settings file, then sign in with OAuth. Muse can then read live orders, ad spend, invoices and tickets from the tools you already run. No API keys, and no server to host.
https://app.popmcp.com/mcp- OAuth 2.1 sign-in
- No API keys
- Read-only option
- Hosted, nothing to install
- URL for every client
- 1
- business tools behind it
- 100+
- API keys to paste
- 0
- sources checked for this guide
- 14
Where it works
How PopMCP connects to Meta Muse
Meta Muse can reach Model Context Protocol (MCP) servers in two places. For Muse Code, its terminal coding agent, Meta documents remote MCP servers with OAuth sign-in. In the Muse app, you ask Muse to create a Custom Connector. Meta does not call that MCP, but server operators report it connects to remote MCP servers with OAuth. PopMCP is a hosted MCP server that puts 100+ business tools behind one URL, https://app.popmcp.com/mcp, so one connector reaches every tool you connect in PopMCP. You choose which connectors Muse may use.
Muse app Custom Connectors
Not documentediOS, Android, muse.ai, WhatsApp · US
Ask Muse in chat to create a Custom Connector with the PopMCP URL, then open the sign-in link it sends. Meta documents Custom Connectors but not MCP or OAuth. Server operators report both work.
Muse Code CLI
SupportedTerminal and CI · macOS, Linux, Windows
Add PopMCP to ~/.config/muse/settings.json, then run muse mcp login popmcp. Muse Code registers itself with PopMCP and opens the browser sign-in.
Meta Model API
Not documentedResponses, Chat Completions and Messages APIs
Meta's API docs list function, custom, web search and tool search tools, but no remote MCP tool. Your code would have to run its own MCP client.
See it work
Ask Muse about your business, get real answers
Muse calls PopMCP's tools, PopMCP reads your connected accounts, and the answer comes back in the chat. Pick a question to replay it.
How did last week's Meta Ads spend compare with our Shopify sales?

meta_ads_get_account_insightsMeta Ads · Spend and purchases by campaign, last 7 daysDone
shopify_get_ordersShopify · Orders created in the same 7 daysDone
You spent $4,180 on Meta Ads last week. Shopify took $21,740 from 268 orders, about $5.20 in sales for every ad dollar.
| Campaign | Spend | Purchases |
|---|---|---|
| Autumn Prospecting | $2,310 | 58 |
| Retargeting 7-day | $1,240 | 61 |
| Catalog Sales | $630 | 22 |
- Retargeting cost $20.33 per purchase, against $39.83 for prospecting.
- Meta credits its ads with 141 purchases. Shopify recorded 268 orders, so 127 were not credited to Meta Ads.
Illustration with sample numbers. Connected to your accounts, Muse answers from your own data, through the same PopMCP tools.
Setup
Connect PopMCP to Meta Muse, step by step
Pick where you use Meta Muse. Each path ends with the same PopMCP sign-in.
Meta's help center says you ask Muse to create a Custom Connector. It does not mention MCP or OAuth, so the steps below follow reports from MCP server operators. Muse works from Meta's cloud, so it can only reach a public HTTPS server, which PopMCP is.
Connect your tools in PopMCP
Sign in at app.popmcp.com, connect Shopify, Meta Ads or any other tool, and check each one shows as Verified.
Ask Muse to create a Custom Connector
In a Muse chat, send the message below.
Paste into chatCreate a Custom Connector for a remote MCP server. Name: PopMCP. Transport: remote streamable HTTP. URL: https://app.popmcp.com/mcp. Auth: OAuth, there is no API key.Answer its questions
If Muse asks, confirm the server is a URL over HTTPS and that it signs in with OAuth. Do not paste a key or header: PopMCP does not issue one.
Open the sign-in link and approve
Muse replies with a sign-in link. Open it, sign in to PopMCP, tick only the connectors Muse should reach, and approve.
Check what Muse can see
Ask Muse to run list_connections. It lists the connectors it was granted. Start with a read-only request.
Try this promptRun list_connections and tell me which tools you can use.
Muse Code, Meta's terminal and CI coding agent, reads MCP servers from its settings file and handles the OAuth sign-in itself.
Add PopMCP to your settings file
Open ~/.config/muse/settings.json and add a popmcp entry under mcp_servers. Keep "schema_version": 1 in the file: without it, every Muse Code command fails at startup. There is no header or key to add.
~/.config/muse/settings.json{ "schema_version": 1, "mcp_servers": { "popmcp": { "transport": "streamable_http", "url": "https://app.popmcp.com/mcp" } } }Sign in
Run the command below. PopMCP's sign-in opens in your browser. Tick the connectors Muse Code may reach and approve. Muse Code keeps and refreshes the tokens.
Terminalmuse mcp login popmcpSign in without a browser
Meta's docs say sign-in also works headless. A Muse Code user's GitHub issue describes this flag: it prints a sign-in URL, then asks you to paste back the final redirect URL.
Terminalmuse mcp login popmcp --headlessConfirm the tools
Start Muse Code and run /mcp to see connected servers and their tools. Then ask it to run list_connections and start with a read-only request.
If it asks you to sign in again
When PopMCP returns a 401, at startup or mid-session, Muse Code tells you the exact muse mcp login command to run.
Try asking
First questions to ask Muse
Click a prompt to copy it, then paste it into Muse once PopMCP is connected.
Sales and stock
Ads and marketing
Money
Customers and support
Safe by design
You decide what Muse can touch
OAuth sign-in, no API keys
Muse signs in to PopMCP with OAuth 2.1. There is nothing to paste, and your Shopify or Stripe credentials stay encrypted inside PopMCP.
You pick the connectors
The PopMCP consent screen lists your connections. Muse reaches only the ones you tick.
Read-only where you want it
A workspace owner or admin sets each teammate to no access, read, or read and write, per connection.
See and stop every call
Usage shows each request by user, connector and tool. Removing someone's access applies on the next request.
Good to know
Before you connect Meta Muse
Meta Muse launched Muse Code in August 2026, the Muse app in September 2026, and its documentation is still changing. Here is what is not settled yet.
Meta has not documented MCP in the Muse app
Meta's help center says you can ask Muse to create a Custom Connector, but it does not mention MCP or OAuth. That it connects to remote MCP servers with OAuth comes from server operators' reports since September 2026. One third-party guide says early testers found OAuth sign-in takes more back-and-forth than a static key. Muse Code is the route Meta documents.
Use chat, not Settings
One third-party guide describes Settings → Connectors → Add custom connector. Another says Settings → Connectors lists only Meta's own connectors. Asking Muse in chat is the route every source agrees on.
US at launch
Meta's launch post says Muse is rolling out in the US on iOS, Android and muse.ai, and you can also talk to it in WhatsApp. One third-party guide says Canada too.
Muse's sign-in address
Server operators report the Muse app signs in with the callback address https://agent.meta.ai/api/hatch/oauth/callback, which several MCP servers rejected at first. PopMCP's OAuth server accepts it.
Muse Code does not sandbox MCP tools
Meta's docs say MCP tools run outside Muse Code's filesystem and network sandbox. Approval still applies, but a tool the server marks read-only runs without a prompt under on-request approvals. Read each prompt before you accept.
Common questions
Meta Muse and PopMCP FAQ
Does Meta Muse support MCP servers?
Muse Code does. Meta's docs show how to add a remote MCP server to its settings file and sign in with OAuth. In the Muse app, you ask Muse to create a Custom Connector. Meta does not call that MCP, but server operators report it connects to remote MCP servers such as https://app.popmcp.com/mcp with OAuth.
How do I add PopMCP to the Muse app?
In a Muse chat, ask it to create a Custom Connector for a remote MCP server named PopMCP, with the URL https://app.popmcp.com/mcp and OAuth sign-in. Open the sign-in link Muse sends, tick the connectors it may use and approve. Meta does not document MCP for the app, so this route rests on server operators' reports.
How do I add PopMCP to Muse Code?
Add a popmcp entry under mcp_servers in ~/.config/muse/settings.json, with transport streamable_http and the URL https://app.popmcp.com/mcp. Then run muse mcp login popmcp and sign in to PopMCP in your browser.
Do I need an API key to connect Muse to PopMCP?
No. PopMCP uses OAuth 2.1 sign-in, so Muse never holds a PopMCP key. If Muse asks for a key or header, tell it the server uses OAuth. Your Shopify, Meta Ads or QuickBooks credentials stay encrypted inside PopMCP.
Which of my tools can Muse reach?
Only the connectors you tick on the PopMCP consent screen. A workspace owner or admin can also set each teammate to no access, read, or read and write per connection.
Is Muse available outside the US?
Meta's launch post names only the US: Muse is rolling out there on iOS, Android and muse.ai, and in WhatsApp. One third-party guide also lists Canada.
Can I use PopMCP with the Meta Model API?
Not directly. Meta's API docs list function, custom, web search and tool search tools, and no remote MCP tool. Your code would need to run its own MCP client and handle PopMCP's OAuth sign-in.
Is Muse safe to give access to my business tools?
Meta says it does not review custom connectors, so the controls in PopMCP matter: tick only the connectors Muse needs and keep teammates on read-only where possible. Muse checks with you before sensitive actions such as sending an email, and you can disconnect a connector at any time in Settings → Connectors.
Sources
Official documentation
Every step on this page comes from these sources. Vendor docs are marked; community sources are labelled.
- Muse CodeMetaOfficial docs
Muse Code is Meta's coding agent for the terminal and CI, and runs on macOS, Linux and Windows.
dev.meta.ai/docs/muse-code - Muse Code: Extending and automatingMetaOfficial docs
Muse Code declares remote servers under mcp_servers with transport streamable_http, signs in with muse mcp login over OAuth 2.1 in the browser or headless, registers its own client by default, lists servers with /mcp, and runs MCP tools outside its sandbox.
dev.meta.ai/docs/muse-code/extending - Muse Code: Configuration and contextMetaOfficial docs
The settings file is ~/.config/muse/settings.json and must include "schema_version": 1.
dev.meta.ai/docs/muse-code/configuration - How Muse works with ConnectorsMeta Help CenterOfficial docs
You can ask Muse to create a Custom Connector, Meta does not review custom connectors, Muse asks before actions such as sending an email, you disconnect a connector in Settings under Connectors, and the page does not mention MCP or OAuth.
www.meta.com/help/artificial-intelligence/1687253048996149/ - Introducing MuseMeta NewsroomOfficial docs
Meta introduced Muse on 8 September 2026, rolling out in the US on iOS, Android and muse.ai and also reachable in WhatsApp, running on its own computer in the cloud.
about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/ - Tool callingMetaOfficial docs
The Meta Model API documents function, custom, web_search and tool_search tools, and no remote MCP tool.
dev.meta.ai/docs/tool-calling - AuthorizationModel Context ProtocolOfficial docs
The OAuth 2.1 flow, with PKCE and dynamic client registration, that remote MCP clients and PopMCP use.
modelcontextprotocol.io/specification/2025-06-18/basic/authorization - Please allow Meta Muse OAuth redirect URIGitHub (SentinelX issue #49)Community source
An end user reports that the MCP server rejected Muse's automatic registration because it uses the callback https://agent.meta.ai/api/hatch/oauth/callback.
github.com/pensados/sentinelx-cloud-core/issues/49 - feat(mcp-worker): let Meta Muse connect with OAuthGitHub (2nd-brain pull request #78)Community source
A server maintainer added Muse's callback address so Muse custom connectors could sign in with OAuth.
github.com/unsubject/2nd-brain/pull/78 - Muse (Meta)SealGate docsCommunity source
Muse adds a remote MCP server when you ask it in chat for a Custom Connector with OAuth, then sends a sign-in link.
sealgate.ai/docs/connect-clients/muse - Meta Muse MCP: Custom Connector SetupAnythingMCPCommunity source
Describes both Settings → Connectors → Add custom connector and a chat prompt, and says Muse is offered in the US and Canada.
anythingmcp.com/guides/clients/muse - Meta Muse ConnectorsSpritesCommunity source
Says Settings → Connectors lists only Meta's built-in connectors, and that early testers found OAuth sign-in takes more back-and-forth than a static key.
www.sprites.ai/muse/connectors - MCP server status and management over MSPGitHub (muse-code-sdk issue #45)Community source
muse mcp login opens a browser, and with --headless it prints a URL and asks for the final redirect URL.
github.com/meta-models/muse-code-sdk/issues/45 - Meta Releases Muse Code Coding Agent With Muse Spark 1.2Let's Data ScienceCommunity source
Meta released Muse Code in beta on August 5, 2026.
letsdatascience.com/news/meta-releases-muse-code-coding-agent-with-muse-spark-12-b8c2ce2e
Checked against these sources on .
More AI clients
Use the same URL everywhere
Put 100+ business tools inside Muse
Connect your tools in PopMCP, add the PopMCP URL, and approve the sign-in. It takes a few minutes, and there is nothing to install.
