Remote Terminal MCP

io.github.TiM00RPublished by GitHub account TiM00Rv1.3.3Updated Oct 24, 2026

Complete SSH terminal for Linux with AI/user control and dual-stream visibility

The publisher's own server: Terminal Tax

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an AI assistant an SSH terminal to Linux hosts, with shared AI and user control and dual-stream visibility.

What you can do
  • Open and manage SSH sessions to Linux machines from the assistant.
  • Run terminal commands over those sessions with both AI and user control.
  • Observe output through dual-stream visibility, so the assistant and the user can follow the same session.
  • Keep configuration files and a database under a configured root directory.
When to use it
Useful when you want an assistant to operate Linux servers over SSH, run commands and follow along in the same terminal session, rather than only reading files or docs locally.
Requirements
Runs as a local process (PyPI package remote-terminal-mcp, stdio transport) on a desktop machine. Requires the environment variable REMOTE_TERMINAL_ROOT, which sets the root directory for config files and the database. SSH access to the target Linux hosts is implied by its purpose but not detailed in the listing.
Before you install
The assistant can run commands on remote Linux hosts, which can change or delete data and affect running services; review what it executes. SSH credentials and host details are stored in config files and a database under REMOTE_TERMINAL_ROOT, so protect that directory. No authentication is declared for the server itself.

Installation

In SourceWeft

  1. Open Remote Terminal MCP 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.

Tools

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

Version history

1
  1. v1.3.3LatestSep 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.

Other Terminal integrations