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.

DimensionOctocode MCP - AI Context PlatformEvidence-first code research for AI agentsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS64 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions14 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • AI agents and developers conducting evidence-first code research.
  • Teams analyzing both local workspaces and GitHub repositories.
  • Code review, refactoring, and architecture work requiring semantic navigation, structural search, and compact context.
  • 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 browser automation, cloud storage, collaboration, or database operations.
  • Environments that cannot grant local workspace or GitHub access.
  • Clients requiring a transport other than stdio.
  • 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 tools can access paths permitted by configuration; local tools are enabled by default.
  • GitHub tools require GitHub authentication; personal access tokens support repo, read:user, and read:org scopes.
  • When cloning is enabled, the server accesses GitHub repositories and uses a local cache.
  • 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
  • Local tools may read code and files within permitted paths; the server blocks many sensitive files and directories.
  • GitHub tokens are sensitive credentials and should be supplied through environment variables or secure credential management, never committed to version control.
  • Secret scanning and automatic redaction may reduce returned-content completeness.
  • Enabling repository cloning expands local caching and external repository data handling.
  • 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 clientsCursor, VS Code, VS Code Insiders, Windsurf, Kiro, Goose, LM Studio, Claude CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1215