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.

DimensionRemem MCP ServerLocal-first persistent memory for coding agents: automatic capture, distillation, and recall.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS66 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation18 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers using Claude Code or Codex CLI long-term
  • Teams needing searchable, auditable, project-scoped memory
  • Users who want data to stay local (SQLite/SQLCipher)
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Cursor users (v1 lacks session-init injection and automatic capture)
  • Anyone needing hosted or team-shared memory services
  • Users wanting a zero-install, no-local-binary solution
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Reads/writes the ~/.remem/ data directory and encrypted database
  • Modifies Claude Code / Codex / Cursor config files to register hooks and the MCP server
  • Calls the configured LLM API in the background for summarization and distillation (incur token costs)
  • Optional local REST API binds only to 127.0.0.1 and requires Bearer token auth
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Background memory summarization via external LLMs incurs ongoing token costs
  • Cursor integration is v1: automatic capture and session-init are not enabled, and config updates are not cross-file atomic
  • Stores project and user context; accidental secret-like content relies on built-in redaction scans and suppression tooling
  • Command enforcement (block mode) is Claude Code only; explicitly unsupported on Codex
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, OpenAI Codex CLI, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615