ssh-connect MCP server

Created By
t-suganumaa year ago
An MCP server for SSH connections and file operations.
Overview

What is ssh-connect MCP server?

The ssh-connect MCP server is a tool designed for establishing SSH connections and performing file operations on remote servers.

How to use ssh-connect MCP server?

To use the ssh-connect MCP server, configure the SSH connection parameters in the MCP settings and utilize the provided commands to connect, execute commands, upload/download files, and manage files on the SSH server.

Key features of ssh-connect MCP server?

  • Connect and disconnect from SSH servers.
  • Execute commands on remote servers with output retrieval.
  • Upload and download files to/from the SSH server.
  • List files in a directory on the SSH server.

Use cases of ssh-connect MCP server?

  1. Managing remote servers via SSH.
  2. Automating file transfers between local and remote systems.
  3. Executing scripts or commands on remote servers for maintenance or data processing.

FAQ from ssh-connect MCP server?

  • What programming language is used for this project?

The ssh-connect MCP server is implemented in Python.

  • Is there a way to test the server functionality?

Yes! Example scripts and a test script are provided to demonstrate and verify the server's functionality.

  • Can I configure the server for different SSH authentication methods?

Yes! You can configure the server to use either password or key-based authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
t-suganuma
Star
0
Language
Python
License
-

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