Skip to main content
Glama
Agent Memory MCP Server

Agent Memory MCP Server

by AiAgentKarl

Agent Memory MCP Server đź§ 

Persistent memory for AI agents — store, retrieve and search knowledge across sessions. No more forgetting between conversations.

The Problem

AI agents lose all context when a session ends. This MCP server gives agents a persistent knowledge store that survives across sessions, tools, and even different agent frameworks.

Related MCP server: haksnbot-memory

Features

  • Store & Retrieve — Key-value storage with full persistence

  • Namespaces — Separate memories by project, user, or context

  • Tags — Categorize memories for easy filtering

  • Full-Text Search — Search across all stored knowledge

  • Access Tracking — See which memories are accessed most

  • Statistics — Dashboard showing memory usage

Installation

pip install agent-memory-mcp-server

Usage with Claude Code

{
  "mcpServers": {
    "memory": {
      "command": "uvx",
      "args": ["agent-memory-mcp-server"]
    }
  }
}

Tools

Tool

Description

memory_store

Store a key-value pair persistently

memory_retrieve

Retrieve stored knowledge by key

memory_search

Full-text search across all memories

memory_list

List all memories in a namespace

memory_delete

Remove a memory

memory_namespaces

List all namespaces

memory_stats

Usage statistics

Examples

"Remember that the user prefers dark mode"
"What do you know about Project Alpha?"
"Store this API response for later"
"What were the key decisions from last session?"

How It Works

Uses SQLite for zero-configuration persistent storage. Data is stored locally — no cloud, no API keys, no costs. The database file (memory.db) is created automatically in the server directory.


More MCP Servers by AiAgentKarl

Category

Servers

đź”— Blockchain

Solana

🌍 Data

Weather · Germany · Agriculture · Space · Aviation · EU Companies

đź”’ Security

Cybersecurity · Policy Gateway · Audit Trail

🤖 Agent Infra

Memory · Directory · Hub · Reputation

🔬 Research

Academic · LLM Benchmark · Legal

→ Full catalog (40+ servers)

License

MIT

Available Tools

7 tools
memory_deleteB

Ein Memory löschen.

Args: key: Schlüssel des zu löschenden Eintrags namespace: Namespace (Standard: "default")

Inputs: key (required), namespace.

memory_listA

Alle Memories auflisten.

Args: namespace: Optional — nur diesen Namespace zeigen limit: Maximale Anzahl (Standard: 20)

Inputs: namespace, limit.

memory_namespacesA

Alle Namespaces mit Anzahl Memories auflisten.

Zeigt eine Ăśbersicht aller verwendeten Namespaces.

Inputs: no named parameters.

memory_retrieveC

Gespeichertes Wissen abrufen.

Args: key: SchlĂĽssel des gesuchten Eintrags namespace: Namespace (Standard: "default")

Inputs: key (required), namespace.

memory_statsA

Speicher-Statistiken abrufen.

Zeigt: Gesamtzahl Memories, Namespaces, meistgenutzte und zuletzt aktualisierte Einträge.

Inputs: no named parameters.

memory_storeA

Wissen persistent speichern.

Speichert einen Key-Value-Eintrag der über Sessions hinweg erhalten bleibt. Ideal für Fakten, Präferenzen, Kontext.

Args: key: Eindeutiger SchlĂĽssel (z.B. "user_preference_language") value: Der zu speichernde Inhalt (Text, JSON, etc.) namespace: Namespace zur Trennung (z.B. "project_x", "user_123") tags: Optionale Tags zum Kategorisieren (z.B. ["preference", "important"])

Inputs: key (required), value (required), namespace, tags.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: store, retrieve, list, search, delete, list namespaces, and stats. No overlap or ambiguity.

    Naming Consistency4/5

    Tools follow a consistent 'memory_' prefix with verbs except for 'memory_namespaces' and 'memory_stats', which use nouns. Minor deviation from the verb_noun pattern.

    Tool Count5/5

    Seven tools are appropriate for a memory management server, covering essential operations without being too few or too many.

    Completeness4/5

    Covers all basic memory operations (create, read, list, search, delete, stats, namespace listing), but lacks an explicit update operation, though store can overwrite existing keys.

    Related MCP Connectors

    Related MCP Servers