← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMengram MCP ServerLong-term memory for AI agents that actually learnsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS57 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Coding agents and CLI workflows that need persistent memory across sessions and machines (Claude Code, Codex, Cursor)
  • Developers building autonomous agents that need semantic, episodic, and evolving procedural memory
  • Teams using LangChain, CrewAI, or OpenClaw who want a ready memory backend
  • Apps that need multi-user data isolation under a single API key
  • Teams wanting an account-free, folder-based memory that uses their own model provider (Anthropic, OpenAI, or Ollama)
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Single-turn chats or scenarios with no need for cross-session state
  • Environments requiring a fully local setup with no SDK or CLI installed (local mode still needs pip install mengram-ai and your own model key)
  • High-concurrency writes demanding whole-folder crash-atomic transactions (the folder is not a single crash-atomic transaction and external editors do not participate in the lock)
  • Self-hosters expecting good extraction from models under 8B parameters or with less than an 8K context window
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • A Mengram API key sent as an Authorization: Bearer header for cloud memory reads and writes
  • In cloud mode, conversations are sent to mengram.io for extraction, embedding, and retrieval
  • Claude Code hooks can read session history and working state and re-inject context before and after compaction
  • `mengram import claude-code` reads local Claude Code session history (the README states secrets are redacted on your machine before upload)
  • The policy gate looks up learned workflows before workflow-shaped Bash commands and can be pointed at a local memory folder via MENGRAM_MEMORY_DIR
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Cloud mode uploads conversations and file content to a third-party service, which may include sensitive data; local mode avoids this but needs your own model key
  • Auto-save and auto-recall hooks read and write memory in the background, which can introduce unwanted context
  • Incorrect memories get re-recalled and injected into system prompts, with a persistent effect
  • Procedures evolve automatically and the policy gate can prompt before command execution, so misconfiguration may cause false alarms
  • In folder mode concurrent external edits are not lock-protected and can be overwritten; local search matches words and does not use embeddings or translation
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Cursor, Codex, Windsurf, Cline, Claude Code, OpenClaw, LangChain, CrewAIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00