Tailscale MCP Server

io.github.itunified-ioPublished by GitHub account itunified-iov2026.3.16Updated Oct 24, 2026

Secure MCP access for private infrastructure over Tailscale — 48 tools across 9 domains

Overview

AI-generated overview

A local MCP server that gives an assistant 48 tools across 9 domains for managing private infrastructure through the Tailscale API.

What you can do
Manage Tailscale tailnet resources through 48 tools grouped into 9 domains, covering devices, network configuration and related administrative areas of a tailnet. The README and tool list are not supplied, so the exact operations per domain are not documented here. Access is authenticated with a Tailscale API key or an OAuth client.
When to use it
Worth adding when an assistant should inspect or administer a Tailscale tailnet — for example devices and network settings — from a desktop MCP client, instead of switching to the Tailscale admin console.
Requirements
Runs locally as a Node.js process via npx (package tailscale-mcp), desktop client only. Needs a Tailscale account and either TAILSCALE_API_KEY or the OAuth pair TAILSCALE_OAUTH_CLIENT_ID and TAILSCALE_OAUTH_CLIENT_SECRET, plus TAILSCALE_TAILNET for the tailnet name. Network access to the Tailscale API.
Before you install
Requires a Tailscale API key or OAuth client secret, which grant administrative access to the tailnet; store them securely and scope them narrowly. Administrative tools may change or delete network and device configuration, so review actions before they run. The full tool list is not published, so verify what each tool does before use.

Installation

In SourceWeft

  1. Open Tailscale MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2026.3.16LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.