A
licenseA
qualityB
maintenanceEnables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
6
5 npm
MIT
portveil-mcp
by roybogs
Related Servers
Alternatives to portveil-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to remotely control multiple devices registered to the same account, executing system commands via the Remote Control Assistant desktop bridge.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage VPN infrastructure through provisioning, lifecycle control, traffic routing, and health monitoring.2-
- FlicenseBqualityCmaintenanceEnables AI assistants to discover devices and perform connectivity diagnostics across a private Tailscale or WireGuard mesh through authenticated CLI or REST API backends. Supports safe dry-run simulations before affecting live node state.2-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage agents, webhooks, and P2P connectivity on the Anycast network, allowing operations like listing agents, creating tokens, and viewing connection stats.6 npmMIT
- AlicenseAqualityCmaintenanceEnables 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
TDQS
A4.4/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct device-management action (move vs rotate vs start/stop rotation vs reconnect/disconnect), and descriptions explicitly clarify boundaries, e.g. 'To just go somewhere different, use rotate_device.' list_devices vs get_device is also clearly separated.
Naming Consistency5/5
All names follow a consistent snake_case verb_noun pattern (get_*, list_*, add_device, update_device, remove_device, move_device, rotate_device, start_rotation, stop_rotation, reconnect_device, disconnect_device). No mixed conventions or vague verbs.
Tool Count5/5
14 tools is well within the 3–15 sweet spot for a VPN/device management server, and each tool covers a distinct operation (account, activity, device CRUD, locations, rotation, connection control). No obvious redundancy or filler.
Completeness4/5
Core device and rotation lifecycle is fully covered (add/list/get/update/remove, move/rotate/start/stop, reconnect/disconnect, locations, activity). Minor gap: token creation/management is referenced (control-scope, admin-scope tokens; 'tokens created' in activity) but no tool exposes it, and account plan changes are read-only.
Maintenance
ActivityMaintained
ResponsivenessNo issues