What is the key difference between Engram Rs and Kremis?

Engram Rs belongs to the Knowledge & Memory category with local stdio execution, while Kremis belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Engram Rs or Kremis 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 Engram Rs and Kremis free or paid?

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

Which MCP server has more tools and community activity?

Engram Rs lists 6 tools with 2 views and 27 GitHub stars. Kremis lists 6 tools with 1 views and 14 GitHub stars.

Can I use both Engram Rs and Kremis 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

Engram Rs vs Kremis

In-depth architectural comparison of the Engram Rs and Kremis 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

Engram Rs

Knowledge & Memory · Local stdio

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

Kremis

Knowledge & Memory · Remote HTTP/SSE

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

Verdict Summary: Choose Engram Rs if you need specialized Knowledge & Memory tools running via a local process. Choose Kremis if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Engram Rs 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: ENGRAM_EMBEDDING_PROVIDER, ENGRAM_EMBEDDING_API_KEY.
Primary tools included: Three-layer memory lifecycle: buffer, working, core, LLM-based quality gate for memory promotion, Exponential decay with differentiated rates by memory kind.

Explore Engram Rs Details

Choose Kremis 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: Deterministic graph engine in Rust, CLI, HTTP API, and MCP bridge, BLAKE3 hashing of full graph state.

Feature & Specification Comparison

Specification	Engram Rs kael-bit Knowledge & Memory	Kremis TyKolt Knowledge & Memory
Summary	Hierarchical memory engine for AI agents with automatic decay, promotion, semantic dedup, and self-organizing topic tree. Single Rust binary, zero external dependencies.	Deterministic knowledge graph MCP server. Single binary, zero LLM/embedding calls in the bridge, BLAKE3 state hashing, canonical KREX export for byte-identical audit. Local-first via redb (ACID). Alpha.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Engram Rs Tools (6)

Three-layer memory lifecycle: buffer, working, core

LLM-based quality gate for memory promotion

Exponential decay with differentiated rates by memory kind

Semantic deduplication and merging of memories

Self-organizing topic tree with LLM-named clusters

Single Rust binary with SQLite storage and no external dependencies

Kremis 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).

Engram Rs Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kael-bit-engram-rs": {
      "command": "npx",
      "args": [
        "-y",
        "engram-rs-mcp"
      ],
      "env": {
        "ENGRAM_EMBEDDING_PROVIDER": "YOUR_ENGRAM_EMBEDDING_PROVIDER_HERE",
        "ENGRAM_EMBEDDING_API_KEY": "YOUR_ENGRAM_EMBEDDING_API_KEY_HERE"
      }
    }
  }
}

Kremis Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tykolt-kremis": {
      "url": "https://kremis.mintlify.app/mcp/overview"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Engram Rs More alternatives to Kremis Knowledge & Memory category hub