mcp-ssh-toolkit-py

Created By
VitalyMalakanova year ago
mcp-ssh-toolkit-py is a powerful MCP server for secure SSH command execution via Model Context Protocol.
Overview

What is mcp-ssh-toolkit-py?

mcp-ssh-toolkit-py is a powerful Model Context Protocol (MCP) server designed for secure SSH command execution, enabling automation and management of remote servers.

How to use mcp-ssh-toolkit-py?

To use the toolkit, you can either run it via Docker or install it using pip. After installation, you can execute commands on remote servers by calling the ssh_execute_command tool with the necessary parameters.

Key features of mcp-ssh-toolkit-py?

  • Execute arbitrary commands on remote servers via SSH.
  • Upload and download files using SFTP.
  • Integration with Claude/Cline and other MCP clients.
  • Supports both password and SSH key authentication.
  • Configurable connection parameters such as timeouts and ports.

Use cases of mcp-ssh-toolkit-py?

  1. Automating DevOps tasks through LLMs.
  2. Managing servers via a chat interface.
  3. Securely executing scripts on remote machines.
  4. Integrating SSH capabilities within the MCP ecosystem.

FAQ from mcp-ssh-toolkit-py?

  • What programming language is used?
    The toolkit is built using Python.

  • Is there a Docker image available?
    Yes, a ready-to-use Docker image is provided for easy deployment.

  • How secure is the connection?
    Connections are encrypted, and no credentials are stored or logged.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
VitalyMalakanov
Star
1
Language
Python
License
MIT 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)

2 days ago