mcp-memory-service is a self-hosted memory backend that lets AI agents store and retrieve shared project context through REST, MCP, OAuth, a command-line interface, and a dashboard. It is intended for agent pipelines and clients such as LangGraph, CrewAI, AutoGen, Claude Desktop, and OpenCode, with support for knowledge graphs and memory consolidation. The catalogue includes skills, agents, commands, instructions, hooks, a setting, an MCP entry, and a plugin for its workflows.
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.
npx skills add doobidoo/mcp-memory-service --skill remember-sessiongit clone --depth 1 https://github.com/doobidoo/mcp-memory-serviceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/doobidoo/mcp-memory-service/remember-session)<a href="https://agentmods.dev/skills/doobidoo/mcp-memory-service/remember-session"><img src="https://agentmods.dev/badge/skills/doobidoo/mcp-memory-service/remember-session/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/doobidoo/mcp-memory-service/remember-session"><img src="https://agentmods.dev/badge/skills/doobidoo/mcp-memory-service/remember-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.01008 |
| Opus 5.5 | $0.00027 | $0.00403 |
| Sonnet 5.5 | $0.00014 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
remember-session 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember Session
Turn the current session into a few separate, tagged memories in MCP Memory Service, then prove they landed. The session-end hook stores a keyword digest automatically; this skill stores what the model understood: decisions, causes, lessons, open items.
1. Find the write path
Use the first one that works:
- A
memory_storetool from the memory MCP server. Its name may carry a prefix (mcp__memory__memory_store,mcp__plugin_mcp-memory-service_memory__memory_store). If the tools sit behind a gateway, discover them through the gateway first. - HTTP:
POST <endpoint>/api/memorieswith headerX-API-Key: <apiKey>and body{"content", "tags", "memory_type"}. Endpoint and key arememoryService.http.endpointandmemoryService.http.apiKeyin~/.claude/hooks/config.json. Search isPOST <endpoint>/api/searchwith{"query", "n_results"}.
If neither works, stop and tell the user. Do not write a local file instead.
2. Project tag
The first tag of every memory is the name the session-start hook filters on. If the hook's "Detection Result" line from this session is in context, use the name it printed. Otherwise derive it the way the hook does, from the session's working directory:
- the
nameinpackage.json,pyproject.tomlorCargo.toml, or the last path segment of the module ingo.mod - else the repository name from
git config --get remote.origin.url - else the directory name
If that project's CLAUDE.md names a different required tag, use that one. Never use the tag of the repository this skill ships in unless the session was in it.
Also pick one session tag, session-YYYY-MM-DD-<topic>, and put it on every memory this run writes.
3. Select
Keep:
- decisions, with the reason and the rejected alternative
- root causes, with the fix and how it was verified
- lessons that apply beyond this task
- open items: owner, next action, absolute date
- facts about people (handle, role, what they own or are waiting for)
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.
- 7d ago First seen · 75 lines · 68 tokens per session scan A 27ac10026477
remember-session is a skill published in the GitHub repository doobidoo/mcp-memory-service (2,021 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 1,008 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
compartmentalize
Sweep this conversation and save everything worth referencing again in future work into Compartment, the encrypted memory vault. Run it before compacting or summarizing so nothing is lost to the summary, or on its own at any point to bank the session.
memwal
Walrus Memory SDK — portable agent memory that works across apps, sessions, and workflows. Use when users say: "add memory to my app" "portable agent memory" "integrate Walrus Memory" "AI agent memory" "memory across agents" "Walrus memory storage" "setup Walrus Memory" "recall memories".
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
lilbee-mcp
Search and manage the user's local lilbee knowledge base over MCP. Use whenever the user has indexed code, docs, PDFs, or web pages into lilbee and you need cited answers, or whenever they ask you to ingest content, swap models, or tune retrieval against their library. Every fact returned cites file and line.…
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
notebrain-assistant
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like…