MCP Catalogs
Home

omem

by ourmem·196·Score 49

Persistent memory system for AI agents with MCP Server plugin enabling cross-agent knowledge sharing.

ai-llmknowledge-graphdeveloper-tools
7
Forks
2
Open issues
2 mo ago
Last commit
2d ago
Indexed

Overview

OMEM is a shared memory system that solves AI agent amnesia by providing persistent memory across sessions, devices, and agents. It features a three-tier Space architecture (Personal, Team, Organization) enabling knowledge flow with provenance tracking. The system implements sophisticated memory management including Weibull decay models, 11-stage hybrid retrieval pipelines, and intelligent reconciliation mechanisms. It can be self-hosted or used via the hosted ourmem.ai service.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:AI coding tools (OpenCode, Claude Code, OpenClaw) sharing context across sessions
you:Development teams sharing architectural decisions and code insights
you:Organizations preserving institutional knowledge across agent interactions
you:What makes OMEM different from other AI memory systems?
you:How does OMEM handle memory conflicts?

When to choose this

Choose OMEM when building AI applications that need persistent memory across sessions and tools, or when multiple AI agents need to share knowledge with provenance tracking.

When NOT to choose this

Avoid OMEM if you need an open-source solution without vendor lock-in, or if you're looking for a simple memory system without the complexity of multi-tier sharing and reconciliation.

Comparable tools

mem0semantic-memoryreact-mcp

Installation

MCP Server Installation

  1. Get API key from ourmem.ai
  2. Configure your MCP client:
{
  "mcpServers": {
    "omem": {
      "command": "npx",
      "args": ["@ourmem/mcp-server"],
      "env": {
        "OMEM_API_KEY": "your-api-key-here"
      }
    }
  }
}

FAQ

What makes OMEM different from other AI memory systems?
OMEM's unique three-tier Space architecture enables cross-boundary knowledge sharing with provenance tracking. It combines sophisticated memory management (Weibull decay) with high-quality retrieval (11-stage pipeline) and seamless agent-to-agent sharing capabilities.
How does OMEM handle memory conflicts?
OMEM implements a 7-decision reconciliation system: CREATE, MERGE, SUPERSEDE, SUPPORT, CONTEXTUALIZE, CONTRADICT, or SKIP. This allows memories to evolve intelligently over time, with the system automatically determining how to handle conflicting or overlapping information.

Compare omem with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.