awesome-muse-connectors
Anil-matcha · Anil-matcha/awesome-muse-connectors
A community catalog of 150 connector skills and Meta Muse integrations, with notes on capabilities, authentication and permissions.
A source-backed catalog of Meta Muse integrations and community connector skills, with capability, authentication, and permission notes.
Preview
What you can do with it
- Browse connector skills to link your agent to third-party services
- Check authentication and permission notes before installing a connector
- Find a starting point for automating an API workflow
Safety check
No risky patterns found in the files we scanned.
Automated scan of the repo files. Always review code you run.
From the README
▶ Watch: Free Open Source Instinct AI Alternative: Unlimited, Any Model
Awesome Muse Connectors
A community-maintained catalog of integrations and connector skills for Meta Muse.
This repository includes Meta-named integrations and 150 community connector skills copied from an MIT-licensed project. The copied skills retain their source license and are listed in the connector catalog. Community skills are distinct from Meta's built-in connectors. Review their permissions and maturity status before use; availability and provider APIs can change.
This is an independent community collection. It is not affiliated with, endorsed by, or operated by Meta.
Related Projects
- Awesome Jev by TypeSafe — typed, confidence-aware decision workflows.
- Awesome Grok Bot — copy-paste bot briefs for persistent AI teammates.
- Awesome GPT-6 Astra — evidence-backed model use cases, prompts, and evaluations.
- Awesome Dots Connectors — the companion catalog mirroring this repository’s 150 community connector entries for OpenAI Dots; Dots compatibility is not yet verified.
- Open Grok Bot — local-first bot-persona workspace with approvals and audit trails.
- Awesome OpenClaw — self-hosted agent resources, skills, and integrations.
- Awesome Hermes Agent — agent workflows and creator-focused automation resources.
- MuseBot — a separate open-source, multi-platform chatbot implementation.
Connector catalog
Browse 150 copied connector skills with descriptions, authentication notes, allowed hosts, operating rules, and maturity status. The built-in connectors named by Meta are also summarized there with source links.
Pull requests are welcome. Add a connector with a source-backed capability description, credential and host boundaries, explicit write approvals, a tested file manifest, and an honest maturity label. See CONTRIBUTING.md.
Agent workflow templates
The original 12 workflow templates remain under templates/ as supporting examples for using Muse and its connectors.
What makes a good Muse bot
Muse can take a broad objective, gather context from connected apps, work through multiple steps, and return for approval when an action is sensitive. A useful bot brief gives that capability a narrow, testable shape.
| Weak brief | Strong brief |
|---|---|
| “Manage my life.” | “Every morning, turn today’s calendar and approved task list into three priorities and a time-aware plan.” |
| “Research this company.” | “Compare the company’s current pricing, public product changes, and three primary sources; link every claim and mark uncertainty.” |
| “Handle my inbox.” | “Classify messages, draft replies, and show the exact send/archive action for approval.” |
| “Run my release.” | “Inspect the milestone, checks, issues, and changelog; prepare release notes and stop before any merge or publish action.” |
The collection follows six principles:
- One job per bot: a bot may have a rich workflow, but it should have one recognizable outcome.
- Context before personality: define the sources, constraints, vocabulary, and examples before choosing a tone.
- Output contracts: specify the table, brief, draft, checklist, or decision record the bot should return.
- Approval by action: reading, drafting, sending, publishing, purchasing, deleting, and changing permissions are different risk levels.
- Evidence over confidence: important claims should link to the message, file, page, event, or record that supports them.
- A graceful stop: ambiguity, missing access, conflicting instructions, and irreversible actions should produce a question—not a guess.
How to use a template
- Check the Muse download page for current access, then open Muse in the app or WhatsApp where available.
- Start a new conversation and copy the prompt from one of the templates below.
- Paste it into Muse and answer its setup questions.
- Connect only the apps the workflow needs.
- Run the first task under supervision. Keep approval required for sending, purchasing, deleting, publishing, or sharing.
Templates are starting points, not unattended automation recipes. Replace bracketed fields, narrow the scope, and tell Muse what it must never do without your approval.
Current availability and connector limits
At launch, Muse was available in the United States to adults 18 and older through the Muse app and WhatsApp, according to Meta and the Associated Press. Check the official download page for current regional and account eligibility before setting up a workflow. Meta announced at Connect on September 23, 2026 that Muse is coming to its AI glasses; treat glasses access as announced, not as a generally available interface, until the current product page confirms availability.
Connector access is not guaranteed just because a browser can reach a service. For example, Axios reported on September 21, 2026 that Amazon blocked Muse from browsing and buying on its store, citing lack of authorization. A template must not instruct Muse to bypass a site's access controls or service-provider decision. When access is denied, stop and use permitted sources or ask the user to choose another route.
Contents
| Section | What it covers |
|---|---|
| Connector catalog | Meta-named integrations and community connector skills |
| Agent workflow templates | Existing prompts for using Muse and integrations safely |