EverMe-for-SeekMoon
EverMe-for-SeekMoon: EverMe personal memory for SeekMoon — an MCP server, plus the CLI that installs it and imports existing sessions.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/chaijie2018--everme-for-seekmoon)HTML
<a href="/listings/chaijie2018--everme-for-seekmoon"><img src="/api/listings/chaijie2018--everme-for-seekmoon/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
# 1. build and install, keeping the binary outside the build tree moon run --release cmd/everme-seekmoon -- install --copy-to ~/.local/bin # 2. (optional) bring earlier conversations in ~/.local/bin/everme-seekmoon import sessions # 3. check ~/.local/bin/everme-seekmoon doctor ~/.local/bin/everme-seekmoon mcp test
`install` registers this machine's agent if the credential has none, writes the skill bundle to `~/.openseek/skills/everme-seekmoon/`, and prints the label it registered under. `--mode mcp-json` merges `~/.openseek/mcp.json` instead (or as well, with `both`), keeping a `<path>.bak` of the previous file. `--agents-md` adds a marked block to the workspace's `AGENTS.md`.
Reopen the workspace in SeekMoon afterwards and ask "what do you remember about me?".
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 · 77 lines
- # EverMe-for-SeekMoon
- `everme-seekmoon` — a MoonBit CLI that connects [SeekMoon](https://github.com/moonbitlang/openseek) to
- [EverMe](https://github.com/EverMind-AI/EverMe) memory: one pool shared across the
- user's devices and agents.
- It is two things in one binary:
- - **an MCP server** (`everme-seekmoon mcp serve`) speaking the EverMe memory contract over
- stdio — tools `mem_context`, `mem_search`, `mem_save_fact`, `mem_save_turn` and
- resources `mem://profile`, `mem://search?q=…` — which SeekMoon launches;
- - **a CLI** that logs in, registers this machine's agent, installs the skill bundle
- SeekMoon reads, and imports existing conversation history.
- It is not a reimplementation of upstream `evercli`: only the parts SeekMoon needs,
- written in MoonBit so the server has no Node dependency. The two can coexist — they
- share an account and its memory, and `everme-seekmoon auth adopt-evercli` reuses an existing
- evercli login.
- ## Install
- ```bash
- # 1. build and install, keeping the binary outside the build tree
- moon run --release cmd/everme-seekmoon -- install --copy-to ~/.local/bin
- # 2. (optional) bring earlier conversations in
- ~/.local/bin/everme-seekmoon import sessions
- # 3. check
- ~/.local/bin/everme-seekmoon doctor
- ~/.local/bin/everme-seekmoon mcp test
- ```
- `install` registers this machine's agent if the credential has none, writes the
- skill bundle to `~/.openseek/skills/everme-seekmoon/`, and prints the label it
- registered under. `--mode mcp-json` merges `~/.openseek/mcp.json` instead (or as
- well, with `both`), keeping a `<path>.bak` of the previous file. `--agents-md` adds
- a marked block to the workspace's `AGENTS.md`.
- Reopen the workspace in SeekMoon afterwards and ask "what do you remember about me?".
- ## Commands
- | Command | What it does |
- |---|---|
- | `auth login` / `status` / `logout` | Device-flow login; `--no-wait` and `--device-code` split it across processes |
- | `auth adopt-evercli` | Reuse an evercli login on this machine (account key only, never its agent token) |
- | `auth disconnect-agent --agent-id ID` | Retire an agent; drops the stored token when it is ours |
- | `install` / `uninstall` | Depth: skill bundle, shared config, `AGENTS.md`; `--dry-run` first |
- | `doctor [--probe-platform]` | Credential, account, agent identity, and (with the flag) the platform label |
- | `mcp serve` / `mcp test` | The stdio server / a self-check with one real `mem_context` |
- | `import sessions` | Incremental import of `~/.openseek/sessions/*/*.jsonl` |
- `--format json` switches stdout to `{"ok":…}` / `{"ok":false,"error":{…}}` envelopes
- with the same `error.type` taxonomy and exit codes as upstream.
- ## What it writes
- | Path | Contents |
- |---|---|
- | `~/.local/share/everme-seekmoon/credentials.json` | `0600`: the `emk_` account key and this CLI's own `evt_` agent token |
- | `~/.config/everme-seekmoon/account.json` | Cached account snapshot (no secrets) |
- | `~/.local/share/everme-seekmoon/import-state.json` | Per-session import cursor |
- | `~/.openseek/skills/everme-seekmoon/` | `SKILL.md` + `mcp.json` for SeekMoon (from `install`) |
- Tokens never reach `mcp.json`, logs, or error messages: the server reads its own
- credential store, and every outward string is redacted (`emk_…` / `evt_…` keep
- eight characters).
- ## Notes
- - The managed backend validates `platform` against its own list; `seekmoon` is not in
- it, so this CLI registers as `evercli` (override with `--platform`).
- - Memory writes are at-least-once: an import interrupted mid-batch can repeat that
- batch. The per-batch cursor keeps everything else from being re-sent.
- Licensed under [Apache-2.0](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.