AI Memory MCP

AI Memory MCP

Gives agents a stable interface for durable memory, combining exact, lexical, semantic, and graph search results.

Category
访问服务器

README

AI Memory MCP

AI Memory MCP gives agents one stable interface for durable memory. The server combines exact, lexical, semantic, and graph search results.

Markdown files are the source of truth. The system derives SQLite indexes and Graphify graphs from Markdown.

Architecture decision

The system is built around Graphify. Graphify remains a replaceable provider behind the stable AI Memory MCP interface.

The MCP facade owns scope, ranking, evidence, health, feedback, and refresh control. Clients do not depend on Graphify commands, files, or response formats.

This boundary permits a future graph-provider change without a client configuration change. Read the complete architecture guide for the design rules.

System architecture

flowchart LR
    subgraph Clients["MCP clients"]
        Codex[Codex]
        Claude[Claude]
        Copilot[Copilot]
        OpenCode[OpenCode]
        VSCode[VS Code]
    end

    subgraph Repository["AI Memory MCP repository"]
        MCP["MCP facade<br/>Eight public tools"]
        Service["MemoryService<br/>Policy and orchestration"]
        Retrieval["RetrievalEngine<br/>Scope, fusion, and reranking"]
        Indexer["Memory indexer<br/>Validation and snapshots"]
        Adapter["GraphifyAdapter<br/>Replaceable provider boundary"]
        Skill["Canonical ai-memory skill"]
    end

    subgraph Authority["Canonical authority"]
        Markdown["Markdown memory<br/>Durable source of truth"]
    end

    subgraph Derived["Derived state"]
        SQLite["Versioned SQLite<br/>FTS5 and semantic vectors"]
        Graph["Graphify graph<br/>Nodes, edges, and paths"]
    end

    Clients --> MCP
    MCP --> Service
    Service --> Retrieval
    Retrieval --> SQLite
    Retrieval --> Adapter
    Adapter --> Graph
    Markdown --> Indexer
    Indexer --> SQLite
    Markdown --> Graph
    Skill -. guides .-> Clients

Main components

Component Responsibility
Markdown memory Stores canonical durable records.
Memory indexer Validates records and publishes versioned SQLite snapshots.
SQLite FTS5 Supplies exact and lexical candidates.
Local semantic index Supplies paraphrase candidates without an external API.
Graphify adapter Supplies relationships, neighbors, and paths.
Retrieval engine Applies scope, RRF fusion, reranking, and context expansion.
MCP facade Supplies the stable public tools and evidence packets.
Canonical skill Gives agents the memory workflow and safety rules.
Client installer Registers the MCP server and repository-linked skill stubs.

Query architecture

memory_recall is the only recall tool. The service selects exact, search, neighbor, or relationship behavior. The retrieval engine combines all provider work internally.

sequenceDiagram
    participant Agent
    participant MCP as MCP facade
    participant Service as MemoryService
    participant Engine as RetrievalEngine
    participant SQLite as SQLite index
    participant Graphify as GraphifyAdapter

    Agent->>MCP: memory_recall query and scope
    MCP->>Service: Validate tool input
    Service->>Service: Select recall intent
    Service->>Engine: Recall request
    Engine->>Engine: Resolve scope and ticket identifiers
    Engine->>SQLite: Get scoped lexical candidates
    SQLite-->>Engine: Ranked lexical hits
    Engine->>SQLite: Get scoped semantic vectors
    SQLite-->>Engine: Ranked semantic hits
    Engine->>Graphify: Rank scoped candidate paths
    Graphify-->>Engine: Relationship signals
    Engine->>Engine: Fuse results with RRF
    Engine->>Engine: Deduplicate and rerank
    Engine->>SQLite: Expand bounded context
    Engine-->>Service: Evidence and relationships
    Service-->>MCP: Structured result
    MCP-->>Agent: Cited memory evidence

The engine applies scope before it ranks each provider result. Exact identifiers receive bounded bonuses during reranking.

Graph traversal contributes one retrieval signal. It does not replace lexical or semantic retrieval.

Refresh architecture

memory_sync updates SQLite after a normal Markdown change. The maintenance script rebuilds the Graphify graph.

flowchart TD
    Change[Canonical Markdown change] --> Sync[memory_sync]
    Sync --> IndexStage[Build staged SQLite snapshot]
    Maintenance[Graphify maintenance script] --> GraphStage[Build staged Graphify data]
    GraphStage --> GraphValidate{Graph validation}
    GraphValidate -->|pass| GraphPublish[Publish Graphify graph]
    GraphValidate -->|fail| GraphKeep[Keep the last satisfactory graph]
    GraphPublish --> Sync
    IndexStage --> IndexValidate{Index validation}
    IndexValidate -->|pass| Pointer[Publish the current-index pointer]
    IndexValidate -->|fail| IndexKeep[Keep the last satisfactory index]
    Pointer --> Health[Run health and retrieval checks]

The maintenance script uses staging, validation, publication, health checks, and rollback. A failed rebuild does not change the Markdown authority.

Reliability and performance

  • The repository pins Graphify 0.9.26 in an isolated environment.
  • Scope filters run before provider ranking.
  • RRF combines independent provider rankings.
  • Bounded reranking limits query work.
  • One query loads context for all returned records.
  • Recall results omit internal provider diagnostics.
  • Incremental indexing skips unchanged Markdown files.
  • Versioned snapshots preserve the last satisfactory index.
  • Full graph refreshes validate staged data before publication.
  • Evidence packets include canonical source paths.

Quick start

Install these items:

  • Git
  • Python 3.11 or later
  • PowerShell 5.1 or later
  • A Markdown memory directory

Open PowerShell in the repository root. Then, run this command:

.\scripts\setup.ps1 -MemoryRoot 'C:\path\to\AI-Memory' -InstallClients

Restart each configured client after the setup procedure is complete.

For more setup information, read the installation guide.

MCP tools

Tool Function
memory_recall Returns cited evidence and applicable relationships.
memory_sync Updates the derived index from canonical Markdown.
memory_status Reports source, index, Graphify, and runtime status.

Repository layout

Path Contents
src/ai_memory_mcp/ MCP server, retrieval engine, indexer, and adapters
scripts/ Setup, client installation, and Graphify operations
skill/ai-memory/ Canonical AI Memory skill
tests/ Automated behavior and portability tests
benchmarks/ Frozen retrieval contract and fixtures
docs/ Architecture, setup, operations, and validation guides

Documentation

The documentation index gives links to all project guides.

Source boundary

This is a public repository. This repository contains all project source files. It contains only neutral examples and synthetic benchmark fixtures. The user memory directory stays outside Git. Generated indexes, logs, and recovery files also stay outside Git. Machine-specific and organization-specific values stay in the ignored .env file.

Read AGENTS.md before you change this repository.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选