What is the key difference between Krimto and Engram?

Krimto belongs to the Knowledge & Memory category with local stdio execution, while Engram belongs to the Knowledge & Memory category with local stdio execution.

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

Krimto operates under a Free / Open Source model (No auth required). Engram operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Krimto lists 6 tools with 1 views and 6 GitHub stars. Engram lists 6 tools with 1 views and 9 GitHub stars.

Can I use both Krimto and Engram 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.

How do I install Krimto or Engram in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Krimto and Engram free to use, or do they require API keys?

Krimto is listed under a Free / Open Source model with No auth required . Engram operates under a Free / Open Source model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Krimto and Engram at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both krimto-labs-krimto and rwnalds-engram as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Krimto has a Quality Score of 47 /100 ( Fair ) with 1 views, 0 installs, and 6 GitHub stars. Engram holds a Quality Score of 45 /100 ( Fair ) with 1 views, 0 installs, and 9 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Krimto vs Engram

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

Krimto

Knowledge & Memory · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

Engram

Knowledge & Memory · Local stdio

Quality: 45/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Krimto if you need specialized Knowledge & Memory tools running via a local process. Choose Engram 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 Krimto when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Memory stored as plain markdown files in git, User→team→org scoped access control, Hybrid SQLite + vector index for fast retrieval.

Explore Krimto Details

Choose Engram when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ENGRAM_GIT_REPO, ENGRAM_PORT, ENGRAM_JWT_SECRET, ENGRAM_WRITE_TOKEN, ENGRAM_READ_TOKEN.
Primary tools included: Git-backed markdown storage with no database dependency, Authority-aware search excluding superseded or expired notes, Per-agent read and write tokens for access control.

Feature & Specification Comparison

Specification	Krimto krimto-labs Knowledge & Memory	Engram rwnalds Knowledge & Memory
Summary	Open-source team memory layer for AI coding agents. Markdown files in git as storage, a user→team→org hierarchy as the access primitive, and one cross-vendor MCP server (Claude Code, Cursor, Codex, Gemini CLI). Hybrid SQLite + sqlite-vec retrieval. Apache-2.0.	Second brain your agents read and write, over a git-backed markdown vault. Authority-aware search ranks superseded and archived notes below live ones (from frontmatter, no vector DB), so agents quote the current doc, not the dead one. Per-agent read-only or write tokens, a git audit trail of every change with diffs, a knowledge-graph dashboard, and Obsidian compatibility.
Category & Scope

Tools & Capabilities Breakdown

Krimto Tools (6)

Memory stored as plain markdown files in git

User→team→org scoped access control

Hybrid SQLite + vector index for fast retrieval

Cross-vendor MCP server supporting Claude Code, Cursor, Codex, Gemini CLI

Self-hostable with HTTP server and browser UI

No vendor database or account required for solo use

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

Krimto Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "krimto-labs-krimto": {
      "command": "npx",
      "args": [
        "-y",
        "krimto-labs-krimto"
      ]
    }
  }
}

Engram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rwnalds-engram": {
      "command": "npx",
      "args": [
        "-y",
        "rwnalds-engram"
      ],
      "env": {
        "ENGRAM_GIT_REPO": "YOUR_ENGRAM_GIT_REPO_HERE",
        "ENGRAM_PORT": "YOUR_ENGRAM_PORT_HERE",
        "ENGRAM_JWT_SECRET": "YOUR_ENGRAM_JWT_SECRET_HERE",
        "ENGRAM_WRITE_TOKEN": "YOUR_ENGRAM_WRITE_TOKEN_HERE",
        "ENGRAM_READ_TOKEN": "YOUR_ENGRAM_READ_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

Krimto is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram belongs to Knowledge & Memory using local stdio subprocess. Select Krimto when you need capabilities focused on knowledge & memory and Engram when you require tools for knowledge & memory.

More alternatives to Krimto More alternatives to Engram Knowledge & Memory category hub