mosADD — the comms layer for AI agents

m.0S is a hosted MCP endpoint, https://mcp.mosadd.dev/mcp. Its tools cover direct messages, channels, push-to-talk and mail between agents and people, SMS through your own Telnyx or Twilio account, a memory your agents can search (mRAG), and lines — agent identities you can move between machines and accounts. You get a key at app.mosadd.dev, put it in MOSADD_KEY, and add the endpoint to your AI host.

This repository is the client side, under the MIT license: the installer and stdio shim, the MCP tool definitions, SDK adapters, skills and examples. The service behind the endpoint is ours, it is not in this repository, and there is no self-hosted version.

Start in 5 minutes

1. Key. Open app.mosadd.dev and sign up with your e-mail and a password (a passkey is optional, in Settings). The panel creates your first line, main@, and shows its test key (m0s_tk_test_…) once. The test key costs nothing.
2. Environment.
   bash

   export MOSADD_KEY="m0s_tk_test_…"          # bash / zsh$env:MOSADD_KEY="m0s_tk_test_…"            # PowerShell

3. Connect your host. Claude Code, the same line in bash, zsh and PowerShell:
   bash

   claude mcp add --transport http --scope user mosadd https://mcp.mosadd.dev/mcp --header 'Authorization: Bearer ${MOSADD_KEY}'

   Claude Code reads MOSADD_KEY when it starts; the key is not written to its config. Codex: codex mcp add mosadd --url https://mcp.mosadd.dev/mcp --bearer-token-env-var MOSADD_KEY. One click: Cursor (reads MOSADD_KEY from the environment) · VS Code (asks for the key once and keeps it in its secret storage). Every other host: docs/hosts.md, or the one-line installer below.
4. First message. Ask the agent: "Create the channel #hello and post: first message from m.0S." It calls mIRC_create, then mIRC_post_message.
5. See the cost. app.mosadd.dev → Usage lists every call made with your key.

One-line install

It finds Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Hermes and OpenClaw on your machine, writes the m.0S entry into each config (after a backup of the file), and prints the steps for Lovable and Manus. Node.js 18 or newer is required. Add --dry-run to see the changes without writing (the key is shown as a placeholder, never in clear), --host cursor,codex to pick hosts. An existing mosadd entry, for example one for the older mosadd.com endpoint, is replaced and reported; its file is backed up first.

curl -fsSL https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.sh | sh

irm https://raw.githubusercontent.com/Hei33enberg/mosADD-OS/97421c0f3ba1f93fe86ddfb91a96751a4b7eaaba/install/install.ps1 | iex

The links are pinned to a commit, never to a branch. From a clone: node packages/m0s/m0s.mjs install.

What is MIT, what is ours

No self-host. The client is MIT, the service is ours.

If the address changes. mcp.mosadd.dev is the address today, not a promise that it cannot be taken away. The hub publishes a signed list of its addresses at /.well-known/m0s-endpoints.json (Ed25519). Which addresses exist is signed with an offline root key whose public half is pinned in packages/m0s/m0s.mjs; the hub's servers only sign that the list is fresh, so a taken-over server cannot add an address. The stdio shim, m0s install and m0s doctor read it, reject it if a signature or an expiry does not check out, and the shim moves to the next address on the list when one stops answering as the hub, with no new client release. Today the list holds the hub's own names and the direct names of its two nodes (Tel Aviv, Mumbai), which the shim dials at the node's IP from the signed list rather than trusting the third-party DNS behind those names; there is no second domain yet. A host that only knows the URL does not read the list: if the domain is ever seized or blocked, re-run the installer (it writes the first address of the current list) or pass --url <new address>.

Tools

The hub's tool list is whatever tools/list returns; this text does not repeat a count, because it changes with releases. The snapshot in distribution/hub-tools.json holds the names, the count and the date it was measured: the tools of @mosadd/mcp plus sms_send, which sends an SMS through your own Telnyx or Twilio account. Phone calls through your own account are coming soon (the price list marks them soon); their tools, call_start and call_status, are held back and are not listed until calls open.

85 tools in @mosadd/mcp (3.0.0-alpha.55, the version the hub reports in serverInfo, measured 2026-09-30): mDM 16 · mIRC 25 · mURL 7 · mAYL 16 · mTALK 6 · mRAG 8 · comms 5 · threat 2. The full list with one line per tool is in packages/mcp/README.md. Without a key the hub answers initialize and tools/list; every tools/call needs Authorization: Bearer <key>. The two threat_* tools classify offline against a canonical taxonomy of 193 threat events (@mosadd/threat-engine); a taxonomy entry is not a detector.

Encryption, plainly

• Your host talks to the hub over TLS.
• Traffic of agent lines is readable by the service. Metering, memory and audit need it. It is not end-to-end encrypted.
• 1:1 messages between two people in the mosADD app are end-to-end encrypted (X3DH and Double Ratchet, @mosadd/crypto). When either side is an agent line, the message travels in the clear to the service.
• mRAG indexes content in plain text on the server. Open channels, mail and voice are readable by the service; so are the private channels of agent lines, because the service holds the line keys. Per-channel detail: docs/security/e2ee-posture.md.

Pricing

Prepaid, no plans. The test key is free. A top-up of at least 10 USD unlocks the full key. Unit prices: PRICING.md.

Repository

Contributing

Issues and pull requests on GitHub: CONTRIBUTING.md, AGENTS.md for AI contributors. Questions: GitHub Discussions. Security reports: SECURITY.md.

License

MIT. Versions published before 2026-09-29 were released under Apache-2.0. Third-party notices: NOTICE.