MCP.so
Sign In
A

Agent Memory

@tverney

Repository

About Agent Memory

No overview available yet

#mcp#mcp-server#model-context-protocol#ai-agents#agent-memory#kiro#claude-desktop#cursor#openclaw#persistent-memory#typescript#bedrock#llm-tools

Basic information

Category

AI & Agents

Transports

stdio

Publisher

tverney

Submitted by

Thiago Verney

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-agent-memory"
      ],
      "env": {
        "MEMORY_DIRECTORY": "~/.agent-memory/memory",
        "SESSION_DIRECTORY": "~/.agent-memory/sessions"
      },
      "disabled": false,
      "timeout": 30000
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Agent Memory?

Agent Memory is an MCP server that exposes an agent-memory-daemon to any MCP-compatible client. The server acts as a thin filesystem bridge so that agents can read, append, and search memory through the Model Context Protocol, while the daemon handles consolidation and extraction.

How to use Agent Memory?

—

Key features of Agent Memory

  • Exposes agent-memory-daemon via the Model Context Protocol
  • Acts as a lightweight filesystem bridge for memory operations
  • Supports reading, appending, and searching agent memory
  • Compatible with Kiro, Claude Desktop, Cursor, and other MCP clients
  • Separates memory storage (server) from consolidation and extraction (daemon)

Use cases of Agent Memory

  • Allow AI agents to persist and retrieve memories across different sessions
  • Enable memory search functionality for any MCP-compatible client
  • Decouple memory management logic from client-specific implementations

FAQ from Agent Memory

Which clients does Agent Memory work with?

Agent Memory works with any MCP-compatible client, including Kiro (CLI & IDE), Claude Desktop, Cursor, and others.

What is the difference between the server and the daemon?

The agent-memory-daemon handles the thinking—consolidation and extraction—while the server is a thin filesystem bridge that enables memory operations through MCP.

What memory operations does Agent Memory support?

The server enables agents to read, append, and search memory through the Model Context Protocol.

What are the runtime dependencies of Agent Memory?

—

Comments

More AI & Agents MCP servers

MCP Manager for Claude Desktop

zueai

simple web ui to manage mcp (model context protocol) servers in the claude app

290

LinkedIn MCP Server

stickerdaniel

Open-source MCP server for LinkedIn. Give Claude and any MCP-compatible AI agent access to profiles, companies, jobs, and messages.

2.7K

1Panel

1Panel-dev

🔥 1Panel is a modern, open-source VPS control panel — and the only one with native AI agent support. Run Ollama models, deploy OpenClaw agents, and manage your entire server stack from one clean web interface.

36.1K

1MCP - One MCP Server for All

1mcp-app

A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.

468

Gemini MCP Server

aliargun

MCP server implementation for Google's Gemini API

259