Entries matching “directory”

Meta's developer portal for Muse connectors: describe a connector, submit it for functional, security and legal review plus end-to-end testing, and get listed in the Muse directory.

OpenTools maintains a source-backed directory of about 163 Muse connector setup guides, separating Meta-documented, partner-documented and community skills (e.g. HubSpot, Attio, Ashby, Plaid, Slack), with status labels such as draft or maintainer-tested.

Greg Isenberg explains how a Muse connector works, pitches four startup ideas to build on one, and covers getting customers beyond Meta's directory.

armand

@armand_ruiz

I went through hundreds of posts to find what people are actually getting done with @muse. 128 real use cases, organized by category; each with the original source and a prompt you can copy. muse.ai/s/muse-use-cas…

@star-power0

@star-power0

muse-fileapi is a dependency-free local HTTP service exposed via Cloudflare Tunnel that lets Muse, through a custom connector, list, read and write files in whitelisted directories with two-phase writes and an audit log.

Sprites.ai lists every Meta Muse connector (39 live, 17 announced, updated after Connect 2026) and sells a custom connector that reaches Google Ads, Meta, LinkedIn, TikTok, Reddit, GA4 and Search Console through one endpoint.

CellCog explains the Muse connector platform: a three-step describe/review/list flow at muse.ai/platform, directory vs custom connectors, and Stripe Link payments.

I've been migrating my workflow from ChatGPT Work / Codex over to Meta's Muse, and I've been auditing the harness as I go — reading cron files, checking diffs, mapping what the system actually does versus what it claims to do. It's a documentation gap. What the docs describe Meta's documentation is written for a normal user. It talks about the Ideas tab, the Goals tab, the Feed, and "background jobs that help Muse improve over time." Everything is described in terms of what it does for you. There is no architectural documentation. Nothing about how any of it is built. What is actually on disk Meanwhile, the home directory contains a fully legible agent architecture, just sitting there(these are just SOME examples, the system file structure is HUGE): • ~/dreams/alignment/ — a nightly job that regenerates an alignment synthesis: a written portrait of the user, how to handle them, current frictions, relationship guidance. • ~/workspace/objectives/goals/STUDYING.md — a daily learning-state projection with mastery bands, next-review dates, and retrieval prompts, plus a file of inferred goal leads the system guessed from behavior (with confidence levels and what would confirm or re

KP

@thisiskp_

14 new Musecases: (total 156) @raunaqbn had Muse call Xfinity and lock ~$5,118 @nathanael_smith cut a WiFi bill $300 in under 10 min @JasonL_Capital shopped identical auto coverage (~$1,156/yr) at the gym @NoSaberNiPapa got AT&T $80→$30/mo with 2x speed

@mlmrx

@mlmrx

Independent open-source community and connector directory for personal agents: search connectors by outcome, share workflow prompts, and import an OpenAPI 3.x document to prepare a connector listing.

Decensored Muse Glimmer 30B made with Heretic v1.4.0, shipped with a reproduce directory.

@emman27

@emman27

MCP server built for the Muse connector directory that answers Singapore bus arrival times and MRT/LRT service questions using the official LTA DataMall API.

@sureshsankaran

@sureshsankaran

A Muse workspace skill for managing GitHub repos through the REST API, including pushing directories via the Git Data API, with the token kept in the Muse vault.

Postiz's Nevo David shows how to hook Postiz's OAuth MCP server into Muse through the custom-connector path, so Muse can schedule posts across 30+ platforms before an official directory listing.

ContextBolt's founder shows how to connect the hosted ContextBolt SEO MCP server to Muse, either from the connector directory or as a custom connector, for keyword research, live SERPs and site audits.