MCP Catalogs
Homemie screenshot

mie

by kraklabs·42·Score 46

MIE is a persistent memory graph MCP server that enables AI agents to share and recall knowledge across sessions.

knowledge-graphdeveloper-toolsai-llm
4
Forks
1
Open issues
2 mo ago
Last commit
2d ago
Indexed

Overview

MIE (Memory Intelligence Engine) creates a shared knowledge graph that AI agents like Claude, ChatGPT, and Cursor can access. It stores structured information as facts, decisions, entities, and events with relationships between them, rather than simple chat logs. The architecture uses an embedded CozoDB database with optional semantic search via Ollama embeddings. The MCP server exposes 12 tools for storing, querying, updating, and managing the knowledge graph, with zero server-side inference costs since it relies on the client agent to evaluate what's important.

Try asking AI

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

you:Cross-agent knowledge sharing between different AI platforms
you:Persistent memory for AI agents working on long-term projects
you:Structured knowledge capture for technical decisions and context
you:What makes MIE different from platform-specific memory features?
you:Can I use MIE without embeddings/Ollama?

When to choose this

Choose MIE when you need persistent memory across multiple AI agents and want structured knowledge storage with relationship tracking.

When NOT to choose this

Don't choose MIE if you need a simple chat history replacement or if you require a cloud-based solution with multi-device synchronization (not yet available).

Tools this server exposes

12 tools extracted from the README
  • mie_analyze

    Surfaces related context before storing — the agent decides what's worth remembering

  • mie_store

    Writes facts, decisions, entities, events, and relationships to the graph

  • mie_bulk_store

    Batch store up to 50 nodes with cross-references — ideal for importing knowledge from files or git history

  • mie_get

    Retrieve a single memory node by ID with full details

  • mie_query

    Semantic search, exact lookup, or graph traversal across all node types

  • mie_list

    List and filter nodes with pagination

  • mie_update

    Invalidate outdated facts, update statuses — with full history preserved

  • mie_delete

    Remove nodes with cascade (embedding + edges) or remove individual relationships

  • mie_conflicts

    Detect contradictions in stored knowledge

  • mie_export

    Export the full graph as JSON or Datalog

  • mie_repair

    Rebuild HNSW indexes and clean orphaned embeddings

  • mie_status

    Graph health, node counts, usage metrics

Comparable tools

memgptsemantic-memorylangchain-memory

Installation

Install MIE using Homebrew:

brew tap kraklabs/mie
brew install mie

Initialize with:

mie init                    # Quick setup with defaults
mie init --interview        # Interactive setup

Configure as MCP server in Claude Desktop (.mcp.json):

{
  "mcpServers": {
    "mie": {
      "command": "mie",
      "args": ["--mcp"]
    }
  }
}

The MCP server will start automatically when needed.

FAQ

What makes MIE different from platform-specific memory features?
MIE works across all AI agents (Claude, ChatGPT, Cursor, etc.), stores structured data with relationships rather than flat text, and is portable/exportable. Platform memory is limited to a single provider and lacks rich relationships between knowledge items.
Can I use MIE without embeddings/Ollama?
Yes, MIE works without embeddings. You'll still get graph traversal and exact-match search capabilities. Embeddings only add semantic search capabilities.

On Hacker News

Recent discussion from the developer community.

Compare mie with

GitHub →

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