M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
P

Pare Remote

Community
Structured SSH and rsync operations as typed JSON.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #431 of 438
Stars
★ 138 Popular
Transport
stdio (local process)
Runtime
Node.js 20+
Credentials
No credential needed
License
MIT
Last commit
Tools
4
23FMRS · D

This server provides structured SSH and rsync operations, suitable for AI agents needing reliable remote operations.

Strongest · Setup experience 6/20 Weakest · Security and permissions 2/20

Reliability
4/20
Security and permissions
2/20
Maintenance
5/20
Documentation
6/20
Setup experience
6/20
Why each score
Reliability 4/20
Only the manifest and repo README were supplied; no source, tests, or CI for packages/server-remote were available. I could not verify that ssh-run, ssh-test, ssh-keyscan, and rsync are actually registered, that their output schemas match, or that the MCP init handshake completes. Per static calibration, missing execution evidence caps the score; I assigned 4.
Security and permissions 2/20
This server's core operations are SSH/rsync remote command execution, yet the supplied material contains no credential-handling, least-privilege, confirmation, or data-boundary details. Remote command execution without explicit confirmation triggers a red-line concern; with no source evidence to refute it, I score within the 0-4 band, giving 2.
Maintenance 5/20
Visible evidence is limited to the MIT license, version 0.22.0, a non-archived repository, and 17 open issues. There is no verifiable commit history, release cadence, dependency-update record, or security-response channel; README badges are untrusted. Maintenance evidence is insufficient, so I score 5.
Documentation 6/20
The README provides general setup, troubleshooting, and links to setup guides, but there are no server-remote-specific parameter docs for ssh-run/ssh-test/ssh-keyscan/rsync, no authentication details, limits, cost, or security boundaries; the linked docs/tool-schemas content was not supplied. Documentation covers general usage only and lacks server-specific depth, so I score 6.
Setup experience 6/20
An install path broadly exists: Node >=20, npx @paretools/init or manual MCP config, and README client config examples. However, there is no server-remote-specific config example and no verifiable startup/connection evidence; static calibration caps setup at 15. I score 6.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeUses the network

Best for

  • AI agents needing reliable remote operation results
  • Developers wanting to reduce parsing overhead from terminal output

Not for

  • Local development scenarios without remote operations
  • Scenarios requiring interactive SSH sessions

Required permissions

  • Requires SSH credentials or keys to authenticate to remote hosts
  • Requires network access to remote hosts
  • May require file system permissions to read private keys

Risks and side effects

  • Remote commands may perform unintended actions; grant tool permissions with caution
  • Risk of SSH key exposure
  • Dependency on remote host availability

Setup

Before you start

Runtime：Node.js 20+

Other optional settings (2)
PARE_TOOLS optional Universal tool filter in server:tool,... format limiting which tools any Pare server registers; not required.
MCP_TIMEOUT optional MCP connection timeout in milliseconds for Claude Code, e.g. 30000 if connections time out; not required.

Install via npm: npm install @paretools/remote. Run with npx: npx @paretools/remote. Requires Node.js >= 20.

Check that it works

Confirm that ssh-run, ssh-test, ssh-keyscan, and rsync appear in the client's tool list, then run an ssh-test prompt — a structured connectivity result proves the connection works.

Troubleshooting

  1. Check Node.js version is >= 20
  2. Ensure SSH authentication configuration is correct
  3. Check network connectivity and remote host reachability
  4. Inspect server logs for error details

Things to try

Once connected, you can ask your AI assistant things like:

  • Use ssh-run to execute uname -a on my remote server and return structured output.
  • Use ssh-test to check whether port 22 on the remote host is reachable.
  • Use ssh-keyscan to fetch the SSH host keys for example.com.
  • Use rsync to sync my local dist directory to /var/www on the remote server.

Tools 4

ssh-run writes
Execute a command on a remote host and return output as structured JSON.
ssh-test read-only
Test SSH connectivity and return connection status and diagnostics.
ssh-keyscan read-only
Retrieve SSH public keys from remote hosts, returning a key list.
rsync writes
Synchronize files between local and remote hosts, returning transfer statistics.

Use cases

Remote command execution
SSH connection diagnostics
Collecting host keys
File synchronization

Overview

Pare Remote is an MCP server in the Pare project that wraps SSH and rsync commands into typed, schema-validated JSON output, replacing fragile terminal text parsing. It provides ssh-run, ssh-test, ssh-keyscan, and rsync tools, returning structured data that AI agents can process directly, reducing token usage and improving reliability.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

More servers from this repository

Pare BazelPare BuildPare BunPare CargoPare CmakePare DBPare DenoPare DockerPare DotnetPare GitPare GithubPare GoPare HTTPPare InfraPare JvmPare LintPare MakePare NixPare NpmPare Process

Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method