Tailscale MCP by usefulapi
Server Details
Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 22 tools
Each tool targets a distinct resource+action, and descriptions clearly delimit overlapping-sounding operations like delete_key vs expire_device_key vs authorize_device (different resources, explained as security/kill-switch actions). The DNS group (get_dns_preferences, get_split_dns, list_dns_nameservers, list_dns_searchpaths) is granular but each covers a separate sub-resource, so an agent can still select correctly.
Every tool follows a strict tailscale_verb_noun pattern (list_devices, get_device, create_auth_key, delete_key, set_device_tags). Verbs are consistent across resources, with no camelCase or style mixing.
22 tools is on the heavy side of the ideal 3-15 band, but the domain spans devices, keys, users, DNS, webhooks, ACL, and settings, so each tool maps to a real API endpoint rather than filler. Slightly over but justified by the broad management surface.
Device and key lifecycles are well covered (list/get/create/delete/rename/tag/route/expire), but many resources are read-only: DNS preferences/split-DNS/nameservers/searchpaths, ACL policy, tailnet settings, and webhooks have only getters or list, with no setters or create/delete. This leaves notable write-side gaps for a management server.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
Manage ngrok from your agent: endpoints, domains, and traffic policy.
Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics.
Manage Fly.io apps, Machines, volumes, secrets, Managed Postgres, and Sprites with OAuth.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables administering a Tailscale tailnet through a single action-router tool that maps requests to the Tailscale API v2: listing and inspecting devices and routes, reading keys, ACL policy, DNS settings and users, and authorizing devices. Device deletion is double-gated behind a confirm flag plus an environment opt-in, refusing the call before any request if either gate is missing.315 npmMIT
- AlicenseBqualityBmaintenanceManage your Tailscale tailnet - devices, ACLs, DNS, keys, and more - through natural language queries.98748 npm35MIT
- AlicenseNot gradedqualityDmaintenanceWraps the Tailscale CLI to enable MCP-capable AI agents to manage devices, serve configurations, and diagnose connectivity.3MIT
- 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
Glama MCP Gateway
Add one secure layer between your agents and this server.