Skip to main content
Glama

mosADD

One person commands people, AI agents and robots from one phone: mRAG remembers, mADD keeps order, push-to-talk gives the orders.

npm License: MIT

mosadd.com · Docs · Changelog

The products

What works today, product by product.

1. mDM: one thread per contact, person or agent

Direct messages between two people are end-to-end encrypted, and agents sit on the same contact list as people. On Slack, guests cannot use agents; on Telegram, bots generally cannot see other bots' messages.

  • mTXT is text. mDM between people is end-to-end encrypted (X3DH + Double Ratchet, @mosadd/crypto). Telegram encrypts only single-device Secret Chats; Slack and Discord have no end-to-end encrypted text.

  • mTALK is push-to-talk inside the thread: hold, speak, let go. The transcript goes to memory.

  • mAYL is the same contact by mail: your agent gets its own mailbox in one MCP call.

2. mIRC: channels

  • Open channels anyone can find and join.

  • Closed channels by invite or request, with roles, bans and guest links.

  • mURL puts a room on any website or domain; anyone joins with no account.

  • mTALK in channels: one speaker at a time, moderators grant the floor. Slack lists push-to-talk only in the mobile huddle menu.

3. mAYL: a mailbox for every agent

Your agent gets its own mailbox in one MCP call, sends mail as the agent, and you see opens, clicks, and a signed audit report.

4. mRAG: one memory

Open channels, your notes, voice transcripts and mail become one searchable memory that you and the agents you allow can query. End-to-end encrypted chats never reach it. Signal: we found no AI memory or semantic search. Slack's real-time search API forbids storing or copying the data it returns.

5. And the rest

  • mADD, your personal admiral, only when you ask: write @mADD in your own thread; it files the task, hands it to an agent after you confirm, and tells you who is stuck.

  • MCP: npx @mosadd/mcp gives your agent its own line: 85 tools over MCP, MIT licence. Telegram and Signal have no official MCP server.

Related MCP server: hauddy

Connect your AI

claude mcp add --transport http mosadd https://mcp.mosadd.com/mcp

Run /mcp, pick mosadd, sign in. Or run npx -y @mosadd/mcp. Codex, Cursor, Windsurf, Hermes and other MCP clients: docs/hosts.md.

First order: "Create the channel #hello and post: first message from mosADD."

The deck

Product

What it is

mDM

one thread per contact: mTXT, mTALK, mAYL

mIRC

open and closed channels, and mURL rooms on any site

mAYL

a mailbox for every agent

mRAG

one memory for all of it

mADD

your personal admiral, only when you ask

MCP

your agent's own line: 85 tools, MIT licence

Tools

85 tools in @mosadd/mcp (run npx @mosadd/mcp tools for the full list): mDM 16 · mTALK 6 · mIRC 25 · mURL 7 · mAYL 16 · mRAG 8 · comms 5 · threat 2

Open core

This repository is the open toolkit around mosADD. It does not contain the hosted app.

In this repo

Not in this repo

What

MCP server, SDK adapters, agent runner, crypto and protocol libraries, agent skills, examples, docs

The hosted app and backend at mosadd.com

License

MIT

BUSL 1.1 licence, private repository

Your account, keys, message delivery, channels, mail, voice and memory run on the mosADD service. There is no self-hosted version of it. Everything here is a client of that service.

Packages

All under packages/, all MIT.

Package

What it is

Version

@mosadd/mcp

The MCP server: every mosADD module as tools for your agent

npm

@mosadd/ai

Adapters for the Vercel AI SDK, LangChain, OpenAI and Anthropic

npm

@mosadd/agent

A local agent runner that answers as a mosADD contact

npm

@mosadd/crypto

X3DH, Double Ratchet, AES and HKDF for 1:1 messages between people

npm

@mosadd/protocol

Message schemas and codecs (Zod)

npm

@mosadd/providers

Transport interfaces

npm

@mosadd/threat-engine

Threat-event taxonomy, scoring and a pure decision engine

npm

@mosadd/m0s

Installer and stdio shim that writes the MCP config into your host

not on npm

@mosadd/messenger

messenger.json: describe a messenger from mosADD blocks and validate it

not on npm

Also here: skills/ (agent skills and Claude Code plugin), examples/, docs/.

Licenses

Part

License

This repository and all nine @mosadd/* packages

MIT

@mosadd/crypto

MIT; original upstream notice kept in LICENSE.original-MIT

Third-party code

see NOTICE

The hosted app at mosadd.com (private repository)

BUSL 1.1 licence, not open source

The mosADD name and logo are covered by TRADEMARK.md.

mosadd.com · Docs · Changelog · CONTRIBUTING · SECURITY · CODE_OF_CONDUCT · Discussions

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.
      3
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send and receive iMessages and emails, and manage agent identities, in MCP-compatible clients.
      6
      20 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to exchange end-to-end encrypted, threaded email-style messages across tools, vendors, and machines through a zero-install remote MCP server. Supports sending, replying, reading, and threading messages with inbox checks, read receipts, and key verification.
      MIT