What is the key difference between Agent Recall and ContextLattice?

Agent Recall belongs to the Knowledge & Memory category with local stdio execution, while ContextLattice belongs to the Knowledge & Memory category with local stdio execution.

How do I install Agent Recall or ContextLattice 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 Agent Recall and ContextLattice free or paid?

Agent Recall operates under a Free / Open Source model (No auth required). ContextLattice operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Agent Recall lists 6 tools with 2 views and 371 GitHub stars. ContextLattice lists 6 tools with 3 views and 153 GitHub stars.

Can I use both Agent Recall and ContextLattice 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

Agent Recall vs ContextLattice

In-depth architectural comparison of the Agent Recall and ContextLattice 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

Agent Recall

Knowledge & Memory · Local stdio

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

ContextLattice

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Agent Recall if you need specialized Knowledge & Memory tools running via a local process. Choose ContextLattice 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 Agent Recall 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: Structured corrections ledger, Cross-session and cross-project persistence, Heeded versus recurred outcome tracking.

Explore Agent Recall Details

Choose ContextLattice 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).
Primary tools included: Durable mission and project context, Provenance-aware staged retrieval, Signed and bounded context transfer.

Explore ContextLattice Details

Feature & Specification Comparison

Specification	Agent Recall Knowledge & Memory	ContextLattice sheawinkler Knowledge & Memory
Summary	Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.	Private-by-default memory and context layer for agents with Go/Rust runtime, staged retrieval across fused data backends, and long-horizon context continuity.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Agent Recall Tools (6)

Structured corrections ledger

Cross-session and cross-project persistence

Heeded versus recurred outcome tracking

Five-layer memory system

Keyword and RRF retrieval

Local storage with zero cloud by default

ContextLattice Tools (6)

Durable mission and project context

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

Agent Recall Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agent-recall": {
      "command": "npx",
      "args": [
        "-y",
        "agent-recall-mcp"
      ]
    }
  }
}

ContextLattice Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sheawinkler-contextlattice": {
      "command": "npx",
      "args": [
        "-y",
        "sheawinkler-contextlattice"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Agent Recall More alternatives to ContextLattice Knowledge & Memory category hub