Memory (Go) MCP Server

A Model Context Protocol server that provides knowledge graph management capabilities.

Remote serverstreamable-httpTypeScript

What is the Memory (Go) MCP Server?

A Model Context Protocol server that provides knowledge graph management capabilities.

What it actually does

Options: -v v0.2.3 for a specific version, -d /usr/local/bin for a custom directory.

  • High-Performance Storage — SQLite backend with WAL mode, read/write connection separation for concurrent access
  • Knowledge Graph Management — Persistent graph of entities, relationships, and observations
  • Advanced Search — FTS5 full-text search with BM25 ranking, synonym expansion, and time-decay scoring
  • Graph Traversal — Search results include 1-hop related entities for richer context
  • Entity Management — Merge duplicate entities, update types, modify observations, detect conflicts
  • Observation Metadata — Track source, confidence, and tags for each observation

Configuration

  • Go 1.24+ * github.com/mark3labs/mcp-go v0.19.0+ * modernc.org/sqlite (pure Go SQLite, no CGO)

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Memory (Go) MCP Server

{
  "mcpServers": {
    "memory": {
      "command": "mms",
      "env": {
        "MEMORY_FILE_PATH": "/path/to/memory.json"
      }
    }
  }
}

Maintainer configuration example. Replace example paths and credential placeholders before connecting.

Configuration

  • Go 1.24+ * github.com/mark3labs/mcp-go v0.19.0+ * modernc.org/sqlite (pure Go SQLite, no CGO)
VariableDescriptionRequired
MEMORY_FILE_PATHFilesystem location the server is allowed to use.Optional
OAUTH_STORE_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • “Use Memory (Go) to Query.”
  • “Use Memory (Go) to Cursor.”
  • “Use Memory (Go) to Migration.”

Frequently asked questions

SQLite (recommended) and JSONL (legacy). SQLite offers FTS5, ACID, WAL, and concurrent reads; JSONL is human-readable and starts faster.