MuseAIConnectorsSubmit a connector

How to Create a Custom Connector in Muse

Last reviewed . Every claim below is backed by a source in Sources. Where we have no source, the guide says so.

You ask Muse to build it. Meta's help page says: “If you want to connect to a service not yet available in the Connector list, you can ask Muse to create a Custom Connector.” That request is the only instruction the page gives. Muse guides you through the process, keeps any keys in its Secure Credentials Store, and Meta does not review what it builds. The rest of this page is what Meta has published about it, what people report working and failing, and what is still not published.

Custom connector or directory listing?

Two different things get called “building a Muse connector”, and people mix them up. One user posted about building a Splitwise connector “now that we have developer access” (@SladynN, 20 September), which runs the two together.

If you only want Muse to reach a service you use, you need the first. If you run the service and want every Muse user to find it, you need the second.

What Meta has published

Meta's help page, “How Muse works with Connectors”, has four sentences on custom connectors. Muse “will guide you through the process, which can involve retrieving API information from the service.” It “stores these in its Secure Credentials Store.” And: “Meta doesn't review custom connectors or how they use your information, so grant access with caution and review the provider's privacy policies.” The page does not mention MCP, OAuth or skills.

Meta's safety write-up, published at launch, adds one line on scope: “Muse can also write its own custom connectors for other services you care about if they have their own APIs or CLIs.” It also describes the credential design. Keys are held by a credential service, the agent's code only ever sees a “surrogate” token, and the real credential is swapped in at the network boundary.

Two people who speak about Muse as its makers have described the feature on X. Alexandr Wang, who announced “our new personal ai assistant” on launch day, wrote on 12 September: “you can often just ask muse to connect to anything and it’ll write the whole integration in the background.” The same day, @dps, who wrote on launch day about “our technical post” on how Muse was built, posted: “Muse can write its own software and run it in the VM you and your Muse share in the cloud. So you can connect Muse to any service with an API.”

How people do it, step by step

Meta publishes no step-by-step guide. This sequence comes from Parallel's walkthrough and the user reports below, and each step says where it comes from.

  1. Find the entry point. Parallel suggests the API docs or OpenAPI document, an MCP server URL, or a CLI package name. Muse can look these up itself, but Parallel found the exchange is shorter if you paste the link.
  2. Ask in one message. Name the service, the entry point and what you want Muse to do with it. One user's wording: “I need you to set up custom connectors so that you can manage all of these apps for me” (@MattPRD).
  3. Give the key through the secure field, not the chat. One user described Muse asking him “to paste my API in a secure field” (@mikepat711). Parallel warns that pasting a key into the conversation defeats the credential design and leaves it in your history.
  4. Ask it to test and save the result. Parallel reports that Muse tested each tool and saved the integration as a reusable skill for later conversations.
  5. Set how much it may do without asking. Meta's safety write-up says approvals can be one-time, session-scoped, task-scoped, time-bounded or perpetual. For anything that sends, posts or spends, Parallel advises keeping approval on.

What people report

These are saved posts, quoted word for word. They are individual accounts, not tests we ran.

The GitHub failure fits something Parallel wrote: token authentication suits the credential flow, while “OAuth-only services may still work through Muse's browser, but expect more back and forth.” That is one report and one explanation, not proof of a rule. Meta's Connect recap has since said “there’s Notion, Granola, GitHub, and Box” among new connectors, and Alexandr Wang listed GitHub on 29 September among connectors launching that day; see our GitHub listing. A user reported the next day that it was broken for them and they used a personal access token instead (@borgerntendies).

What about MCP servers?

Consumer Muse has no “add MCP server” setting, according to Parallel. When Parallel handed Muse the URL of its own hosted MCP server, Muse built a client on its VM, called each tool and saved the result as a skill. Parallel makes that server, so it is not a neutral tester. It also notes that a server running on your own laptop is out of reach, because the VM is in Meta's cloud. Meta's help page does not mention MCP at all. At least one user is asking for more: “we need to be able to connect it to custom mcps” (@mostaiai).

What to check before you hand over a key

What is not published

Sources

Something here wrong or out of date? Tell us and we will fix it.