← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionDreamGraphA graph-governed architecture cognition layer for MCP-enabled software projects.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS58 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions8 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers whose codebases have grown beyond short-term memory, seeking AI that understands the system and explains changes.
  • Architects, system engineers, and product builders needing an architecture intelligence layer.
  • Projects using MCP clients like Claude Desktop or VS Code that benefit from persistent graph memory.
  • 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 seeking a lightweight chat assistant rather than a complex knowledge graph system.
  • Projects preferring simple tooling without persistent state or architecture governance.
  • Environments without Node.js 20+ or a compatible shell.
  • 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
  • Read project files to build the knowledge graph (scan, enrich).
  • Read and write instance configuration and database (SQLite by default, optional PostgreSQL).
  • Execute `dg` CLI commands to manage daemon lifecycle.
  • VS Code extension permissions: file access, editor integration, daemon connection.
  • Potential network access (via HTTP daemon) and LLM API or local model server connections.
  • 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
  • Cognitive outputs are advisory until backed by governed evidence or explicit review; expired or rejected ideas remain inspectable but not authoritative.
  • Ensure instance configuration is secured, especially when using HTTP transport; do not expose the daemon on untrusted networks.
  • Plugins (when enabled) must be trusted; untrusted plugins may pose risks, but mechanisms for gating and trust banners exist.
  • Backup data before major upgrades, as migration scripts may be needed for older versions (e.g., pre-v8.2.6).
  • 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, VS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015