Short answer: not through Muse's own connector directory — no social media scheduler is listed there yet, seenpaid included. What does work today is a custom connector: ask Muse, in plain language, to add a connector for a scheduler's MCP server URL, and it builds the connection itself. That route isn't reviewed by Meta and isn't the same as being listed, but it's real and it works right now.
I make seenpaid, a scheduler that submitted a directory listing on 20 September 2026, so read this with that in mind. Everything about Muse below comes from Meta's own pages (muse.ai/platform, Meta's Help Center) and Mark Zuckerberg's own 18 September post, read on 24 September 2026 — plus one direct email Meta sent seenpaid, as a submitter, on 24 September, which I quote rather than a public link because there isn't one.
- Muse's connector directory (Settings → Connectors): built-in and Meta-reviewed connectors only. No scheduler is in it today.
- Custom connectors ("add a connector for this URL"): work today, for any MCP server, unreviewed by Meta.
- seenpaid's directory listing: submitted 20 September 2026, status submitted, not approved.
- Today, to post from an AI agent: ChatGPT's plugin directory (seenpaid approved 24 September) or a custom connector in Muse or Claude.
Last verified: 24 September 2026.
What a Muse connector actually is
Muse launched 8 September 2026 — personal AI agent, its own app plus muse.ai and WhatsApp, United States only, 18+. It shipped with a handful of built-in connectors (Gmail, Apple Health, Android SMS, and Meta's own Facebook, Instagram and Threads, auto-connected), added the normal way: ask Muse to connect one, or go to Settings → Connectors and authorize it.
On 18 September, ten days after launch, Meta opened that up to outside developers. Zuckerberg posted the news himself and pointed to muse.ai/platform, a page with one button — "Submit a connector" — describing three steps: describe your product, Meta reviews it "for functional, security, and legal requirements, and complete[s] end to end testing," and once approved, "users will be able to find your connector in Muse. Editors will review connectors for featured placement." The same page says Muse has "partnered with Stripe to make accepting payments easy with Link" for connectors that charge for something. No connector config format is published — Meta reviews and lists what you submit; it doesn't hand developers a spec to implement against.
That's the directory path: submit, get reviewed, get listed, users find you by name or Muse surfaces you when it's relevant. It's a different thing from a custom connector, below, and as of today no scheduler has gone through it.
What's actually live in the directory today
Per Meta's own Connect keynote (23 September) and Muse's own account, the launch partners named so far are shopping and payments: Stripe and Shopify (with Lync and Shop Pay for checkout), plus retail connectors for Best Buy, Gap, Sephora, Walmart and Wayfair, and productivity connectors for GitHub, Notion and Granola. Muse's own account was explicit on 23 September that a fresh batch — Shopify, PayPal, Expedia and Instacart — was "announced in the last 24 hours, all coming soon," not live yet. Meta said it had received more than 1,500 third-party developer submissions in the platform's first week.
None of that is a social media scheduler. As of 24 September 2026, there is no post-scheduling or cross-posting connector in Muse's directory — not seenpaid, not a competitor.
Where seenpaid actually stands
seenpaid submitted a directory listing on 20 September 2026. On 24 September, Meta emailed everyone who'd submitted: more than 2,000 submissions received, a developer portal coming "in the coming days," and developers being onboarded "in waves over the coming weeks." That's a queue, not a rejection, and not an approval either — seenpaid is not listed in Muse's directory today, and this post isn't claiming otherwise. When that changes, this page will say so with the same directness.
The custom-connector route: what already works, today
Separately from the directory, Meta's Help Center describes a second path that needs no review: "request Muse create a custom connector" for a service it doesn't already have. Muse fetches from the service's API, stores any credentials in a secure vault, and — its own words — "Meta does not review custom connectors or how they use your information," so it tells you to grant access carefully and check the provider's own privacy policy.
That's the route that works for seenpaid right now: ask Muse to add a custom connector for https://api.seenpaid.com/mcp, hand it a seenpaid API key when it asks, and it builds and saves the connection as a skill — same MCP server, same tools, as any other client on this site. Full steps:
One competitor says the same thing about itself
Postiz, another scheduler, published its own Muse explainer on 22 September 2026 (postiz.com/blog). Its FAQ is direct: "Not yet. Postiz is not listed in the Muse connector directory today. You connect it yourself through the 'Custom' path with the Postiz MCP link." That's the same distinction this post is making, from a company with no reason to undersell its own directory status if it had one. Worth knowing if you came here after reading that post and wondering whether the goalposts had moved since — they hadn't, for either of us, as of 24 September.
What to use today instead
- ChatGPT's plugin directory — seenpaid was approved there on 24 September 2026. Reviewed, listed, no URL to paste.
- Claude (claude.ai or Desktop) — add any scheduler's MCP server as a custom connector; works on every plan, Free is capped at one.
- Muse — the custom-connector route above works today; the directory listing doesn't exist yet, for any scheduler.
What changes once a scheduler is actually listed
Being in the directory doesn't add capability — the MCP tools are the same either way, list_accounts, validate_post, schedule_post, list_posts. What it changes is discovery and trust: Muse can surface a listed connector when it's relevant instead of you naming a URL, and Meta has reviewed it rather than you taking a developer's word for what it does with a key. Until that's true for any scheduler, the custom-connector route and Meta's own "we don't review these" warning both still apply.
Sources
Checked 24 September 2026: muse.ai/platform (submission steps, review, Stripe Link); meta.com/help/artificial-intelligence/1687253048996149 (How Muse works with Connectors — built-in connectors, custom-connector steps, the no-review warning); x.com/finkd/status/2101084678640066765 (Zuckerberg's 18 September post); techcrunch.com/2026/09/23/everything-new-coming-to-metas-ai-agent-muse (Meta Connect connector partners, 1,500+ submissions figure); postiz.com/blog/meta-muse-ai-connectors-schedule-social-media-posts and postiz.com/muse (22 September, Postiz's own directory-status FAQ); Meta's email to seenpaid as a directory submitter, 24 September 2026 (2,000+ submissions, portal timeline, onboarding in waves) — not public, quoted rather than linked.