A human OS. Add.
m·os·add — operating system for human communications.
Modular primitives — DMs, push-to-talk, rooms, calls, email, channels — and you add what you need.
Tagline-to-code real:
npx -y @mosadd/mcp…starts an MCP server with 40 tools across six mosadd OS modules. Drop it in Claude Code, Cursor, Cline, Windsurf, or any MCP-capable agent and tell the model to send a DM, spin up an ephemeral room with a no-signup join link, manage a persistent channel, send email, run a push-to-talk room, or recall facts from its own knowledge base — all through your own mosadd backend (BYOK).
| Channel | Tools | Highlight |
|---|---|---|
| mDM (6) | mDM_list_contacts, mDM_send, mDM_send_unencrypted, mDM_list, mDM_publish_keys, mDM_respond_request |
Multi-thread per contact (USP) + X3DH/Double-Ratchet E2EE |
| mTALK (5) | mTALK_open, mTALK_join, mTALK_press, mTALK_release, mTALK_state |
Half-duplex push-to-talk: one speaker, FIFO queue, anti-hog auto-release |
| mKB (1) | mKB_search |
RAG recall over the user's own messages/emails/calls (hybrid vector+BM25) |
| mIRC (17) | 5 channel ops (mIRC_create/list/get/update/delete) + 10 member ops (join/leave/kick/ban/unban/request-access/approve-request/reject-request/set-role/set-ptt) + 2 message ops (mIRC_post_message, mIRC_list_messages) |
Discord/Slack-style persistent channels, full RBAC + chat |
| mROOM (8) | mROOM_create, mROOM_create_guest_link, mROOM_join/leave/close/list, mROOM_send_message, mROOM_list_messages |
No other registered MCP server exposes single-call guest links |
| mAIL (2) | mAIL_send, mAIL_view |
Every user gets <userId>@mosadd.com for free |
Phase 1 follow-ups: mTALK (push-to-talk + agent in the room), mCALL (PSTN with vocoder + anonymized DID), mIRL (live-stream after-party), and bridges to Telegram / Discord / Matrix / Signal / Slack.
Alpha distribution: install directly from GitHub for now (
npx github:...). Once we claim themosaddnpm org,npx @mosadd/mcp@alphawill Just Work. The tarballs attached to release v3.0.0-alpha.0 are identical to what we'll publish.
claude mcp add mosadd npx -- -y github:Hei33enberg/mosadd-os --package=@mosadd/mcpThen set three env vars in your MCP config — see examples/claude-code/ for the walkthrough (including how to grab your session JWT from mosadd.com DevTools).
Drop examples/cursor/mcp.json into ~/.cursor/mcp.json (or your equivalent) and fill in the env. Restart the editor.
claude plugin install https://github.com/Hei33enberg/mosadd-os.gitThis installs the MCP server and the four skills/ — each SKILL.md teaches Claude when to invoke which channel.
You: "Create a room and give me a guest link for Bob, valid 1 hour."
Claude: calls
mROOM_create→mROOM_create_guest_link({ display_name: "Bob", ttl_seconds: 3600 })→ returns the share URL. Bob opens it in any browser. No signup. Done.
| Module | What | Status |
|---|---|---|
mDM |
Direct messages, multi-thread per contact, optional E2E | alpha (shipped) |
mTALK |
Push-to-talk voice, LLM-as-participant | Phase 1 (design in LINEAR-2145) |
mAIL |
Email, every user gets <id>@mosadd.com |
alpha (shipped) |
mCALL |
PSTN out, anonymous DID pool, vocoder | Phase 1 (design in LINEAR-2172) |
mIRC |
Persistent channels (Discord/Slack semantics) | alpha (shipped) |
mIRL |
Live-stream after-party (YT/TikTok creators monetize) | Phase 1 |
mROOM |
Ephemeral rooms + no-account join links | alpha (shipped) |
| Module | What | Status |
|---|---|---|
mMATRIX |
Matrix.org federation | Phase 1 P0 (LINEAR-2168) |
mDISCORD |
Discord DM + channel post | Phase 1 P0 |
mTELEGRAM |
Telegram DM + group | Phase 1 P0 |
mSLACK |
Slack workspace | Phase 1 P1 |
mSIGNAL |
Signal | Phase 1 P1 |
mWHATSAPP |
Phase 2 (legal review) | |
mIMESSAGE |
iMessage | Phase 2 (legal review) |
Community-contributed modules in v3.1+: mPOST, mWALL, mBROADCAST, mPING, mPAY, mVAULT, … RFC required — see RFC 0001.
Public OSS layer (Apache-2.0, this repo):
@mosadd/mcp— single MCP server, all channels (THE main artifact)@mosadd/core— channel primitives@mosadd/providers— vendor adapters (forked LiveKit, Routr SIP, nwaku p2p, Dendrite Matrix)@mosadd/bridges— Telegram/Discord/Matrix/Signal/WhatsApp (Hermes-derived)@mosadd/ai— framework adapters (Vercel AI SDK, LangChain, OpenAI Agents, Anthropic Agents)@mosadd/crypto,@mosadd/protocol,@mosadd/threat-engineapps/dev— the mosadd.dev developer portal (Next.js; deployed standalone via Vercel, Root Directoryapps/dev). Lives here, alongside the toolkit it documents.
Commercial hub (proprietary, hosted at mcp.mosadd.com + hub.mosadd.com):
- Hosted MCP gateway with OAuth + BYOK key broker
- 167-event threat radar middleware (the moat)
- Unified billing across providers
- Multi-provider PSTN failover orchestration
- Enterprise self-host packaging + NIS2 audit trail
Built for the agent era (Claude Code, Cursor, Lovable, Manus, ChatGPT Apps) — first-class MCP support, semantic OS primitives instead of vendor-shaped tool wrappers. Vendor-agnostic across our forked stack + Telnyx/Twilio/Matrix/Discord backends. Managed threat radar watching every message, call, and bridge — the moat nobody else ships.
Read docs/roadmap.md for the full plan or jump to the M5 milestone for live status.
We're an open community. Start with CONTRIBUTING.md, GOVERNANCE.md, and the RFC index.
Adding a new m* module requires an RFC — see RFC 0001 for the bar (semantic primitive, ≥2 backend providers, radar hooks, MCP tool surface).
Discord: coming soon · Web: mosadd.dev · Linear: M5 epic
Apache-2.0. Patent grant included. Compatible with proprietary use.
This project includes or adapts code from:
- LiveKit (Apache-2.0) — vendored as
forks/livekit-server/, rebrandedm0ssad-fabric - Hermes Agent (MIT, Nous Research) —
gateway/platforms/adapted topackages/bridges/ - @noble/curves, @noble/ciphers, @noble/hashes (MIT) —
@mosadd/crypto - Several other dependencies — see full attribution in NOTICE.