# Muse Connector Platform: What Meta Opened to Developers

> Meta opened Muse connectors to developers on Sept 18, 2026. Three steps, Stripe Link, no fee or revenue share published. The page, read and dated.

- Author: Nitish Garg, Founder & CEO, CellCog
- Published: 2026-09-18
- Canonical (HTML): https://cellcog.ai/blog/muse-connector-platform/
- Section: Guides / Choosing a platform
- Publisher: CellCog (https://cellcog.ai), the AI employee platform. Blog index for agents: https://cellcog.ai/blog/llms.txt

## Key points

- At 7:03 PM Eastern on September 18, 2026, Mark Zuckerberg posted that Meta is 'Opening access for developers to build Muse connectors', ten days after Muse launched. The link goes to muse.ai/platform, a one-screen page with a single button, Submit a connector. His post says 'New connectors are live today' and names none of them; neither does the page.
- The pitch is three sentences and one inversion. 'You bring the API', Muse brings 'the agent, the browser, and the context of what the person actually wants', and 'People reach your service just by asking for it'. The business keeps its service; the customer's agent, running on Meta's computer, comes to it. Whoever owns the agent owns the moment of choice.
- The page describes a process, not a program. Three steps: describe your product, submit for review of 'functional, security, and legal requirements' with 'end to end testing' by Meta, appear in the directory, where 'Editors will review connectors for featured placement'. Payments run on Stripe Link, the rail Muse already uses for its own checkouts.
- What it does not publish: an SDK or API specification, a fee, a revenue share, a review timeline, developer terms, or a list of launch partners. The form asks for a description of the product, not code, and the page does not say who writes the connector. Stripe Link is a payments rail, not a term sheet.
- Meta's help center already describes two classes under the one word. Directory connectors are reviewed by Meta and listed in Settings. Custom connectors are built by Muse itself for one user, from any service with an API, and Meta says it 'doesn’t review custom connectors or how they use your information, so grant access with caution'. Tonight's page opens the reviewed class to businesses.
- Meta has never published a fixed connector list. The closest primary is Alexandr Wang's launch-day thread naming Gmail, Google Calendar, Outlook, Plaid, OpenTable, Google Docs, Spotify, Function Health, Withings, Tailscale and Peloton 'and more', plus Muse-only connectors for Instagram, Threads, Facebook and Messenger. The connectors added on September 18 are unnamed in every primary we could read.
- The week around the post: Muse for Mac on September 17, the number one free app on Apple's US App Store on the morning of September 18, and the developer door that evening. For a business the read is simple: your customers' agents are becoming your customers, and a reviewed directory listing is the way to meet them. The same connector model already runs on the working side of the agent market, where an AI employee reaches a business's tools one authorized connection at a time.

## At a glance

- **What did Meta announce?** On September 18, 2026 at 7:03 PM Eastern, Mark Zuckerberg posted that developers can now build Muse connectors and pointed to muse.ai/platform, a page with a Submit a connector button, a three-step review process, and Stripe Link for payments. The post says new connectors are live today without naming them.
- **What is a Muse connector?** Per Meta's help center, a connector links Muse to an app or service so the agent gains an ability, such as reading a calendar or writing an email. Two classes exist: connectors listed in the directory and reviewed by Meta, and custom connectors Muse builds for one user from a service's API, which Meta does not review.
- **What are the developer terms?** None are published. The platform page does not state a fee, a revenue share, a review timeline, an SDK, or developer terms. It says Meta reviews submissions for functional, security and legal requirements and completes end to end testing, and that Meta has partnered with Stripe so connectors can accept payments with Link.
- **Which connectors exist?** Meta has not published a list. Alexandr Wang's September 8 thread named Gmail, Google Calendar, Outlook, Plaid, OpenTable, Google Docs, Spotify, Function Health, Withings, Tailscale and Peloton, plus Muse-only connectors for Instagram, Threads, Facebook and Messenger. The September 18 additions are unnamed.

Meta opened Muse to third-party connectors on the evening of September 18, 2026: a founder post, a one-button page, a three-step review by Meta, Stripe Link for payments, and no published fee, revenue share or SDK. This page reads the post, the platform page and Meta's help center, quotes them, and dates every claim; it will be updated as the blanks fill.

## What Meta published tonight

At 7:03 PM Eastern on September 18, 2026, Mark Zuckerberg [posted on X](https://x.com/finkd/status/2101084678640066765): "Opening access for developers to build Muse connectors." The rest of the post is the pitch in three sentences. Muse "brings the agent, the browser, and the context of what the person actually wants". "People reach your service just by asking for it, and their agent takes it from there." And: "New connectors are live today. Come build with us." The link goes to [muse.ai/platform](https://muse.ai/platform). Two hours later the post had passed 230,000 views.

The platform page is short. Its heading is Muse Connector Platform, its one button reads Submit a connector, and its promise is a single sentence: "A connector brings what you’ve built into the everyday tasks people ask Muse to help with." Then three numbered steps and a payments line: "we've partnered with Stripe to make accepting payments easy with Link."

*The platform page in three pictures*

![Split infographic titled Two Kinds of Connector: a directory connector, a plug with a shield badge, built by the business, reviewed by Meta, listed in Settings, Stripe Link payments; a custom connector, a plug with a caution triangle, built by Muse for one user, not reviewed by Meta, only in that user's Muse, payments not described](https://cellcog.ai/blog/media/muse-connector-platform/slide-1.webp)
*Two kinds of connector under one word, per Meta's help center and the platform page*

![Timeline infographic titled Ten Days From Launch to a Developer Door with five nodes: Sep 8 Muse launches, Sep 8 Wang names eleven connectors, Sep 17 Muse for Mac, Sep 18 number one free app in the US, and a highlighted Sep 18 connector platform opens with an open door above it](https://cellcog.ai/blog/media/muse-connector-platform/slide-2.webp)
*Ten days from launch to a developer door: audience first, then the shelf*

![Two-column infographic titled What the Page Says, What It Leaves Blank: checkmarks for Submit a connector button, 3-step review, functional security legal, end to end testing, featured placement by editors, Stripe Link payments; dotted empty boxes for SDK or API spec, fee, revenue share, review timeline, developer terms, launch partners](https://cellcog.ai/blog/media/muse-connector-platform/slide-3.webp)
*What muse.ai/platform says and what it leaves blank, read Sept 19, 01:05 UTC*

*Table: What muse.ai/platform says, read September 19, 2026, 01:05 UTC*

| Item | On the page |
|---|---|
| Who it is for | Businesses: Grow your business with Muse and Reach new customers and give existing ones more ways to use your product |
| Step 1 | Describe your product: Tell us what your connector does and how users will use it |
| Step 2 | Submit for review: functional, security, and legal requirements, plus end to end testing by Meta |
| Step 3 | Appear in the directory: Once approved, users will be able to find your connector in Muse. Editors will review connectors for featured placement |
| Payments | Stripe Link, the rail Muse already uses for its own checkouts |
| Documentation | None linked; the page's only links are the submit form, the Muse app, and the consumer privacy policy and terms |
| Fee, revenue share, timeline, developer terms, launch partners | Not on the page |

## The inversion

Every app store since 2008 has worked one way: the developer builds the client, the platform owns the shelf, the user finds and installs. Zuckerberg's sentence takes the client out of the picture. Zuckerberg's opening words, you bring the API: the business keeps its service and its own terms of use, and the agent is the customer's, running on Meta's computer, with Meta's browser and Meta's memory of "what the person actually wants". The service is reached "just by asking for it".

That is the sentence a business should read twice. Whoever owns the agent owns the moment of choice, and a directory with an editorial layer ("Editors will review connectors for featured placement") is the part of this page that will matter most to anyone selling anything. The page asks for a description of the product, not code, and it does not say who writes the connector once the description is in.

## Two kinds of connector, one word

Meta's [help center](https://www.meta.com/help/artificial-intelligence/1687253048996149/) describes a connector as anything that gives Muse "new abilities, like the ability to see your calendar or write an email", and it describes two different things under that word. The directory class is what tonight's page opens: reviewed by Meta, listed under Settings, connected with a tap. The custom class has been there since launch: a user can ask Muse to build a connector to any service with an API, and Meta says plainly that it "doesn’t review custom connectors or how they use your information, so grant access with caution and review the provider’s privacy policies". The reviewed class is the one a business would want to be in. The unreviewed class is the one its customers can already use to reach it, terms or no terms.

*Table: Directory connectors vs custom connectors, per Meta's help center and the platform page*

| | Directory connector | Custom connector |
|---|---|---|
| Who builds it | Submitted by the business at muse.ai/platform | Built by Muse itself, at one user's request |
| Review | functional, security, and legal requirements plus end to end testing by Meta | None: Meta doesn’t review custom connectors |
| Where it appears | The Connectors list under Settings, with editorial featured placement | Only in that user's Muse |
| Credentials | The user authorizes the connection and can disconnect it any time | API details go into Muse's Secure Credentials Store |
| Actions | Governed by the user's approval settings; many connectors can be limited to retrieving data | Governed by the same approval settings |
| Payments | Stripe Link | Not described |

## Which connectors exist

Meta has never published a fixed list, and its September 8 launch post does not use the word connector once. The closest primary is Alexandr Wang's [thread](https://x.com/alexandr_wang/status/2097454574202495340) from launch day: "you can connect Muse to Gmail, Google calendar, Outlook, Plaid, Opentable, Google Docs, Spotify, Function Health, Withings, Tailscale, Peloton, and more", plus "unique connectors that are only available to Muse like Instagram (incl dm’s), Threads, Facebook (incl marketplace), and Messenger". The help center adds that Facebook, Instagram and Threads connect automatically for anyone with those accounts in the same Accounts Center. Tonight's post says "New connectors are live today" without naming one, and the platform page names none. Here is what a primary supports.

*Table: Muse connectors named in a primary source, September 19, 2026*

| Connector | Source |
|---|---|
| Gmail, Google Calendar, Google Docs, Outlook | Alexandr Wang on X, September 8 |
| Plaid, OpenTable, Spotify | Alexandr Wang on X, September 8 |
| Function Health, Withings, Peloton, Tailscale | Alexandr Wang on X, September 8 |
| Instagram (including DMs), Threads, Facebook (including Marketplace), Messenger | Alexandr Wang on X, September 8: available only to Muse |
| Facebook, Instagram, Threads | Meta help center: connected automatically through Accounts Center |
| Apple Health, Android SMS | Meta help center: access managed in device settings |
| The connectors added September 18 | Not named in Zuckerberg's post, on the platform page, or in the help center |

## Ten days

The developer door is the third move of the week. Muse for Mac arrived on September 17 ([TechCrunch](https://techcrunch.com/2026/09/18/metas-muse-hits-mac-letting-the-ai-take-actions-on-your-computer/): "On the Mac, Muse can interact with your files, messages, calendar, notes, and mail, all within their native applications"). On the morning of September 18, [Business Insider](https://www.businessinsider.com/meta-muse-personal-ai-agent-top-app-store-charts-2026-9) and 9to5Mac reported Muse at number one among free apps on Apple's US App Store, ahead of ChatGPT. The platform page followed that evening. Ten days from a consumer launch to a directory pitch is fast by any platform's history, and it is the order that matters: audience first, then the shelf.

*Table: Muse, launch to developer door, all times UTC*

| Date | Event | Source |
|---|---|---|
| Sep 8, 19:00 | Muse launches in the US on iOS, Android and muse.ai | Meta newsroom |
| Sep 8, 22:38 | Wang names eleven connectors and more, plus four Muse-only ones | Alexandr Wang on X |
| Sep 17 | Muse for Mac, acting on files, messages, calendar, notes and mail | TechCrunch, September 18 |
| Sep 18, 12:39 | Number one free app on Apple's US App Store | Business Insider |
| Sep 18, 23:03 | Connector platform opens to developers | Mark Zuckerberg on X |
| Sep 19, 01:05 | Platform page read: three steps, one button, no terms | Our read |

## What is missing, and why it matters

The gap between Zuckerberg's post and the page under it is the story. "Come build with us" points at a form that asks what your product does, not at a specification, and a business reading it tonight cannot answer five questions it would ask of any platform.

- What does it cost to be listed, and does Meta take a share of what a connector earns? Stripe Link is a payments rail, not a term sheet.
- Who writes the connector? The form collects a description; the page does not say whether the business ships code or Meta's team wires the API.
- How long does review take, and what happens to a rejected submission?
- What terms govern a developer's connector? The only Terms link on the page is the consumer one.
- Which connectors went live today? Neither the post nor the page names one.

None of this is unusual for a day-one page. It is unusual to open the door with a founder post at seven in the evening and 230,000 views in two hours, which is why the blanks will fill fast and why this page will be updated as they do.

## For a business, and for anyone hiring an AI employee

Two sentences for a business. Your customers' agents are becoming your customers, and a reviewed listing in a directory with editorial placement beats being a custom connector nobody reviewed. If your service has an API, the description form is worth filling in tonight, and the terms are worth asking about before anything else.

The same connector model already runs on the working side of the agent market. An AI employee reaches a business's tools through connections its owner authorizes, one at a time, with the scope set at connection: read the inbox, or also send from it. On CellCog that is 1,000+ apps through the Connectors page, and a business with an internal API or an MCP server plugs it in the same way: its own API, the employee's agent. Since September 17, 2026 the door opens the other way too. CellCog's own MCP connector at cellcog.ai/mcp lets Claude and other MCP clients reach a person's CellCog account, so a customer's agent can hand work to a business's AI employee.

The difference from Muse is the job, and the rail. [Muse](https://cellcog.ai/blog/what-is-muse/) is one person's agent on Meta's computer, and the Sentinel on that computer approves what reaches the internet. An AI employee is hired into a role, with its own inbox, task board and memory, and the agent classifies every command that reaches your world, your machine, your real browser, your connected tools, so the platform rejects any command that arrives unclassified. Both designs put a gate between the agent and the world. Muse's gate belongs to Meta; an AI employee's belongs to the owner.

## What would change this page

- Meta publishing developer terms, a fee, a revenue share, a review timeline or an SDK.
- A named list of the connectors that went live on September 18.
- A business announcing an approved directory connector, with a date.
- The directory becoming browsable outside the Muse app.
- Meta's help center or newsroom describing the platform in its own words.

## The record

As of September 19, 2026, 01:10 UTC: page opened. Mark Zuckerberg's post is dated September 18, 23:03 UTC; the platform page carries three steps, one button and no terms; the help center's connector article, updated within the week, describes reviewed and custom connectors and names no September 18 addition. Every quote above was read from the primary at the time stated.

## FAQ

**Where do developers submit a Muse connector?**

At muse.ai/platform, the page Mark Zuckerberg linked in his September 18 post. The page has one button, Submit a connector, and describes three steps: describe your product, submit for review, appear in the directory. As of September 19, 2026, 01:05 UTC the page carries no documentation link, no SDK and no developer terms; its only links are the submit form, the Muse app, and the consumer privacy policy and terms.

**Does Meta charge developers or take a cut of connector revenue?**

The page does not say. It states that Meta partnered with Stripe to make accepting payments easy with Link, which is the payments rail Muse uses for its own checkouts, and nothing about fees, revenue share or payouts. Any figure you read elsewhere is not from Meta's page.

**How is a directory connector different from a custom connector?**

Meta's help center describes both. A directory connector is reviewed by Meta for functional, security and legal requirements, tested end to end, and listed under Settings so any user can connect it with a tap. A custom connector is one Muse builds for a single user when a service is not in the list, using API details stored in Muse's Secure Credentials Store; Meta says it does not review custom connectors or how they use your information.

**Can a Muse connector act on my behalf, or only read data?**

Both, under the user's approval settings. The help center says that by default Muse will not take many important actions, like sending an email, without your approval, and that many connectors can be set up so Muse can only retrieve data and not take actions. Some connectors can also push information to Muse proactively, such as calendar changes, and Meta says it identifies those before you connect them.

**How does this compare to how an AI employee connects to tools?**

Same shape, different job. Muse is one person's agent on Meta's computer, and a connector is how a business meets that person. An AI employee is hired into a role at a business and reaches the business's own tools through connections its owner authorizes one by one. On CellCog that means 1,000+ apps through the Connectors page, plus any internal API or MCP server the owner plugs in, with every command that reaches your world classified before it lands. Since September 17, 2026 the door opens the other way too: CellCog's own MCP connector at cellcog.ai/mcp lets Claude and other MCP clients reach a person's CellCog account. Try it free, no credit card needed.

## Related

- [What Is Muse? Meta's Personal AI Agent on Its Own Secure Computer, Explained](https://cellcog.ai/blog/what-is-muse/index.md)
- [Muse Spark 1.3 Is Out: Meta Claims Frontier Parity, and Its Own Table Mostly Backs It](https://cellcog.ai/blog/muse-spark-1-3/index.md)
- [What Is Muse Code? Meta's Terminal Coding Agent, Explained](https://cellcog.ai/blog/what-is-muse-code/index.md)
- [What Is an AI Employee? The 5-Part Test for a Standing AI Worker](https://cellcog.ai/blog/what-is-an-ai-employee/index.md)

## The AI employee for this read

[AI Head of Growth](https://cellcog.ai/ai-employees/ai-head-of-growth): I built this page, checked every quote against its source and drew the charts. I can do the same for your company.

---

Markdown alternate of https://cellcog.ai/blog/muse-connector-platform/. Try CellCog free, no credit card needed: https://cellcog.ai/signup