Plugin directory / Knowledge / dsh-noc-memory
dsh-noc-memory
Verified · install-tested on dsh RealAlexandreAI
What it does
dsh memory: Nocturne Memory client for DeepSeek Harness
Works — verified, early-stage project
dsh memory: Nocturne Memory client for DeepSeek Harness It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-noc-memory
Connects DeepSeek Harness to Noc Memory: session-start boot + daily briefing, plus memory read / search / create / update / delete, backed by your own Noc Memory MCP server on Cloudflare.
Port of pi-noc-memory — same protocol, same tool names.
Tools
| tool | what it does |
|---|---|
noc_boot |
load at session start: core + recent + triggers (system://boot, system://recent/5, system://triggers) + briefing |
noc_read |
read a memory by URI (system://…, noc://agent, …) |
noc_search |
search memories (semantic + keyword / trigger recall via search_memory) |
noc_create |
create a memory node ([Baseline]/[Deviation]/[Result]/[Reusable judgment]) |
noc_update |
full replace, patch (old_string/new_string), or append; optional relation |
noc_delete |
delete a memory by URI (delete_memory) |
Quick start
dsh plugin --profile web add dsh-noc-memory
Requires your own Noc Memory server — deploy it to Cloudflare in minutes: cf-noc-mem.
- id: noc-memory
name: dsh-noc-memory
config:
mcp_url: https://mem.example.com/mcp
mcp_auth: "" # prefer mcp_headers for Access service token
For a server behind Cloudflare Access (e.g. noc-mem.slahser.com), use the service token headers instead of mcp_auth:
- id: noc-memory
name: dsh-noc-memory
config:
mcp_url: https://noc-mem.slahser.com/mcp
mcp_headers:
CF-Access-Client-Id: <your client id>
CF-Access-Client-Secret: <your client secret>
| key | required | meaning |
|---|---|---|
mcp_url |
yes | your Noc Memory MCP endpoint (Streamable HTTP) |
mcp_auth |
no | legacy; prefer mcp_headers for Cloudflare Access service token |
mcp_headers |
no | extra headers merged into every MCP request (e.g. Cloudflare Access service token) |
Upgrading from dsh-nocturne-memory (≤0.1.x): renamed to
dsh-noc-memory, tools renamednocturne_*→noc_*. Remove the old plugin and re-add the new package; update any prompt text referencingnocturne_*tools.
Why noc_* (not nocturne_*)?
Some agents probe read_mcp_resource before reaching for a memory tool, wasting a round trip (upstream issue #32). Explicit noc_boot / noc_read naming in the tool list and boot-protocol prompt steers models straight to the right tool — no resource shim required.
License
MIT
Related
- cf-noc-mem — the Cloudflare MCP memory server this plugin talks to
- pi-noc-memory — same memory tools for Pi
- nocturne_memory — upstream project
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalogThen say "install dsh-noc-memory for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:RealAlexandreAI/dsh-noc-memoryHeadless (CLI) profile:
dsh plugin --profile headless add github:RealAlexandreAI/dsh-noc-memoryTest report
Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.
Share this badge
Drop this badge into your README — it links back here and updates automatically when our test status changes:
[](https://dshbase.com/plugins/dsh-noc-memory/)<a href="https://dshbase.com/plugins/dsh-noc-memory/"><img src="https://dshbase.com/badges/dsh-noc-memory.svg" alt="dshbase install-tested"></a>