starlink-blade-mcp
Related Servers
Alternatives to starlink-blade-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides live astronomical telemetry and space data, including ISS tracking, NASA APOD, and solar weather, via a Model Context Protocol server with SSE and JSON-RPC support.MIT
- AlicenseCqualityCmaintenanceA local-first Model Context Protocol server that enables AI-assisted development through scoped file access, opt-in shell and process execution, Git automation, development pipelines, and optional Windows desktop and Android/ADB tools. It supports streamable HTTP and stdio transports with secure local-only defaults.105MIT
- AlicenseAqualityBmaintenanceA developer-focused server that exposes information from VW vehicles via a Model Context Protocol (MCP) interface. This project is designed for integration, automation, and experimentation with connected car data.33CC BY-SA 4.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that lets AI assistants control Samsung Smart TVs (Tizen OS, 2016+) over the local network. No cloud, no SmartThings account required.1MIT
- AlicenseAqualityAmaintenanceEnables users to query a Tesla vehicle's battery, charging, climate, odometer, software, location, charging history, and local mileage or range reports through a local stdio MCP connector. Status can come from cached snapshots without waking the car, while wake-and-refresh is budget-gated and no vehicle commands are exposed.9MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP (Model Context Protocol) server that exposes Polestar 2 vehicle data to AI assistants like Claude. Query your car's battery status, vehicle info, and health data through natural conversation.1MIT
TDQS
Scored across 9 tools
Each tool targets a distinct aspect of Starlink dish management: status, alerts, obstruction, history, location, diagnostics, and three write operations (reboot/stow/unstow). The only potential confusion is between starlink_status and starlink_diagnostics, which both report firmware/state/uptime, but their descriptions differentiate status (connectivity summary) from diagnostics (troubleshooting detail).
All tool names follow a consistent starlink_<noun> pattern, with verbs only for the write operations (reboot, stow, unstow). This is a predictable and uniform convention across the entire set.
Nine tools is well-scoped for a Starlink dish management server: six read-only monitoring/diagnostic operations and three write operations cover the core domain without redundancy or bloat.
The surface covers the main Starlink dish operations: status, alerts, obstruction, history, location, diagnostics, reboot, stow, and unstow. Minor gaps exist (e.g., no tool for changing dish settings or updating firmware), but the core monitoring and recovery workflows are complete.