SSH MCP Tool

io.github.oaslanankaPublished by GitHub account oaslanankav2.2.7Updated Oct 25, 2026

Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local MCP server for SSH automation with policy controls, exposed over stdio or HTTP so an assistant can run remote server tasks.

What you can do
Run SSH automation tasks against remote hosts through the MCP server, subject to its policy controls. Use built-in resources and prompts alongside the tools to guide remote operations. Connect over stdio for local use, or over Streamable HTTP for browser-based clients with restricted origins. Apply policy controls to constrain what automation is permitted.
When to use it
Worth adding when you want an assistant to carry out SSH-based automation on remote machines and you need policy limits and a choice of stdio or HTTP transport. It suits local desktop use rather than shared web deployments.
Requirements
Runs as a local process on the user's machine, installed from the npm package mcp-ssh-tool over stdio; desktop only. For non-loopback HTTP bindings it needs SSH_MCP_HTTP_BEARER_TOKEN_FILE (path to a bearer token file) and SSH_MCP_HTTP_PUBLIC_URL, plus optionally SSH_MCP_HTTP_ALLOWED_ORIGINS and SSH_MCP_HTTP_TRUST_PROXY.
Before you install
The server performs SSH automation on remote hosts, so actions may change or delete data there; review its policy controls before use. For non-loopback HTTP it requires a bearer token file referenced by SSH_MCP_HTTP_BEARER_TOKEN_FILE, and SSH_MCP_HTTP_TRUST_PROXY should only be enabled behind a trusted reverse proxy. Keep allowed origins restricted when not using loopback.

Installation

In SourceWeft

  1. Open SSH MCP Tool in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.2.7LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.