memory-server-up

A command for starting the single-tenant lean-memory console in Docker. Docker runs the console in a separate container on your computer or server.

In plain words
What is it for?
Start the console, connect an agent through its MCP address, open its web interface, and stop the service when finished.
Why use it?
It provides the startup steps and required authentication setup for running the console locally instead of working out the Docker and connection commands yourself.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/wuesteon/lean-memory/memory-server-up
Clone the repo
git clone --depth 1 https://github.com/Wuesteon/lean-memory
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 218 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00218
Opus 5 $0.00009 $0.00109
Sonnet 5 $0.00003 $0.00044
Haiku 4.5 $0.00002 $0.00022

Measured 2d ago against content hash 025d2673fdcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memory-server-up scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/commands/memory-server-up.md · 23 lines

What it actually says

Bring up the Docker console using the compose file packaged inside the installed lean-memory-console wheel (the single source of truth — the plugin ships no compose copy).

LM_API_KEY is required in Docker mode; the container refuses to boot without it. Set one if you have not already (e.g. export LM_API_KEY=$(openssl rand -hex 24)).

!docker compose -f "$(lean-memory-console --print-compose-path)" up -d

After it starts, connect an agent over streamable-HTTP MCP:

claude mcp add --transport http lean-memory http://127.0.0.1:8377/mcp \
  --header "Authorization: Bearer $LM_API_KEY"

Open the console UI at http://127.0.0.1:8377/ and authenticate with the same LM_API_KEY. Stop it with /memory:server-down.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 23 lines · 17 tokens per session scan A 025d2673fdcb

Subscribe to this mod's changes

memory-server-up is a command published in the GitHub repository Wuesteon/lean-memory (47 stars, last pushed 25d ago), licensed Apache-2.0. It adds 17 tokens to every session and 218 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.