@mindbridgeio/muse
v0.1.2
Published
MindBridge MCP and lifecycle hooks for Muse.
Readme
@mindbridgeio/muse
MindBridge MCP tools and lifecycle hooks for Muse, using durable OAuth.
npx -y @mindbridgeio/muse@latest setupThe command writes the streamable_http MCP server and native lifecycle hooks
into ~/.config/muse/settings.json (or $XDG_CONFIG_HOME/muse/settings.json),
starts Muse's MCP login, then signs lifecycle hooks in through the system
keychain. It uses https://memory.ifelse.io by default; pass
--server-url https://… or set MINDBRIDGE_MCP_SERVER_URL for a nonsecret
server override. The server entry merges into whichever MCP section already
exists (mcpServers or mcp_servers), since Muse faults the config when both
spellings are present.
npx -y @mindbridgeio/muse@latest auth status
npx -y @mindbridgeio/muse@latest auth logout
npx -y @mindbridgeio/muse@latest doctorNo Bearer [REDACTED] is placed in Muse configuration, command arguments, or an environment variable. A keychain is required; setup fails safely when one is unavailable.
Setup validates the server, Muse CLI, and keychain before changing config. If
MindBridge is temporarily unavailable, hooks remain non-blocking and replay
redacted pending events from a bounded local outbox. doctor --json reports
MCP configuration, lifecycle OAuth, and outbox health. The MCP server is
registered as optional so a MindBridge outage can never abort a session.
New sessions are tagged automatically from Muse's working directory. Git repositories use a credential-free remote identity; non-Git directories use a private install-scoped local identity. Recall prefers the current project and then fills from the wider MindBridge workspace.
