A
licenseNot graded
qualityB
maintenanceEnables authenticated web agents to reach a local machine through a portable MCP endpoint, with optional Cloudflare Tunnel or Tailscale Funnel ingress for public access.
MIT
tslink
by anydoor7
Related Servers
Alternatives to tslink
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePublishes a single self-hosted MCP endpoint that lets AI apps reach all of your machines through outbound-only device agents, so they can read, write, and run commands within permitted folders on each device with per-key access levels and folder/device scoping. Every allowed or denied call is checked against the app's key and recorded in an audit log, with support for HTTPS/tunnels and OAuth for web-based clients.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP 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
- FlicenseNot gradedqualityNot gradedmaintenanceExposes a governed suite of 38 tools over one OAuth-gated MCP endpoint so web AI chat clients can read and edit files, run whitelisted shell commands, search, query Git/SQLite, drive browsers via DevTools, and manage background jobs on the local machine. Remote access runs through Tailscale Funnel while local tools connect straight to 127.0.0.1, keeping operations permission-scoped rather than granting unrestricted shell access.-
- AlicenseAqualityAmaintenanceMCP server for safe programmatic access to the local Tailscale daemon: tailnet discovery, SSH config generation, port sharing via Serve/Funnel, and latency matrices.6161 npm1Creative Commons Attribution Non Commercial No Derivatives 4.0 International
TDQS
A3.6/5.0
Scored across 48 tools
Disambiguation2/5
Several clusters overlap heavily: add/share/recipe_apply/template_apply all create or expose services, while people_add/people_grant/people_update/invite_device/extend all modify access and deadlines. status/doctor/health/logs also overlap around diagnostics. Descriptions cross-reference alternatives and help, but with 48 tools the boundaries are still not clean enough to reliably prevent misselection.
Naming Consistency3/5
Domain-prefixed families such as guest_, people_, invite_, portal_route_, access_, recipe_, and template_ are internally consistent and readable. However, core tools are bare nouns or verbs (add, share, list, url, status, health, logs), and the noun/verb ordering varies across families, so the overall convention is mixed.
Tool Count2/5
At 48 tools, the surface is far above the 3-15 sweet spot and likely overwhelms an agent selecting among similar operations. The domain is complex, but several families (recipe/template, people/invite, access/diagnostics) could be consolidated or staged behind fewer tools.
Completeness4/5
Coverage is broad: service sharing, people/guest access, invitations, portal routes, requests, access logs, recipes/templates, and diagnostics are all represented. Minor gaps remain around a generic service update/edit operation and changing exposure settings such as Funnel after creation, though agents can often work around these via unshare/add flows.
Maintenance
ActivityActive
ResponsivenessOutdated data