How to add a custom connector to Meta Muse (API or MCP)
A custom connector lets Muse use a service that is not in its connector list. You ask Muse to create one, give it the service's API details, and it stores your key in its Secure Credentials Store. Meta does not review custom connectors, so the service has to be one you trust.
By the superagnt_ team // updated
What a Muse custom connector is
Muse has three ways to reach a service. Built-in connectors come from Meta. Directory connectors are built by other companies and reviewed by Meta. Custom connectors are built by Muse for you, from the service's API details, and only you can use them. Meta's connector help article says it does not review custom connectors or how they use your information.
| Built-in or directory | Custom | |
|---|---|---|
| Who builds it | Meta or the app's company | Muse, from the details you give it |
| Reviewed by Meta | Yes | No |
| Who can use it | Anyone, from Settings, then Connectors | Only you |
| Where your key lives | The app's own sign-in | Muse's Secure Credentials Store |
What Muse needs from the service
Meta's documentation stops at the chat flow and the credential store. The requirements below come from builders who have done it, so check them against your own setup.
| Requirement | Why it matters | Source |
|---|---|---|
| A public HTTPS endpoint | Muse runs in Meta's cloud, so it cannot reach localhost or a private network | Reported by builders |
| An API it can read, or an MCP server URL | Muse needs to learn which calls exist; a documented API or an MCP server gives it that | Reported by builders |
| An API key or bearer token | Muse's credential prompt takes a key directly; browser sign-in (OAuth) reportedly takes more back and forth | Reported by builders |
| Clear error messages | Muse may show the service's errors to you as they come back | Our guidance |
API or MCP: which route to use
MCP (Model Context Protocol) is the open standard AI apps use to connect to tools. Claude and ChatGPT both accept remote MCP servers as custom connectors, so a service that already runs one is the easy case.
| API key + docs | MCP server URL | |
|---|---|---|
| Best when | The service has a documented public API but no MCP server | The service already hosts a remote MCP server |
| What Muse does | Reads the docs and writes the calls itself | Lists the server's tools and calls them |
| Setup effort | Higher: Muse has to work out the API | Lower: the tools describe themselves |
| Works elsewhere | Only where you rebuild it | The same server also works in Claude and ChatGPT |
How to add a custom connector to Muse
- 01Ask Muse to create it
Open a chat and ask Muse to create a custom connector for the service. Name the service and what you want it to do.
- 02Give it the details
Paste the API docs link or the MCP server URL when Muse asks. Muse guides you through what it needs, which can include pulling information from the service's API.
- 03Enter your key in the secure prompt
Paste the API key where Muse asks for it, not into the chat. Muse keeps it in its Secure Credentials Store.
- 04Test one read-only request
Ask for something harmless first, like listing recent items, to confirm the connection works.
- 05Set approvals
Keep Muse asking before any action that sends, buys or deletes. You can change approval behavior in Settings.
Prompts to start with
Create a custom connector for [service]. Its MCP server is at [https://...]. I will give you an API key when you ask. Once it's connected, list the tools you can use and don't take any action yet.
Create a custom connector for [service] using its public API. The docs are at [https://...]. Ask me for the API key through your secure prompt. Start with read-only calls and show me one example result.
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.
- 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.
When Muse cannot connect
| What you see | Likely cause | What to try |
|---|---|---|
| Muse cannot reach the service | The endpoint is local, behind a VPN, or blocked | Use a public HTTPS URL |
| Sign-in keeps looping | The service only supports browser sign-in | Use an API key if the service offers one |
| Muse uses the wrong calls | Thin or missing API docs | Point it at the service's MCP server or a fuller API reference |
| You want to remove it | Disconnect in Settings, then Connectors, and revoke the key at the service |
Custom connector or wait for a listing?
A custom connector works today but only for you, and without Meta's review. A listed connector is reviewed and available to everyone, and it is up to the service's company to submit it at muse.ai/platform. If you run a business and your tool is missing, a custom connector gets you working now. See the full Muse connectors list first; it may already be there.
Common questions
01How do I create a custom connector in Muse?
Ask Muse in chat to create one for the service, give it the API docs or MCP server URL, enter your key in Muse's secure credential prompt, test a read-only request, and set approvals.
02Does Meta Muse support MCP?
Meta's documentation describes custom connectors built from a service's API details. Builders report that pointing Muse at a remote MCP server URL works too. MCP servers are the standard that Claude and ChatGPT custom connectors use.
03Can Muse connect to any API?
It can build a connector for a service with a public, documented API that it can reach over the internet. Private or undocumented APIs, and anything on your local network, will not work.
04Are custom connectors safe?
Meta does not review custom connectors or how they use your information, so only connect services you trust, use keys with minimal permissions, and keep approvals on for actions.
05What is the difference between a custom connector and a directory connector?
A directory connector is built by the app's company, reviewed by Meta and available to everyone. A custom connector is built by Muse for you alone and is not reviewed.
06How do I remove a custom connector?
Disconnect it in Settings, then Connectors, then revoke the API key at the service. Ask Muse to forget anything it learned that you want removed.
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.
- Meta Help Center: How Muse works with Connectors
- Muse platform: submit a connector
- Claude Help Center: custom connectors using remote MCP
- OpenAI Help Center: developer mode and MCP apps in ChatGPT
- Sprites: Meta Muse connectors (builder notes)
- PostFast: Meta Muse connectors list
Muse and Meta are trademarks of Meta Platforms, Inc. superagnt_ is an independent company and is not affiliated with or endorsed by Meta.