← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionOKFy MCP ServerTurn docs into Open Knowledge Format bundles served to AI agents over a local read-only MCP server.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS63 / 100 · C76 / 100 · B
Reliability11 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams that need the knowledge behind agent answers to stay inspectable, versioned, and portable
  • Local-first workflows that avoid hosted indexes, cloud registries, or cloud refresh workers
  • Scenarios requiring visible source references and conservative link resolution that warns instead of guessing
  • Deployments that want deterministic lexical search without an embedding service or LLM key
  • 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
  • Retrieval quality that depends on vector or semantic search
  • Heading-based splitting, or Obsidian semantics like Canvas, Bases, PDFs, images, audio, video, and Dataview fields
  • Importing GitHub repository URLs directly (there is no dedicated importer; use a local checkout or docs folder)
  • Workflows that need to write back to the knowledge source or need agent-callable write tools
  • 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 local bundle directories and source cache and refresh state under ~/.okfy
  • Make same-origin network fetches to registered documentation sites when refresh is enabled (respects robots.txt by default)
  • Be launched as a stdio subprocess by an MCP client; the tools themselves are read-only
  • 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
  • HTML cleanup quality varies by documentation site and can affect search results
  • Preflight rejects DNS-resolved private targets, but fetch-time DNS is not IP-pinned, leaving a theoretical DNS rebinding risk
  • The default stale-while-refresh mode can briefly serve non-latest docs; blocking or off modes change this
  • One page or file becomes one concept with no heading-based splitting, so granularity can be coarse
  • `--force` replaces a non-empty output bundle, and unsafe output directories are rejected unless an explicit dangerous override is given
  • 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, Claude Code, Codex, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615