Tailscale Compute MCP server

Tailscale Compute MCP

Run builds, tests, and benchmarks on your own remote compute node from an MCP coding agent.

The coding agent edits files on your local computer. This MCP server copies the project through rsync and runs a command through SSH only when the agent calls compute_run.

This is an independent project. It is not an official Tailscale product and is not endorsed by Tailscale Inc. Tailscale is a trademark of Tailscale Inc.

Release status

This package is a beta.

• The full path has run on a Mac laptop and an Apple M4 Mac mini.
• The server includes Linux probes and NVIDIA inventory support.
• Linux parsing has automated coverage.
• This release has not run on a real NVIDIA DGX Spark. Do not treat the Linux or NVIDIA result as DGX Spark validation yet.

How it works

MCP coding agent
    |
    | local stdio
    v
Tailscale Compute MCP
    |
    | rsync and SSH through the user's tailnet
    v
Mac or Linux compute node

The package runs on the local computer. No MCP service runs on the remote node. The project author does not receive your code, credentials, command output, or Tailscale traffic.

Security warning

compute_run can run any non-interactive command with the permissions of the remote SSH user. Treat it as remote code execution.

• Use a dedicated non-root account on the remote node.
• compute_status reports the remote user id and warns when the SSH user is root. Run compute through a non-root user so a compromised build cannot control the whole node.
• Command starts, artifact fetches, and successful workspace deletions are recorded in a local audit log. The log never contains environment values, standard input, or credentials.
• Do not auto-approve command, fetch, cancel, or deletion tools.
• Do not put passwords, SSH private keys, or Tailscale auth keys in MCP configuration.
• Use an SSH agent or Tailscale SSH.
• Limit access with Tailscale policy rules.
• Review SECURITY.md before use.

Requirements

Local computer

• Node.js 20 or later.
• Tailscale connected to the same tailnet as the remote node.
• OpenSSH client.
• rsync with --include and --exclude support.
• An MCP host that supports local stdio servers.

macOS and Linux are the supported local systems for this beta.

Remote node

• Darwin or Linux.
• Tailscale connected.
• SSH server.
• rsync available on PATH.
• A known SSH host key.
• The toolchain required by the project.

The MCP package does not need Node.js on the remote node unless the remote workload uses Node.js.

Set up a Mac mini

1. Install and connect Tailscale on both Macs.
2. On the Mac mini, open System Settings, select General, select Sharing, and turn on Remote Login.
3. Add the local public key to the remote account:

ssh-copy-id -i ~/.ssh/id_ed25519.pub user@mac-mini.example.ts.net

1. Verify the host key and non-interactive access:

ssh user@mac-mini.example.ts.net /usr/bin/true

1. Check the remote tools:

ssh user@mac-mini.example.ts.net '/bin/zsh -lc "rsync --version"'

A sleeping or powered-off Mac might not accept a Tailscale connection. Configure macOS network wake when required. This MCP server does not send wake packets.

Set up a Linux node

Install and connect Tailscale by using the official Tailscale instructions for your Linux distribution. Then install an SSH server and rsync.

For Ubuntu or Debian:

sudo apt-get update
sudo apt-get install --yes openssh-server rsync
sudo systemctl enable --now ssh

Use a standard SSH key:

ssh-copy-id -i ~/.ssh/id_ed25519.pub user@compute-node.example.ts.net
ssh user@compute-node.example.ts.net /usr/bin/true

You can use Tailscale SSH on supported Linux nodes instead of distributing SSH keys. Your Tailscale policy must permit both the network connection and SSH connection.

Install in an MCP host

Shortened. The full README is on GitHub.