Skip to main content
Glama
itunified-io

mcp-tailscale

by itunified-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-tailscale

No user-submitted related servers found.

    Related Servers

    • tailscale-mcp-server

      pnocera
      A
      license
      Not graded
      quality
      F
      maintenance
      An 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.
      3
      MIT

    • tailscale-mcp

      TMHSDigital
      A
      license
      A
      quality
      A
      maintenance
      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
      4 npm
      1
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • mcp-tailscale

      aplaceforallmystuff
      A
      license
      A
      quality
      C
      maintenance
      An 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.
      6
      5 npm
      7
      MIT

    • mcp-server

      Ezzeay
      A
      license
      B
      quality
      D
      maintenance
      Production-ready TypeScript MCP server exposing utility, GitHub, and Microsoft Teams tools over stdio.
      14
      1
      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

    A3.6/5.0

    Scored across 49 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action pairs, and the names make selection straightforward. Minor overlap exists between tailscale_dns_nameservers_get and tailscale_dns_preferences_get (both surface MagicDNS status) and between tailscale_acl_validate and tailscale_acl_test.

    Naming Consistency4/5

    The dominant pattern is tailscale_<resource>_<action>, which is applied consistently across most tools. A few outliers break the pattern: tailscale_derp_map and tailscale_status lack an action verb, and tailscale_api_verify places the verb at the end.

    Tool Count2/5

    At 49 tools, this is well beyond the 25+ threshold and makes tool selection a heavy burden for agents. The count reflects the broad Tailscale admin API surface rather than redundant duplicates, but the sheer volume still hurts usability.

    Completeness4/5

    The surface covers nearly all major Tailscale admin resources: devices, DNS, ACL, auth keys, webhooks, users, posture integrations, tailnet settings, log streaming, and DERP maps. Minor gaps exist (no webhook update, no general-purpose device update), but core workflows are fully supported.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources