// meta muse guide

How to add a custom connector to Meta Muse (API or MCP)

A custom connector lets Muse use a service that isn't in its connector list. Ask Muse in chat to create one and give it four things: a name, the transport (Streamable HTTP for a remote MCP server), the URL, and how it signs in (OAuth if the server supports it, otherwise an API key). Muse keeps the credential in its Secure Credentials Store, and Meta doesn't review custom connectors, so connect only services you trust.

By the superagnt team // updated November 3, 2026

01// before you start

What to give Muse up front

Muse builds a custom connector from what you tell it, so have these ready. A custom connector is yours alone and unreviewed; the connectors Meta and app makers ship are compared with custom ones on the Muse connectors list.

Field	What to enter	superagnt's value
Name	What you'll call it in chat	superagnt
Transport	Streamable HTTP for a remote MCP server; for an API, its docs URL instead	Streamable HTTP
URL	The server's public HTTPS address	https://mcp.superagnt.com/mcp
Sign-in	OAuth if the server supports it, otherwise an API key, entered in Muse's secure prompt	The access token on your superagnt MCP server card, sent as a bearer header
What it's for	One line, so Muse knows when to reach for it	Finding customers: people and company search, work emails and verification, LinkedIn and X data

superagnt, ready to paste

Create a custom connector named superagnt. It's a remote MCP server: transport Streamable HTTP, URL https://mcp.superagnt.com/mcp. It authenticates with a bearer token: ask me for it through your secure prompt. Once it's connected, list the tools you can use and don't take any action yet.

02// step by step

How to add a custom connector to Muse

01
Ask Muse in chat
Open a chat in the Muse app and ask it to create a custom connector. Custom connectors are set up in the Muse app, not in WhatsApp (WhatsApp Help).
02
Give it the four fields
Name, transport, URL and sign-in method, as in the table above. For an API without an MCP server, paste the docs link instead.
03
Sign in
For OAuth, finish the sign-in Muse opens. For an API key, paste it into Muse's secure credential prompt, never into the chat itself.
04
List the tools, then make one read-only call
Ask Muse which tools it can now use, then ask for something harmless, like a search, before anything that writes.
05
Set approvals
Keep Muse asking before anything that sends, buys or deletes. Settings, then Permissions, sets how often it asks (Meta's help).

Prompts to start with

mcp server

Create a custom connector named [name]. It's a remote MCP server: transport Streamable HTTP, URL [https://...]. Sign in with OAuth if it offers it; otherwise ask me for an API key through your secure prompt. Once it's connected, list the tools you can use and don't take any action yet.

api + docs

Create a custom connector for [service] from its public API. The docs are at [https://...]. Use OAuth if the service supports it, otherwise ask me for an API key through your secure prompt. Start with read-only calls and show me one example result.

03// worked example

Worked example: what superagnt's server answers

superagnt's server lists its tools by family: people and company search, the email finder and verifier, LinkedIn, X, Reddit, Instagram, YouTube, web search and a database. The first call should be read-only. Here is that call, sent directly over MCP to superagnt's staging environment rather than from inside Muse: the result as received, trimmed and masked where it says so.

the ask

“Use the superagnt connector to find 25 owners of medical practices in Austin, Texas. Don't contact anyone.”

01Search for owners (one page of 25)792 ms wall timeNov 3, 2026, 17:06 UTC

→ calldata_agnt_people

{
  "action": "search",
  "filters": {
    "seniority": ["Founder/Owner"],
    "industry": ["Medical Practices"],
    "location": ["Austin, Texas"]
  },
  "page": 1,
  "response_format": "json"
}

← result

{"items":[
  {
    "full_name": "•••••••",
    "job_title": "Owner",
    "seniority": "Founder/Owner",
    "city": "Austin",
    "state": "Texas",
    "country": "United States",
    "email_status": "VERIFIED",
    "company_name": "•••••••",
    "company_domain": "•••••••",
    "company_industry": "Medical Practices",
    "company_employee_count": 5,
    …
  },
  …
],"total":149}

» Trimmed: 24 of the 25 people, and this one's first and last name, headline, mobile status, department, LinkedIn links and person id. Names, company and domain are masked at a fixed width; the tool returned them.

25 people from 149 matches in under a second, for 1.98¢: a harmless first call that proves the connection works before you let it near your inbox.

04// permissions

Read, write and sensitive write: what Muse asks before

Meta's guidelines for listed connectors class every tool as read, write or sensitive write (Muse connector guidelines). Read and ordinary write tools offer allow once, always allow or deny. Sensitive writes ask on every use, and Meta says they "cannot be set to Always allow, including through Settings or a saved permission." Meta doesn't say the tiers apply to custom connectors, so set your own: in Settings, then Permissions, "Ask for some actions" asks before every write and important read actions, and "Always ask" before anything at all.

05// limits

What can't work, and why

A server on localhost, behind a VPN or on a private network. Muse runs on a cloud machine Meta hosts, and its SSRF rules stop a public hostname from resolving to private infrastructure (Meta's security write-up).
A server process on your own computer, such as a local npx package. Muse can't reach your machine; Sequenzy tells readers not to use its local npx package with Muse. Parallel reports that stdio servers npm or pip can install run on Muse's own cloud machine instead, but a public Streamable HTTP URL is the simplest route (Sequenzy, Parallel).
An undocumented or private API. Muse needs docs or an MCP server to learn what calls exist.

06// troubleshooting

When Muse can't connect

What you see	Likely cause	What to try
The OAuth window never finishes	A blocked pop-up, or sign-in started in another browser	Allow pop-ups for Muse, finish sign-in in the same browser, and on mobile open the link in the system browser (Sequenzy)
Sign-in asks for a client ID	Muse publishes no OAuth client document of its own, so a developer reports the client ID always has to be supplied (PostFast)	Use the server's API key or bearer token route if it has one; a server that wants Muse on OAuth hosts a client document for it
It worked yesterday, now it asks to sign in again	A short-lived token with no refresh	Reconnect; PostFast reports tokens lasting about an hour
Muse opens its browser instead of the connector	It picked the website over the tool	Say "use the [name] connector" in the prompt (Sequenzy)
Muse can't reach the service	A local, VPN-only or blocked endpoint	Use a public HTTPS URL
Muse uses the wrong calls	Thin or missing API docs	Point it at the service's MCP server or a fuller API reference

From Sequenzy's setup guide (October 18) and the developer reports PostFast collected, as of 2026-11-03.

07// stay safe

Keeping a custom connector safe

Use a key with the smallest permissions the service offers. Read-only if you only need to look things up.
Never paste a key into the chat itself; use Muse's credential prompt. Meta says the agent's harness "doesn't see real credentials" and stores tokens in a separate container on your Muse machine.
Keep approvals on for sending, purchasing and deleting.
Read the service's privacy policy. Meta says to, because it does not review custom connectors.
Rotate or revoke the key at the service if you stop using the connector.

08// get listed

Getting your connector listed in Muse's directory

A custom connector works today but only for you. A listed one is reviewed by Meta and shows up for everyone, and the service's company submits it at platform.muse.ai. What the form and Meta's guidelines ask for:

Part	What Meta asks for
Connection type	Raw API (API URL, an optional OpenAPI URL and docs) or existing MCP (a hosted endpoint and docs), per Stacktree, who filled in the form
Authentication	API keys, OAuth with PKCE or other, per Stacktree; Meta asks for the endpoint, auth setup, requested scopes and credentials, such as OAuth client credentials or an API key
Tools	Each classed as read, write or sensitive write; sensitive writes ask on every use
Testing	A dedicated test account Meta can use
Review	Three stages: risk assessment, tool review, end-to-end QA. Meeting the guidelines doesn't guarantee approval, and Meta isn't approving new tools that move money
Timeline	None published. Meta says it can't answer status emails, and Stacktree reports onboarding in waves after more than 2,000 submissions

From Meta's connector guidelines (platform.muse.ai/docs) and Stacktree's write-up of the form, checked 2026-11-03.

09// questions

Common questions

01Muse add Custom connector gone?

Some users report the "Add custom connector" entry under Settings, then Connectors, is missing or gone in recent app versions, and builders say it shows on some accounts only. You don't need it: ask Muse in chat to create a custom connector, which is the route Meta's help describes.

02Does a custom connector work on Muse after all?

Yes. Meta's help describes custom connectors built in chat, and builders who connected a remote MCP server report the tools worked (Parallel, October 29, 2026; TruCommerce, September 26, 2026).

03How do I add a custom connector to Meta Muse?

In the Muse app, ask Muse to create a custom connector and give it a name, the transport (Streamable HTTP for an MCP server), the URL and the sign-in method (OAuth if the server supports it for Muse, otherwise an API key or token in the secure prompt). Then ask it to list its tools, make one read-only call and set approvals.

04Can Meta Muse use MCP servers?

Yes, in practice. Meta's developer guidelines cover API and MCP connectors for its directory, and builders report custom connectors work with a remote MCP server URL over Streamable HTTP. Meta's consumer help describes custom connectors without naming MCP.

05Does Muse see my API keys?

Muse keeps connector credentials in its Secure Credentials Store, and Meta says the agent's harness doesn't see real credentials. Enter a key in Muse's secure prompt, never in the chat, and use a key with the smallest permissions the service offers.

06Is a custom connector the same as a skill?

No. A skill is a built-in capability Meta ships, like web browsing, image generation or creating documents. A custom connector links Muse to an outside service, with its own tools and your credential.

superagnt for muse

Find customers from inside Muse.

We are building a superagnt connector for Muse: people and company search, verified work emails, and Buyer Signal Search, which finds people publicly asking for what you sell. Get early access and we will tell you when it is ready.

Get early access→

sources

Muse and Meta are trademarks of Meta Platforms, Inc. superagnt is an independent company and is not affiliated with or endorsed by Meta.

// more muse guides

Muse connectors list

Every connector we can source, grouped by category and dated, plus how to add one.

Find customers with Muse

Muse for Small Business, the connectors by job, and the customer-finding prompt run through superagnt.

30 Muse prompts

Free prompts for small business owners, a five-part formula, and two customer-finding prompts run through superagnt.