What is the key difference between Engram and Tribal?

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

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

Engram operates under a Free / Open Source model (API Key required). Tribal operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

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

Can I use both Engram and Tribal 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 Engram or Tribal 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 Engram and Tribal free to use, or do they require API keys?

Engram is listed under a Free / Open Source model with API Key required . Tribal operates under a BYOK (Pay Provider Direct) 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 Engram and Tribal at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both rwnalds-engram and tribal-memory-tribal 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, Engram has a Quality Score of 45 /100 ( Fair ) with 1 views, 0 installs, and 9 GitHub stars. Tribal holds a Quality Score of 52 /100 ( Good ) with 1 views, 0 installs, and 9 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Engram vs Tribal

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

Knowledge & Memory · Local stdio

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

Tribal

Knowledge & Memory · Local stdio

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

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

Explore Engram Details

Choose Tribal 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: OPENAI_API_KEY, ANTHROPIC_API_KEY, OLLAMA_API_KEY, TRIBAL_BEARER_TOKEN.

Feature & Specification Comparison

Specification	Engram rwnalds Knowledge & Memory	Tribal tribal-memory Knowledge & Memory
Summary	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.	Self-hosted semantic memory server, served over MCP, for an engineering team's tribal knowledge: the tacit decisions and hard-won reasoning behind the code, captured once and kept queryable for the team and the agents they work with. Postgres-backed (pgvector).
Category & Scope

Tools & Capabilities Breakdown

Engram Tools (6)

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

Full git audit trail with per-file diffs and attribution

Knowledge graph visualization of markdown links

Obsidian vault compatibility with no import step

Tribal Tools (5)

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 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"
      }
    }
  }
}

Tribal Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tribal-memory-tribal": {
      "command": "npx",
      "args": [
        "-y",
        "tribal-memory-tribal"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY_HERE",
        "TRIBAL_BEARER_TOKEN": "YOUR_TRIBAL_BEARER_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

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