Tailscale is a zero config VPN that creates a secure network between your servers, computers, and cloud instances. It works everywhere, even behind NATs and firewalls.
Shared rooms for coding agents from different vendors (Claude Code, Codex, Gemini CLI, opencode): 25 MCP tools for room messages, file claims that expire, shared state, memory and moving git branches between machines.
25
596 PyPI
5
MIT
Why this server?
Allows listing devices on a Tailscale network using Dashbrr's integration.
MCP server exposing Dashbrr's REST API as tools, so an LLM can read and manage a dashbrr instance: configured services, per-service health, and summary panels for many apps. Write tools cover settings management, download-queue deletes, Overseerr approvals, UI preferences, and the Plex auth PIN flow.
34
MIT
Why this server?
Enables analysis of anomalous network calls to identify Tailscale VPN traffic, aiding in suppression rule creation.
MCP server for safe programmatic access to the local Tailscale daemon: tailnet discovery, SSH config generation, port sharing via Serve/Funnel, and latency matrices.
6
902 npm
1
Creative Commons Attribution Non Commercial No Derivatives 4.0 International
Why this server?
Supports Tailscale as a pluggable transport backend to enable secure networking and connectivity between the MCP server and distributed OpenCode instances.
An MCP server that enables discovery and interaction with multiple OpenCode instances across different machines using SSH reverse tunnels. It provides tools for listing instances, managing chat sessions, and sending messages to remote coding environments.
3
16 npm
MIT
Why this server?
Optional gateway links your own machines and phone over your Tailscale tailnet, enabling agentsocks communication beyond the local machine.
Enables Claude Code, Codex, and other coding-agent sessions on the same machine to message each other, exchange tracked tasks with owners and states, and coordinate through channels, broadcasts, and multi-session asks without typing into terminals. Messages are routed by what the receiver is doing — next tool call, end of turn, or a held-back digest — so a flood of traffic doesn't interrupt active work.
14
78 npm
1
MIT
Why this server?
Provides tools for managing Tailscale tailnet devices, including listing devices, removing devices, and joining hosts to the tailnet.
Enables an agent to oversee and operate a fleet of Linux servers over the system ssh and Tailscale — inspecting host status, auditing configuration, tracking drift and reading history across many machines. Every mutating operation runs as a dry-run plan first and only applies after explicit confirmation of that exact plan, rolling out one host at a time with a local journal.
63
MIT
Why this server?
Enables secure remote access to the approval GUI over Tailscale network.
MCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.
