Mebular
The decentralized memory layer for AI agents — offline-first, signed knowledge graph with validity & provenance, P2P sync across every device you own. MCP tools.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Windsander/Mebular with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Windsander/Mebular'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/windsander--mebular)HTML
<a href="/listings/windsander--mebular"><img src="/api/listings/windsander--mebular/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 192 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <div align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/banner-light.svg">
- <img src="assets/banner.svg" alt="Mebular">
- </picture>
- **One memory. Every assistant. Every device.**
- A distributed memory network for your AI assistants.<br>
- Memory and tasks stay on your devices; devices sync directly.
- [](https://github.com/Windsander/Mebular/actions/workflows/ci.yml) [](LICENSE) [](docs/getting-started/QUICKSTART.md) [](docs/getting-started/QUICKSTART.md) [](https://awesome-dsh-plugin.com/p/Windsander/Mebular--packages-dsh-plugin/)
- [Start in 5 minutes](docs/getting-started/QUICKSTART.md) · [How it works](docs/architecture/ARCHITECT.md) · [Website](https://mebular.cyberfederal.io) · [中文](README_CN.md)
- <sub>No hosted account · No central coordinator</sub>
- </div>
- ---
- <p align="center">
- <img src="assets/star-map-baseline-en.jpg" width="49%" alt="Star map baseline: the device network before hovering">
- <img src="assets/star-map-lanes-en.jpg" width="49%" alt="Task lanes and a fleet event: blue can send, gold can receive, gray unreachable">
- </p>
- <p align="center"><sub>The map at rest: devices and their shared-subscription edges. · On hover: task-domain lanes plus live fleet traffic.<br>Blue and gold show this device's two-way task-domain reachability, not peer-to-peer links.</sub></p>
- ## One memory
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/one-graph-en-light.svg">
- <img src="assets/one-graph-en.svg" alt="Why Mebular: one shared graph instead of a silo; local-first, direct sync, auditable, MCP">
- </picture>
- </p>
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/memory-runtime-en-light.svg">
- <img src="assets/memory-runtime-en.svg" alt="Memory Runtime: lightweight MCP and immersive access share one graph">
- </picture>
- </p>
- <p align="center"><sub>0.3 adds an optional runtime above MCP. Default off; local Qwen optional.</sub></p>
- <p align="center"><a href="docs/guides/MEMORY_RUNTIME.md">Memory Runtime guide</a> · <a href="docs/integrations/DSH.md">DSH</a> · <a href="docs/integrations/HERMES.md">Hermes</a> · <a href="docs/integrations/OPENCHAMBER.md">OpenChamber</a></p>
- ## Get started
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/dsh-plugin-en-light.svg">
- <img src="assets/dsh-plugin-en.svg" alt="DSH plugin integration: the DSH sidebar loads the same Mebular Console, and the official MCP client reaches the same daemon">
- </picture>
- </p>
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/desktop-steps-en-light.svg">
- <img src="assets/desktop-steps-en.svg" alt="Desktop app setup: 1 Start deployment, 2 Create or join a Cloud, 3 Invite the next device">
- </picture>
- </p>
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/other-paths-en-light.svg">
- <img src="assets/other-paths-en.svg" alt="Other ways to start: Browser, CLI and Agent, all sharing one graph">
- </picture>
- </p>
- <table width="100%">
- <thead>
- <tr>
- <th align="left" width="30%">Desktop app · v0.3.4</th>
- <th align="left">Download & first launch</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><strong>Unsigned release</strong><br><sub>macOS Universal · Windows x64 · Linux x64</sub></td>
- <td><a href="https://github.com/Windsander/Mebular/releases/tag/v0.3.4">Download from GitHub Releases</a><br><sub>Verify with <code>SHA256SUMS.txt</code>. macOS: right-click → <strong>Open</strong>. Windows: <strong>More info → Run anyway</strong>. Bundles Electron and its runtime.</sub></td>
- </tr>
- </tbody>
- </table>
- **Or install the CLI and server:**
- ```bash
- npm install -g @mebular/core
- mebular serve # browser console
- fleet quickstart --daemon # CLI start
- mebular print-config --client opencode # MCP config
- ```
- ## How it works
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/network-overview-en-light.svg">
- <img src="assets/network-overview-en.svg" alt="Mebular network overview: each machine runs one node; nodes sync memory and tasks directly; add devices with a QR code or token">
- </picture>
- </p>
- <p align="center"><sub>Write with <code>memory_write</code>, hand off with <code>task_submit</code> — the same graph, from any assistant.</sub></p>
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: light)" srcset="assets/pairing-flow-en-light.svg">
- <img src="assets/pairing-flow-en.svg" alt="Pairing flow: device A invites, device B joins with the QR code or token, then connection and the default grant happen automatically">
- </picture>
- </p>
- ## Docs
- <table width="100%">
- <thead>
- <tr>
- <th align="left">Start</th>
- <th align="left">Learn</th>
- <th align="left">Run</th>
- <th align="left">Trust</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><strong><a href="docs/getting-started/QUICKSTART.md">Quickstart</a></strong><br><sub>Install & pair</sub></td>
- <td><strong><a href="docs/architecture/ARCHITECT.md">Architecture</a></strong><br><sub>Nodes & sync</sub></td>
- <td><strong><a href="docs/console/README.md">Console</a></strong><br><sub>Local GUI</sub></td>
- <td><strong><a href="docs/limitations/LIMITATIONS.md">Limitations</a></strong><br><sub>Sensitive data</sub></td>
- </tr>
- <tr>
- <td><strong><a href="packages/skill/SETUP.md">Agent skills</a></strong><br><sub>Setup playbooks</sub></td>
- <td><strong><a href="packages/fleet/RUNBOOK.md">Fleet ops</a></strong><br><sub>Multi-machine</sub></td>
- <td><strong><a href="docs/operations/RELEASE.md">Release SOP</a></strong><br><sub>Release steps</sub></td>
- <td><strong><a href="SEALING.md">Sealing docs</a></strong><br><sub>Protocol rules</sub></td>
- </tr>
- <tr>
- <td><strong><a href="CHANGELOG.md">Changelog</a> · <a href="ROADMAP.md">Roadmap</a></strong><br><sub>Released & planned</sub></td>
- <td><strong><a href="CONTRIBUTING.md">Contributing</a></strong><br><sub>Quality gates</sub></td>
- <td><strong><a href="SECURITY.md">Security</a></strong><br><sub>Report a vuln</sub></td>
- <td><strong><a href="https://mebular.cyberfederal.io">Website</a></strong><br><sub>Product site</sub></td>
- </tr>
- </tbody>
- </table>
- <p align="center"><strong>Community</strong><br>
- <a href="https://github.com/Windsander/Mebular/discussions">Discussions</a> · <a href="https://github.com/Windsander/Mebular/discussions/categories/q-a">Q&A</a> · <a href="https://github.com/Windsander/Mebular/issues">Issues</a> · <a href="ROADMAP.md">Roadmap</a> · <a href="CONTRIBUTING.md">Contributing</a><br>
- <sub>Usage questions → Q&A · early ideas → Ideas · reproducible problems → Issues</sub></p>
- <p align="center"><strong>Use with DSH</strong><br>
- Install the plugin from npm into DSH's web profile:<br>
- <code>dsh plugin --profile web add @mebular/dsh-plugin@0.3.4</code><br>
- The App and the DSH Plugin are two equal entries to one local Mebular runtime: the plugin defaults to <code>attach</code> and connects to an existing App/CLI/service without starting or downloading anything. If no runtime exists, the panel explicitly offers a pinned shared-runtime install. The sidebar panel embeds the same Console through <code>?embed=dsh</code> (loopback only), and the official MCP client reaches the same graph. The plugin is an independent adapter with its code isolated in <code>packages/dsh-plugin</code>; it is published by its own npm job, while its version follows the unified release train. For plugin development, install from <code>packages/dsh-plugin</code> instead.<br>
- Listed under <code>memory</code> on <a href="https://awesome-dsh-plugin.com/p/Windsander/Mebular--packages-dsh-plugin/">awesome-dsh-plugin</a> and <a href="https://dshmarketplace.dev/plugins?q=mebular">dshmarketplace.dev</a>; every other directory is tracked in <a href="docs/community/LISTINGS.md">community listings</a>.<br>
- <a href="packages/dsh-plugin/README_EN.md">DSH plugin guide →</a> · <a href="docs/integrations/DSH.md">Integration notes →</a></p>
- <details>
- <summary>Who does what</summary>
- | Who | Handles |
- |---|---|
- | **You** | One-time pairing, Cloud choice, invites, subscriptions. |
- | **Your assistant** | Memory reads and writes, task claim and completion. |
- | **Mebular** | Discovery, direct / relay / hole-punch, retries, certificates, service autostart. |
- </details>
- <details>
- <summary>Use it from code</summary>
- ```ts
- import { Mebular } from 'mebular';
- const mebular = new Mebular({
- storagePath: './store.jsonl',
- deviceId: 'device-a',
- network: { enabled: false },
- });
- await mebular.initialize();
- ```
- Runnable examples: [`examples/quickstart`](examples/quickstart/index.mjs) writes and recalls a preference; [`examples/two-devices`](examples/two-devices/index.mjs) demonstrates offline sync.
- </details>
- <div align="center">
- v0.3.4 · early · MIT · © 2026 Sobert Li
- </div>
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.