Meta Muse Connectors: The Full List, and How to Build One

Meta Muse connectors let the agent read from and act in other services. As of September 27, 2026, trackers count about 37 to 39 live connectors, including Gmail, Google Calendar, Outlook, Notion, Plaid, Stripe Link, Shopify, OpenTable, Ticketmaster, Duffel and Spotify, with about 20 more announced. You can also have Muse build a custom connector to any API in chat.

There are two ways to build one. A custom connector is private: Muse writes it for you from an API, MCP server or CLI, and Meta doesn't review it. A directory connector is public: you submit it at muse.ai/platform and Meta reviews it before listing.

Meta Muse connectors list

This follows PostFast's sourced list, updated September 27. Sprites.ai's tracker (updated September 24) counts 39 live and marks some announced partners, such as Shop Pay, PayPal, GitHub and Box, as live already, so expect the two lists to disagree while rollouts land.

Category	Live connectors
Meta's own	Facebook, Instagram, Threads (auto-connected), Instagram Messages, Threads Messages, Messenger, Meta Catalog, the built-in browser
Email and calendar	Gmail, Google Calendar, Outlook Mail, Outlook Calendar, Outlook Contacts, Google Contacts, Google Tasks, Calendly
Docs and notes	Google Docs, Drive, Sheets, Slides and Forms; Notion and Granola (added Sep 18)
Finance and payments	Finances via Plaid, Link by Stripe
Shopping, dining, travel, events	Shopify Catalog and Checkout, OpenTable, Ticketmaster, Duffel, Spotify, Printify
Health and fitness	Function Health, HealthEx, Withings, Peloton, Apple Health
Messaging and devices	Telegram, Android SMS, Philips Hue, Tessie
Developer	Tailscale, Railway (Sep 23), Replit (rolling out Sep 26), and Custom Connector

Announced, not yet live everywhere: 1Password, Shop Pay, PayPal, Expedia, Instacart, Walmart, Best Buy, American Eagle, DICK'S Sporting Goods, Fanatics, Gap, Michael Kors, Sephora, Ulta Beauty, Wayfair, GitHub, Box, Fever, Turo and Viator. Most came out of Meta Connect on September 23. Shopify has since confirmed that Shop Pay is live as a wallet in Muse.

Amazon isn't on either list. It blocked Muse purchases from September 20.

Directory connectors vs custom connectors

	Directory connector	Custom connector
Who builds it	A business, via muse.ai/platform	Muse, for one user, on request
Reviewed by Meta	Yes: functional, security, legal, end-to-end tests	No
Who sees it	Every user, in the directory	Only you
Credentials	Handled through the connector	Muse's Secure Credentials Store

Sources: Meta help, CellCog.

Many connectors can be set to read-only, so Muse retrieves data but can't act. You can disconnect any of them under Settings, then Connectors. Meta's warning on custom ones is blunt: "Meta doesn't review custom connectors or how they use your information, so grant access with caution."

How to build a custom Muse connector

You don't write code. You ask Muse, and it writes and tests the integration inside its VM. David Singleton showed Muse writing and running its own integration code, and a Reddit demo has it building a Linear connector in under a minute.

Parallel published a six-step method that matches what builders report:

1. Find the entry point. An MCP server URL, an OpenAPI spec or API docs, or a CLI package name.
2. Send one message naming the service, the entry point and what you want done.
3. Answer transport and auth questions. Usually HTTP, plus "none" or a bearer token.
4. Paste credentials into the secure prompt, not the chat. Keys go to a store outside the agent's runtime.
5. Ask it to test every capability end to end and save the integration as a reusable skill.
6. Set the approval policy: read-only, ask per action, or allow.

Parallel's template prompt: "Build a custom integration to [SERVICE]. Its [MCP server URL / OpenAPI document / CLI package] is [LINK]. I want you to be able to [WHAT YOU WANT DONE] from any future conversation. Connect to it, test every capability end to end, show me the results, and save the integration as a reusable skill. If it needs credentials, ask me for them through the secure credential flow."

AdaptlyPost adds one useful habit: name a safe first call, like "call GET /social-accounts first, don't publish anything yet." Real examples from the connectors and MCP shelf: a TickTick integration in five minutes, a todo app with no official API, a Strava connector Muse built for itself, and Postiz's OAuth MCP server. For the difference between the two protocols, see MCP servers vs Muse connectors.

