MCP.so
Sign In

Memory MCP Server (Go)

@okooo5km

About Memory MCP Server (Go)

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

Basic information

Category

Memory & Knowledge

Runtime

go

Transports

stdio

Publisher

okooo5km

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

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 Memory MCP Server (Go)?

Memory MCP Server (Go) is a Go implementation of the Model Context Protocol server that provides knowledge graph management capabilities. It enables LLMs to create, read, update, and delete entities and relations in a persistent knowledge graph, helping AI assistants maintain memory across conversations.

How to use Memory MCP Server (Go)?

Install via Homebrew, quick install script, pre-built binaries, or build from source. Run the mms command with options for transport (stdio, sse, http), memory file path, port, host, and authentication. Configure MCP clients like Claude Desktop or Cursor by specifying the command and environment variables.

Key features of Memory MCP Server (Go)

  • SQLite backend with WAL mode for concurrent access
  • FTS5 full-text search with BM25 ranking and synonym expansion
  • Graph traversal returning 1-hop related entities
  • Entity management: merge, update, and conflict detection
  • Observation metadata tracking source, confidence, and tags
  • Flexible transport with stdio, SSE, and Streamable HTTP

Use cases of Memory MCP Server (Go)

  • Persisting AI assistant memory across multiple conversations
  • Maintaining a knowledge graph of people, concepts, and relationships
  • Searching and retrieving relevant memories by keyword
  • Managing and deduplicating entity data

FAQ from Memory MCP Server (Go)

What storage types are supported?

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

How do I migrate from JSONL to SQLite?

Automatic migration occurs by default when using a JSONL memory file path. Manual migration is available with the --migrate and --migrate-to flags.

What authentication options are available?

Supports Bearer token (--auth-bearer) and OAuth 2.1 (--oauth-user/--oauth-pass and related flags) for SSE and HTTP transports.

What transport protocols are supported?

stdio, SSE, and Streamable HTTP (with optional Bearer or OAuth 2.1 authentication).

Does the server require CGO?

No, it uses pure Go SQLite and works on Linux, macOS, and Windows without CGO.

Comments

More Memory & Knowledge MCP servers