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.

DimensionSSH Manager MCP ServerSSH remote server management via Model Context ProtocolGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS52 / 100 · D76 / 100 · B
Reliability5 / 2013 / 20
Security and permissions9 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers and DevOps engineers using Claude Code or OpenAI Codex
  • Teams managing multiple servers who want to automate routine tasks
  • Sysadmins needing quick command execution, file transfer, or monitoring
  • 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
  • Non-technical users, as SSH and command-line basics are required
  • Highly security-sensitive environments if misconfigured, as SSH credentials exposure is a risk
  • Use cases requiring agent installation on each server, as this uses direct SSH
  • 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
  • Access to local SSH config and credentials (passwords, keys, ssh-agent)
  • Ability to execute remote commands, transfer files, manage databases and backups
  • Ability to create SSH tunnels and persistent sessions
  • Ability to read and modify local .env and TOML configuration files
  • 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
  • Credentials may be stored in plaintext in config files, posing security risks if files are compromised
  • Executing arbitrary commands via ssh_execute can cause unintended changes or damage
  • SSH agent forwarding can expose local keys to remote hosts if used with excessive permissions
  • Unstable network connections may lead to command timeouts or failures
  • 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 Code, CodexClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools3615