mcp-automem: Instructions file for Claude Code

AGENTS.md

This file provides guidance to coding agents (Claude Code, Cursor, Codex, etc.) when working with code in this repository. It is the single source of truth; CLAUDE.md imports it via @AGENTS.md.

Migration note: if you previously had a local, gitignored AGENTS.md, delete it before pulling (or run git clean -f AGENTS.md) to avoid checkout/merge errors.

Project Overview

MCP AutoMem is an MCP (Model Context Protocol) server that bridges AI assistants like Claude with the AutoMem memory service. It enables AI to store, recall, and associate memories using FalkorDB (graph database) and Qdrant (vector search).

Core Purpose:

• Translate MCP tool calls into AutoMem API requests
• Provide memory management for AI assistants (storage, hybrid search, relationships)
• Support Claude Code integration with session-recall and opt-in storage-nudge hooks

Build & Development

# Build TypeScript to dist/
npm run build

# Development with hot-reload
npm run dev

# Test server help output
npm test

# Publish preparation
npm run prepublishOnly  # Runs build automatically

# Formatting (CI runs format:check before lint)
npm run format
npm run format:check

Prettier owns src/, tests/, scripts/, and repo config files. .prettierignore excludes templates/, plugins/, and skills/ because those are regenerated by the memory-policy sync on every build — formatting them would fight the generator. Markdown is excluded too: tests/docs/integration-coverage.test.ts asserts against README/INSTALLATION prose and table sections, so reflowing them risks silent coverage breakage.

Four JSON files are checked with Prettier's json-stringify parser instead of its default json parser, through an overrides block in .prettierrc: manifest.json, server.json, .claude-plugin/marketplace.json and .release-please-manifest.json. Release Please rewrites all four on a release PR, and each of its JSON updaters ends in jsonStringify — JSON.stringify(parsed, replacer, detectIndent(content).indent) — which puts every array element on its own line. The default parser collapses any array that fits printWidth, so the two tools disagree permanently and format:check, which the test job runs before Build, fails the release PR. That cost a hand-fix commit on the 0.16.0 release. json-stringify prints what JSON.stringify prints, which is why package.json was never affected — Prettier infers that parser for it by default. Keeping these four on it means Prettier still validates them and the release PR's diff stays at the version line. Add any new json-type extra-files entry to that overrides block as well.