terminalOperation Initialized

ANCHORMIND
MEMORY FOR AGENTS

So your AI agent stops starting every session as a stranger. A long-term memory MCP server where you sign in with GitHub and own and manage your memory fragments.

How It WorksMCP

SIGN INGitHub OAuth

FRAGMENT QUOTA5,000 / account

API KEYSSplit per key

DATA COLLECTEDGitHub ID only

FRAGMENT TYPES7 kinds

LATEST RELEASEv5.6.0

FRAGMENT_TYPES

factdecisionerrorpreferenceprocedurerelationepisode

Quickstart

.mcp.json

{
  "mcpServers": {
    "anchormind": {
      "type": "http",
      "url": "https://memento.anchormind.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCESS_KEY"
      }
    }
  }
}

verify

# 1. store a fragment
remember(
  content="connection test",
  topic="setup", type="fact"
)

# 2. recall — the stored fragment should return
recall(keywords=["setup"])

Download config templates · Full integration guide

Features

7 fragment types

Structure memory as fact, decision, error, preference, procedure, relation, and episode.

Semantic search

pgvector-based recall retrieves semantically similar fragments without exact keywords.

Case tracking

Bundle multi-step work with caseId, phase, and resolutionStatus to retrace the flow.

Anchored memory

Pin core fragments so they are always injected at session start.

Quota & key split

Split the 5,000-fragment quota (10,000 for sponsors) across API keys.

Search telemetry

Inspect search quality and usage metrics within your own scope.

Multiple agents

Share the same memory across MCP clients such as Claude Code and Cursor.

Full tool reference →

How It Works

Agents build and revive memory with three operations.

01 · REMEMBER

Store important facts, errors, decisions, and procedures as fragments during a session.

remember(
  content="port 8080 → 15000",
  topic="deploy", type="fact"
)

02 · RECALL

Recall past fragments in the next session via keyword or natural-language semantic search.

recall(
  keywords=["deploy", "port"]
)

03 · REFLECT

Persist summaries, decisions, and resolved errors as a narrative at session end.

reflect(
  summary=[...],
  narrative_summary="..."
)

Transparency

Being explicit about what is collected — and what is not.

check_circleSign-in is GitHub OAuth only. No passwords, payment data, or repository code is collected.
check_circleThe only data collected is your GitHub login ID, display name, and avatar URL.
check_circleMemory fragments belong to your account and can be exported as JSON or Markdown at any time.
check_circleServer infrastructure status and other users' information are never shown on any screen.
check_circleRevoking an API key immediately blocks that key's agent access.
check_circle5,000 memory fragments per account — 10,000 with GitHub Sponsors.

ANCHORMINDMEMORY FOR AGENTS