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.
Borrowing it
Nothing to install: this file belongs to doobidoo/mcp-memory-service. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/doobidoo/mcp-memory-service/main/.claude/commands/release.mdgit 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/commands/doobidoo/mcp-memory-service/release)<a href="https://agentmods.dev/commands/doobidoo/mcp-memory-service/release"><img src="https://agentmods.dev/badge/commands/doobidoo/mcp-memory-service/release/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/commands/doobidoo/mcp-memory-service/release"><img src="https://agentmods.dev/badge/commands/doobidoo/mcp-memory-service/release.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.00000 | $0.00951 |
| Opus 5.5 | $0.00000 | $0.00380 |
| Sonnet 5.5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
release 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 22d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release — Full Release Cycle
Execute the complete release workflow for mcp-memory-service by delegating to the github-release-manager agent.
What This Command Does
Spawn the github-release-manager agent to handle the entire release lifecycle:
- Pre-Release: List open PRs, merge approved ones, verify CI green on main
- Version Bump: Determine bump type (MAJOR/MINOR/PATCH) from PR labels, update
_version.py,pyproject.toml,uv.lock - Documentation: Run
python3 scripts/release/collect_changelog.pyfirst — it merges thechangelog.d/fragments every PR left behind into[Unreleased]and deletes them. Then retitle[Unreleased]in CHANGELOG.md to the new version and leave an empty## [Unreleased]heading above it. The README carries no version string and needs no edit. Do not add a version line to CLAUDE.md — it was removed on 2026-09-05 in favour of a pointer to CHANGELOG.md, because it was the file that actually got forgotten. - Landing Page: Update
site/index.htmlfor MINOR/MAJOR releases only — version badge, What's New cards, test count. Deploys automatically to mcpmemory.services on merge (.github/workflows/deploy-site.yml) - Tag: Annotated tag on the merge commit, pushed with git and an explicit refspec:
The push is what triggersgit tag -a vX.Y.Z -m "<summary>" <merge-sha> git push origin refs/tags/vX.Y.Z # never --tags, never the forge APIrelease.yml. A tag created through the release API or the web form is not a push event, so nothing fires — that is how v11.8.1 was tagged and never published. - Verify the artifacts, not the run:
bash scripts/release/verify_artifacts.sh X.Y.Zmust exit 0 before the release object exists. It checks both PyPI distributions by version and all four Docker tags pluslatestby digest. Never accept an HTTP 200, or a green run, as proof: v11.11.0 had two of three jobs green whilelateststill served the previous build. - Release Creation: Publish the release object from the tag, with notes and contributor recognition — last, after step 6 is green. A release with notes looks finished, which is what hid v11.8.1 for a day. Re-fetch the published release afterwards and quote the live notes back as evidence.
- Post-Release: Fast-forward the GitLab mirror (prove the ancestor check first, never tags), clean up branches, close resolved issues.
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.
- 22d ago Changed 353bd28e8b29
- 29d ago Changed · +18 lines 91940615642b
- 1mo ago Changed ecc6ca4e3128
- 1mo ago First seen · 27 lines · 0 tokens per session scan A a781b66311ae
release is a command published in the GitHub repository doobidoo/mcp-memory-service (2,021 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 951 tokens. 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.
Other commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.