Side Chat IDs Are Addresses

Description and use

muse‑mcp turns a Muse chat ID into a routable address, providing full CRUD and conversational automation on a self‑hosted Linux server.

Problem

Muse chat IDs are routable addresses, but the official SDK does not expose operations to enumerate or manage chats, limiting automation.

Outcome

muse‑mcp turns a Muse chat ID into a routable endpoint, enabling full CRUD and conversational automation on a self‑hosted Linux server.

Workflow

• Pair a Linux host as a Muse Link device via the SDK
• Run muse‑mcp as a systemd service on a general‑purpose Linux host
• Use the registry sync tool to enumerate chats and build a local address book
• Invoke CRUD tools (create, list, rename, archive, delete) through the Bridge chat
• Send messages and ask questions via the ask tool
• Monitor status and history tools for conversation state

Evidence

A Muse chat ID is not just an identifier the app uses internally. It is a routable address.

Source

muse-mcp is the address book, the directory service, and the delivery mechanism, in one server.

Source

The first registry sync made the premise visible in one line of output: 125 enumerated chats, 5 registered, 120 unregistered drafts, 56 archived.

Source

There is no unread state. I probed the SDK across its Linux, ESP32, Android, iOS, and web-flasher sources for the blue dot. There is no unread field, no unread count, no read or seen receipt, no mark-as-read endpoint.

Source