A
licenseNot graded
qualityD
maintenanceQuery devices, check connectivity, and get network status from your Tailscale tailnet directly via an AI assistant.
1
MIT
@yawlabs/tailscale-mcp
by YawLabs
Related Servers
Alternatives to @yawlabs/tailscale-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to securely interact with Tailscale tailnets for device inventory, ACL review, key hygiene, and more, with token-efficient output and write-gated mutations.19MIT
- AlicenseNot gradedqualityDmaintenanceWraps the Tailscale CLI to enable MCP-capable AI agents to manage devices, serve configurations, and diagnose connectivity.3MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with the Tailscale API to manage devices, ACLs, keys, and DNS configurations directly from MCP clients like Claude Desktop or Raycast.-
- AlicenseAqualityCmaintenanceEnables Claude to connect and disconnect the host machine from its Tailscale network via the local CLI, and to manage the wider tailnet (devices, routes, DNS, ACL policy, auth keys, webhooks, users, audit log) through the Tailscale REST API. Access is governed by configurable risk tiers, with destructive operations gated behind interactive human approval.189 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server for managing and monitoring Tailscale networks through natural language. It enables users to list devices, check connection status, monitor for client updates, and retrieve detailed tailnet summaries.611 npm7MIT
TDQS
A3.5/5.0
Scored across 98 tools
Disambiguation4/5
Most tools are clearly separated by resource and action (devices, users, ACL, DNS, services, webhooks, keys, etc.), so an agent can usually tell them apart. Some overlap exists between the unified DNS getter/setter and the individual DNS tools, and between single-device and batch operations, but the descriptions explain the distinctions. With 98 tools, a few pairs still risk misselection.
Naming Consistency4/5
Almost all tools follow the tailscale_verb_noun pattern (list_devices, create_webhook, delete_device, update_acl), which is highly consistent. Minor exceptions like tailscale_status and tailscale_tool_groups break the verb_noun pattern, and a few singular/plural mismatches (set_device_posture_attribute vs get_device_posture_attributes) keep it from being perfect.
Tool Count2/5
98 tools is far beyond the well-scoped range and even the heavy 25+ threshold. While Tailscale's API is broad, this is too many tools for one MCP server; agents will struggle to navigate the surface. Many tools could be consolidated (e.g., unified DNS vs individual DNS setters) or split into domain-specific servers.
Completeness5/5
The tool set covers essentially the full Tailscale management surface: devices, users, invites, keys, ACL, DNS, services, posture integrations, webhooks, log streaming, OAuth apps, tailnet settings, contacts, audit logs, and network flow logs. CRUD/lifecycle operations are present for each resource, and destructive operations are paired with getters/listers, leaving no obvious dead ends.
Maintenance
ActivityActive
ResponsivenessUnresponsive