How to get a connector into the Muse directory

If you run a service and want every Muse user to find it, the platform has three steps: describe your product, submit for "functional, security, and legal" review with end-to-end testing, then appear in the directory, where editors may feature it (muse.ai/platform). Stripe Link is the payments rail. Meta received more than 1,500 applications in under a week (TechCrunch).

Pietro Zullo's walkthrough of submitting an MCP server shows what the form asks for:

1. Overview: connector name, company, website, example prompts, a 512 x 512 icon, whether you accept payments, a work email, support contact, privacy policy and terms.
2. Technical specs: connection type "Existing MCP", your hosted HTTPS endpoint, a docs URL, access requirements (accounts, paid plans, regions, rate limits) and authentication (API keys, OAuth with PKCE, or none).
3. Review: confirm you're authorized, accept the Muse Connector Terms, and submit.

What's still missing: no published review timeline, fee structure or revenue share. CellCog also found no SDK or developer terms as of September 18 (CellCog). The review-times tracker watches the queue.

Why the credentials stay safe (in theory)

Custom connector code runs inside the Muse Secure VM but never sees your real token. Meta's security post describes credential surrogation: the code gets a surrogate token, and Sentinel swaps in the real credential at the network boundary. Sentinel is also "the sole permission authority" for connector actions and all network egress. Details in what the Muse Secure VM is.

How often do real errands use a connector?

Less than the launch coverage suggests. Of the 132 catalog entries where someone describes having Muse do a specific errand, only about 15 name a connector such as Instacart, Plaid, Spotify or Notion (counted by hand on September 28, 2026). The rest ran through the browser, email or a phone call. Connectors matter most for repeat jobs and for services with no usable website, which is why builders keep writing custom ones for tools like Strava and Linear (see the steps above).

Patterns builders use

Builders converged on a few shapes:

• Serverless gateway with one bearer token. The Cloudflare Workers starter keeps upstream keys server-side behind one token, with an OpenAPI spec and a SKILL.md template.
• Registry-generated routes. AstroxNetwork's Apache-2.0 template generates routes, OpenAPI and llms.txt from one registry.
• Small-business actions. The HVAC and plumbing connector quotes a visit, holds a slot, books the job and sends a deposit link.
• Hold-and-approve. Change Verifier runs seven checks on payee bank changes and holds them until a named owner accepts.
• Read-only data. Dowser surfaces settlements, recalls and unused credits.
• Reaching your own machines. muse-fileapi and the Mac menu-bar connector expose local files over a Cloudflare tunnel with whitelists and audit logs.

Stackademic's developer guide adds design rules: idempotent, narrow endpoints (agents retry), typed schemas, human-readable errors, and a second confirmation for destructive actions. Collections like 150 one-paste connector skills are worth reading for conventions, but they're unreviewed. Read the code before you paste anything that asks for a token.

Practical tips

• Start read-only. Add write actions once you've watched a few runs.
• Give Muse a harmless first call to verify auth.
• Keep scopes narrow and make destructive actions two-phase (propose, then confirm).
• Publish an llms.txt or a clear docs page; Muse reads it when writing the client.

Built one? Submit it to the catalog.

Frequently asked questions

What connectors does Meta Muse support?

About 37 to 39 live ones as of late September 2026, including Gmail, Google Calendar and Drive, Outlook, Notion, Granola, Plaid, Stripe Link, Shopify, OpenTable, Ticketmaster, Duffel, Spotify, Peloton and Tailscale. Around 20 more, such as Walmart, PayPal and Expedia, are announced.

How do I add a custom connector to Muse?

Ask Muse to connect to the service and give it the MCP server URL, OpenAPI spec or API docs. Paste any API key into the secure credential prompt, not the chat. Muse writes the client in its VM, tests it and saves it as a skill.

How do I submit a connector to the Muse directory?

Apply at muse.ai/platform. The form asks for listing details, a hosted HTTPS MCP endpoint, docs and auth method, then Meta runs a functional, security and legal review with end-to-end tests. Fees and review times haven't been published.

Does Meta Muse support MCP servers?

Yes. Custom connectors can use an MCP server URL, and the directory form accepts an existing hosted MCP endpoint with API key or OAuth (PKCE) auth.

Can Muse connect to Amazon?

No. Amazon blocked Muse purchases from September 20, 2026. One user built a self-hosted cart API Muse reaches over SSH as a workaround.