M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← 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 learnsContext7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS57 / 100 · C80 / 100 · B
Reliability9 / 2014 / 20
Security and permissions11 / 2016 / 20
Maintenance12 / 2017 / 20
Documentation13 / 2015 / 20
Setup experience12 / 2018 / 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)
  • Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
  • Scenarios wanting zero-config documentation lookup
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
  • Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
  • Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
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
  • Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
  • Read-only documentation lookup — no code execution or local filesystem access involved
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
  • The free tier has limited quota — high-frequency use may hit rate limits
  • Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
Supported clientsClaude Desktop, Cursor, Codex, Windsurf, Cline, Claude Code, OpenClaw, LangChain, CrewAIClaude Code, VS Code, Cursor, Cline, Amp
Tools02