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.

DimensionMemory Journal MCP ServerPersistent memory and context handoff across AI sessions, with deep GitHub workflow integration.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS70 / 100 · B76 / 100 · B
Reliability11 / 2013 / 20
Security and permissions15 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers working on large projects who need persistent AI memory.
  • Teams want to integrate IDE agents and GitHub Copilot with shared context.
  • Engineers managing multiple repositories who need unified project intelligence.
  • 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
  • Users who need only a trivial, stateless tool without any configuration.
  • Projects where persistent memory is explicitly not desired due to privacy concerns.
  • Environments that do not permit local file storage or database files.
  • 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
  • Local filesystem access limited by the `ALLOWED_IO_ROOTS` environment variable, used for import/export and Code Mode.
  • GitHub API access via the `GITHUB_TOKEN` to interact with issues, PRs, actions, etc.
  • Network access for remote HTTP/SSE transport, fetching embedding models, and OAuth token validation.
  • Read/write access to SQLite database files stored on the local machine.
  • 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
  • Misconfiguration of `ALLOWED_IO_ROOTS` could expose unintended file paths to the MCP tools.
  • A compromised GITHUB_TOKEN could allow unauthorized access to your repositories.
  • Code Mode executes sandboxed JavaScript, but there is always a risk if the sandbox is not perfectly isolated.
  • HTTP transport without proper authentication (e.g., OAuth or token) could allow unauthorized access.
  • Third-party embedding models may introduce supply chain risks.
  • 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 Desktop, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools6415