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 ProtocolMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS52 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 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
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
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
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
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
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
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
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Code, CodexClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools360