Skip to main content
Glama
Sign In
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.
      4
      MIT

    • claude-bridge

      Jenish109
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets a Claude Code session on one Mac run tasks in Claude Code on another Mac over Tailscale. Tools start, follow, list and cancel resumable headless sessions, with token auth and allowlisted folders.
      1
      MIT

    • mcp-drone-mcp

      longjoel
      F
      license
      B
      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.
      13
      -

    • nomad

      Ad3n1ne
      A
      license
      B
      quality
      D
      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
      3
      MIT

    • ssh2mcp

      AndyerNotFound
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a single SSH-reachable host as MCP tools for running and backgrounding remote commands, resumable verified file transfers, and read-only file comparison, stat, hashing, listing and reading. Runs on loopback with per-request Bearer auth and hot-switchable permission levels, letting an agent compile and manage files on a build machine while keeping its workspace on the device.
      MIT
    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

    ActivityStale
    ResponsivenessNo issues

    Resources