MCP SSH Agent

Created By
AiondaDotComa year ago
A Model Context Protocol (MCP) server for managing and controlling SSH connections.
Overview

what is MCP SSH?

MCP SSH is a Model Context Protocol (MCP) server designed for managing and controlling SSH connections through a standardized STDIO interface, utilizing native SSH commands for reliability and compatibility.

how to use MCP SSH?

To use MCP SSH, clone the repository, install dependencies, and start the server. It integrates with MCP-compatible clients to facilitate SSH operations.

key features of MCP SSH?

  • Reliable SSH operations using native ssh/scp commands.
  • Automatic discovery of SSH hosts from configuration files.
  • Full support for SSH agents, keys, and various authentication methods.
  • Ability to upload and download files using scp.
  • Execute multiple commands in sequence with batch processing.
  • Comprehensive error handling and reporting.

use cases of MCP SSH?

  1. Managing SSH connections in a development environment.
  2. Automating file transfers between local and remote servers.
  3. Executing remote commands in batch for system administration tasks.

FAQ from MCP SSH?

  • Can MCP SSH work with any SSH configuration?

Yes! MCP SSH automatically discovers hosts from your SSH config and known_hosts files.

  • Is there a graphical interface for MCP SSH?

No, MCP SSH operates through a command-line interface and STDIO.

  • What are the system requirements for MCP SSH?

Node.js 18 or higher and a properly configured SSH setup are required.

Server Config

{
  "mcpServers": {
    "mcp-ssh": {
      "command": "npx",
      "args": [
        "@aiondadotcom/mcp-ssh"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AiondaDotCom
Star
1
Language
JavaScript
License
MIT license
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago