What is the key difference between Memkeeper and Memora?

Memkeeper belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Memora belongs to the Knowledge & Memory category with local stdio execution.

How do I install Memkeeper or Memora in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Memkeeper and Memora free or paid?

Memkeeper operates under a Free / Open Source model (No auth required). Memora operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Memkeeper lists 6 tools with 1 views and 2 GitHub stars. Memora lists 6 tools with 2 views and 719 GitHub stars.

Can I use both Memkeeper and Memora together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Memkeeper vs Memora

In-depth architectural comparison of the Memkeeper and Memora MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Memkeeper

Knowledge & Memory · Remote HTTP/SSE

Quality: 51/100 (Good) | Auth: No auth required

Memora

Knowledge & Memory · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Verdict Summary: Choose Memkeeper if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Memora if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Memkeeper when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Single-file SQLite storage with atomic writes, Hybrid BM25/full-text search with optional ONNX embeddings, Cross-encoder reranker for improved retrieval precision.

Explore Memkeeper Details

Choose Memora when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEMORA_DB_PATH, MEMORA_STORAGE_URI, CLOUDFLARE_API_TOKEN, AWS_PROFILE, AWS_ENDPOINT_URL, MEMORA_CLOUD_ENCRYPT, MEMORA_ALLOW_ANY_TAG, MEMORA_GRAPH_PORT.

Feature & Specification Comparison

Specification	Memkeeper teflon07 Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Local-first memory for AI agents: a single self-contained Rust binary over one SQLite file. Hybrid BM25/FTS + on-device ONNX embeddings + cross-encoder rerank; abstains instead of returning a confident wrong memory. No server, no API key, zero marginal cost. memkeeper mcp	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope

Tools & Capabilities Breakdown

Memkeeper Tools (6)

Single-file SQLite storage with atomic writes

Hybrid BM25/full-text search with optional ONNX embeddings

Cross-encoder reranker for improved retrieval precision

Local-only operation with no cloud or telemetry

MCP JSON-RPC 2.0 interface over stdio for agent integration

Durable schema-versioned storage with retention model

Memora Tools (6)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Memkeeper Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "teflon07-memkeeper": {
      "url": "https://api.openai.com/v1/embeddings"
    }
  }
}

Memora Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-mcp-tools-memora": {
      "command": "npx",
      "args": [
        "-y",
        "wrangler"
      ],
      "env": {
        "MEMORA_DB_PATH": "YOUR_MEMORA_DB_PATH_HERE",
        "MEMORA_STORAGE_URI": "YOUR_MEMORA_STORAGE_URI_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
        "AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
        "AWS_ENDPOINT_URL": "YOUR_AWS_ENDPOINT_URL_HERE",
        "MEMORA_CLOUD_ENCRYPT": "YOUR_MEMORA_CLOUD_ENCRYPT_HERE",
        "MEMORA_ALLOW_ANY_TAG": "YOUR_MEMORA_ALLOW_ANY_TAG_HERE",
        "MEMORA_GRAPH_PORT": "YOUR_MEMORA_GRAPH_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

Memkeeper is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Memora belongs to Knowledge & Memory using local stdio subprocess. Select Memkeeper when you need capabilities focused on knowledge & memory and Memora when you require tools for knowledge & memory.

More alternatives to Memkeeper More alternatives to Memora Knowledge & Memory category hub Canonical compare URL