mcp-tailscale
Related Servers
Alternatives to mcp-tailscale
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP (Model Context Protocol) server for managing Tailscale resources using the official Tailscale Go client library v2. This server provides complete coverage of the Tailscale API with enhanced, self-descriptive tools powered by OpenAPI documentation.3MIT
- AlicenseAqualityAmaintenanceMCP server for safe programmatic access to the local Tailscale daemon: tailnet discovery, SSH config generation, port sharing via Serve/Funnel, and latency matrices.64 npm1Creative Commons Attribution Non Commercial No Derivatives 4.0 International
- AlicenseAqualityCmaintenanceProduction-ready MCP server for Tailscale management with 48 tools across 9 domains: Devices, DNS/Split DNS, ACL policies, Auth Keys, Users, Webhooks, Posture Integrations, Tailnet Settings, and Diagnostics. Supports stdio and SSE transport with Bearer token authentication. Built with TypeScript strict mode, Zod validation, and zero shell execution. AGPL-3.0 + Commercial dual-licensed.4993 npm1AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceWraps the Tailscale CLI to enable MCP-capable AI agents to manage devices, serve configurations, and diagnose connectivity.3MIT
- AlicenseNot gradedqualityAmaintenanceMCP server and CLI for Tailscale that lets agents inspect and manage tailnet devices, routes, users, keys, DNS, and ACL policy over stdio or streamable HTTP.5AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.MIT
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose with no ambiguity: checking updates, getting a device summary, retrieving a specific device, listing all devices, listing offline devices, and listing online devices. The descriptions clearly differentiate each tool's function, making misselection unlikely.
All tool names follow a consistent 'tailscale_verb_noun' pattern with snake_case throughout. The verbs (check, get, list) are used appropriately and predictably, creating a cohesive naming scheme that enhances usability.
With 6 tools, this server is well-scoped for managing Tailscale devices. Each tool earns its place by covering distinct aspects of device monitoring and management, avoiding both bloat and thin coverage for this domain.
The toolset provides strong coverage for device querying and monitoring (list, get, summary, status filters, update checks). A minor gap exists in device management operations like modifying device settings or removing devices, but core workflows are well-supported.