mcp-memory-service: Instructions file for Claude Code

CLAUDE.md

mcp-memory-service CLAUDE.md is an instructions file for Claude Code from doobidoo/mcp-memory-service. It costs 7,166 tokens per session, scanned B, original, Apache-2.0.

A project instruction file for the MCP Memory Service repository. It records required workflows, hard rules, where development happens, and how the agent should look up and save information.

In plain words
What is it for?
Use it to guide development, find project information, follow Codeberg and CI conventions, and preserve useful learnings in memory.
Why use it?
It gives the coding agent the repository context and rules it needs to avoid incorrect commands, releases, and source-control changes.

Instructions file for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is doobidoo/mcp-memory-service's own configuration. It tells Claude Code how to work on mcp-memory-service itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-memory-service configures →

About the project

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.

doobidoo/mcp-memory-service · 1,929 stars · on GitHub

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/doobidoo/mcp-memory-service/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/doobidoo/mcp-memory-service

Made for: Claude Code.

Wrote 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.

agentmods badge for mcp-memory-service CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/doobidoo/mcp-memory-service/claude-md.svg)](https://agentmods.dev/instructions/doobidoo/mcp-memory-service/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/doobidoo/mcp-memory-service/claude-md"><img src="https://agentmods.dev/badge/instructions/doobidoo/mcp-memory-service/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 7,166 This file is loaded in full into every session.
When invoked 7,166 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.07166 $0.07166
Opus 5 $0.03583 $0.03583
Sonnet 5 $0.01433 $0.01433
Haiku 4.5 $0.00717 $0.00717

Measured today against content hash df54f440dc18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

mcp-memory-service CLAUDE.md scanned grade B with 1 finding 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 today.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

block in `~/.claude/settings.json` before assuming the skill is missing.
CLAUDE.md · 448 lines

How it starts

The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with this MCP Memory Service repository. It is written to be self-sufficient: a model should be able to work correctly here from this file alone, without filling gaps from prior knowledge.

Personal Customizations: You can create CLAUDE.local.md (gitignored) for personal notes, custom workflows, or environment-specific instructions. This file contains shared project conventions.

Information Lookup: Files first, memory second, user last. See .claude/directives/memory-first.md for strategy. Comprehensive project context is stored in the MCP Memory Server with tag claude-code-reference.

Non-Negotiables (hard rules)

Quick reference; each rule is expanded in the sections below. Violations cause real incidents.

  1. Development happens on GitHub. origin is github.com:doobidoo/mcp-memory-service; CI is GitHub Actions (.github/workflows/); issues, PRs, releases and the tag push that starts a release all live there, and gh is the CLI for all of it. GitLab is a push mirror that receives fast-forwards of main and never tags (see "Source Control & Hosting").
  2. Never manually bump versions. Follow the documented release workflow for every version bump and release.
  3. Run bash scripts/pr/pre_pr_check.sh before every PR. It is the mandatory pre-PR gate and must pass.
  4. Use the project venv. Run .venv/bin/python and .venv/bin/pytest (Python 3.12) — the system interpreters are not the project environment.
  5. Store context in the MCP Memory Server first, tagged mcp-memory-service. Claude Code's file-based memory (~/.claude/projects/<project>/memory/) may run alongside it as a local cache — it is a supplement, not a substitute, and it lives outside the repo. Never commit memory files into the working tree.
  6. Access Memory fields by attribute (memory.tags), never via memory.metadata.get('tags'). This has caused 3 production bugs.
  7. Sanitize user-provided values in logs with _sanitize_log_value() (from mcp_memory_service.compat).
  8. MCP server configs go in .mcp.json, not settings.json.
  9. Update site/index.html version strings on every MINOR/MAJOR release (a CI gate enforces this).
  10. Never click "Always allow" on heredoc commands — it corrupts .claude/settings.local.json.
  11. Before any SSH/network task, verify hostname and connection direction (source → target).
  12. Report outcomes faithfully. "Tests pass" means you ran them and saw them pass; if a step was skipped or failed, say so with the output.
  13. Write in the maintainer's or contributor's own voice. Commit messages, PR descriptions, CHANGELOG entries, issue/PR comments, and release notes read as authored by the maintainer or contributor.

Read the full file on GitHub · 448 lines

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. today Changed · +39 lines · +785 tokens per session scan A → B df54f440dc18
  2. 8d ago First seen · 409 lines · 6,381 tokens per session scan A 4b40df7460eb

Subscribe to this mod's changes

mcp-memory-service CLAUDE.md is an instructions file published in the GitHub repository doobidoo/mcp-memory-service (1,929 stars, last pushed today), licensed Apache-2.0. It adds 7,166 tokens to every session, about $0.0358 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens