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.

DimensionCtxlintLint your AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS57 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions11 / 2014 / 20
Maintenance9 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers and teams using AI coding assistants (e.g., Claude Code, Cursor).
  • Projects with multiple context files and complex structure.
  • Teams that need to maintain accurate agent context.
  • Environments with strict security requirements for MCP configs (e.g., no hardcoded API keys).
  • 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
  • Projects that don't use AI context files.
  • Simple, solo projects where files change infrequently (may be overkill).
  • Non-critical projects that don't require strict context maintenance.
  • 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 context and config files in the project directory (e.g., CLAUDE.md, .mcp.json).
  • Optionally reads user-level config files (e.g., ~/.claude/settings.json) and global MCP configs (with --mcp-global).
  • Optionally reads agent history and memory files in the user's home directory (e.g., ~/.claude/history.jsonl) when session or skill audits are enabled.
  • Optionally writes context files to fix broken paths when --fix is enabled.
  • 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
  • Auto-fix (--fix) may modify files unexpectedly; preview with --fix-dry-run and review changes.
  • Session audit accesses sensitive history files in the home directory; enable only in trusted environments.
  • The tool reads config and context files that may contain secrets (e.g., API keys); ensure access is controlled.
  • Redundancy checks may produce false positives as inferred content may vary by context.
  • 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, Cursor, Windsurf, VS Code, GitHub CopilotClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools715