About this site, and how we check things
MuseAIConnectors is an independent directory of connectors for Muse, Meta’s personal AI assistant, plus guides to the rest of the Muse ecosystem. It is built by App Agentic. We are not Meta, we do not speak for Meta, and nothing here is endorsed by Meta.
Why this site exists
The connector directory inside Muse is behind sign-in. From the outside, muse.ai/connectors redirects to a sign-in page and the site’s public sitemap lists four URLs, none of them a connector. So there is no public page that answers “which products work with Muse, and what does each one actually do?” We are trying to be that page — honestly, rather than completely.
What we never do: crawl muse.ai
Muse’s robots.txt states that collecting data from Muse by automated means is prohibited without express written permission, disallows /connectors and /api/, and points at Meta’s automated data collection terms.
We take that at face value. No script on this project requests a muse.ai connector path, and we do not link to muse.ai/connectors anywhere, because it is a sign-in wall rather than a page. Everything below is how we work within that.
Where the data comes from
- Public announcements and makers’ own pages. A company saying “we are live on Muse” on its own site or account is our strongest routine source.
- Press coverage from named outlets, with the article linked.
- Posts on X, checked one by one. We resolve each post id through the public syndication endpoint and record the handle, the date and the text. If the handle does not match, the post will not resolve, or the claim runs past the text we could actually read, we drop it. We never cite a post we could not check.
- Somebody opening the Muse app and looking. Done by a person, by hand, never by a script — that is the only way it can be done without breaking the rule above.
- Maker submissions. Sent in by the people who built the connector, then checked against a public source like everything else. See how to submit.
The evidence rule
Every fact on a listing carries a source URL, the quote it rests on, and the date we last confirmed that source still says it. Nothing is inferred from a product’s other integrations, its category or what “obviously” must be true. A field we have no source for reads not published rather than being filled with a guess, and our own one-line summaries restate the evidence instead of adding to it.
When sources genuinely disagree, we show both and pick no winner. Shop Pay is the current example: Meta’s newsroom called it coming soon while a Shopify VP said it works today. We are not in a position to settle that, so we don’t pretend to.
What the status labels mean
- Publicly confirmed
- A public source shows it is live on Muse.
- Seen in app
- One of us opened the Muse app and saw it.
- Announced
- A source says it is coming. Not the same as live.
- Sources conflict
- Two credible sources disagree. We show every source and pick none.
- Single report
- One person reported seeing it and nobody has independently confirmed it. Worth knowing, not worth relying on.
Only the first two get a listing into search engines. The rest still render, and say why they are not confirmed, but they stay out of the sitemap and carry a noindex tag.
Staying current
Evidence goes stale. A listing whose sources have not been re-checked within 30 days says so at the top of its page, and after 90 days it drops out of the index automatically until somebody re-reads them. We would rather show a page that admits it is unchecked than quietly serve an old claim with a fresh-looking date on it.
The “checked” date on a listing is the day a human or an automation last re-read its sources. It is not a rotated timestamp, and it is not the same thing as the day the listing last changed.
What we don’t publish
- Ratings and review scores. We have no reviews, so we show no stars and put no rating markup in our pages.
- Usage, popularity or traffic numbers. Directories that publish these host the servers and measure them. We don’t, so we can’t.
- Connector counts. There is no public count of Muse connectors. Any number we showed would either be invented, or be a count of our own incomplete list presented as if it were the catalogue.
- Rankings and “best of” ordering, unless and until we publish the method behind it.
- Paid placement. Nobody has paid to be listed here. Nobody can. If that ever changes, those slots will carry a visible “Sponsored” label and the appropriate link attribute, and this paragraph will change first.
Corrections
If something here is wrong, out of date, or about your product and shouldn’t be, tell us and we will fix it. Email hello@museaiconnectors.com with the page URL and what is wrong. A link we can check makes it much faster.
We will:
- correct anything demonstrably wrong, and re-date the listing;
- remove a claim we cannot support with a source, rather than defend it;
- take a listing down at the publisher’s request — being here is not something you opted into.
Every change to this site goes through a reviewed pull request in a git repository, so each listing has a real edit history rather than a rotating “updated” badge.
For machines
Everything we publish is available without scraping these pages: /api/connectors.json carries every listing with its evidence and check dates, and /llms.txt summarises the site for AI agents. If you cite us, please also cite the source we cite — it is in every record.
Independence
MuseAIConnectors is an independent directory. Not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. Muse is a trademark of its owner.
We use no Meta or Muse logos or brand colours, and we do not describe ourselves or anything we list as approved, endorsed or certified by Meta. Where we say a connector was announced, we mean a named source announced it, and that source is on the page.
Where to go next
- Search the connector directory — to find out whether your app works with Muse.
- The dated source timeline — everything behind the directory, in the order it was published.
- Submit or correct a listing.