vssh

io.github.meshpopPublished by GitHub account meshpopv3.3.0Updated Oct 24, 2026

SSH tunnel and remote server management MCP — execute commands, transfer files, manage

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant run commands and transfer files on remote servers over SSH, and manage SSH tunnels.

What you can do
This is a local MCP server for SSH tunnel and remote server management. According to its registry description, it lets an assistant execute commands on remote hosts, transfer files, and manage tunnels. No tool list is published, so the exact tool names and parameters are not documented here.
When to use it
Consider it when an assistant needs to operate on remote machines over SSH — running commands, moving files, or setting up and managing tunnels — from a desktop MCP client. It is less useful if you only work with local files or already have a dedicated deployment tool.
Requirements
Runs as a local process on the user's machine over stdio, and is marked desktop only. No packages, environment variables, headers, or authentication are declared, so the runtime and any SSH credentials or key material it needs are not specified in the available information.
Before you install
It is described as executing commands and transferring files on remote servers, which can change or delete data on those hosts. Credentials, keys, and host details it may require are not declared, so review what access it is given before installing.

Installation

In SourceWeft

  1. Open vssh 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. v3.3.0LatestSep 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.