Skip to main content
Glama
dylantirandaz

Tailscale Compute MCP

by dylantirandaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Tailscale Compute MCP

No user-submitted related servers found.

    Related Servers

    • mcp-ssh-remote

      JasonLinjc
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables executing commands on remote SSH hosts, with full support for bastion/jump hosts and ~/.ssh/config, plus Slurm job management and rsync.
      3
      MIT

    • mcp-drone-mcp

      longjoel
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables parallel agent tasks on disposable Arch Linux drones by providing a local stdio gateway for batch job submission, status monitoring, log retrieval, artifact fetching, and cancellation across SSH-connected runners.
      -

    • nomad

      Ad3n1ne
      A
      license
      B
      quality
      B
      maintenance
      A local MCP server for agentic remote development that enables code sync via rsync, SSH command execution, and long-running task management in remote tmux sessions.
      15
      2
      MIT
    • heliograph by heliograph-io

      heliographofficial

      heliograph-io
      A
      license
      A
      quality
      B
      maintenance
      Runs commands on machines you cannot SSH into by publishing steps to a transport the far side already reaches (git, file share, S3, relay), then reads back a log with every line timestamped in UTC. Seven tools cover send, status, logs, stall detection and a pre-flight check.
      7
      Apache 2.0

    • Remote Shell MCP

      jeefies
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure remote workspace management over SSH, supporting file operations, shell commands, and profile configuration for agent-safe remote code environments.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    compute_status and compute_run are clearly distinct: one inspects the remote node's configuration and health, while the other executes a command. There is no overlap or ambiguity between the two tools.

    Naming Consistency5/5

    Both tools follow the same compute_ prefix with a concise action suffix (status, run), creating a consistent and predictable naming pattern.

    Tool Count4/5

    With only two tools, the server is under the typical 3-15 range, but the scope is intentionally narrow—checking status and running commands on a configured remote node. Each tool is essential and earns its place.

    Completeness5/5

    The server covers the core workflow: verify connectivity/state with compute_status and perform remote work with compute_run, which includes automatic project syncing. No obvious gaps exist for its stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources