starlink-blade-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STARLINK_TIMEOUT | No | gRPC timeout in seconds | 10 |
| STARLINK_MCP_HOST | No | HTTP transport bind address | 127.0.0.1 |
| STARLINK_MCP_PORT | No | HTTP transport port | 8770 |
| STARLINK_DISH_ADDRESS | No | Dish gRPC endpoint | 192.168.100.1:9200 |
| STARLINK_MCP_TRANSPORT | No | stdio or http | stdio |
| STARLINK_WRITE_ENABLED | No | Enable reboot/stow/unstow | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| starlink_statusA | Get current dish status: identity, connectivity, signal quality, orientation, uptime. Returns compact summary with dish ID, hardware/software version, state, ping drop rate, latency, throughput, SNR, and antenna orientation. |
| starlink_alertsA | Get active dish alerts with human-readable descriptions. Checks 22 alert flags covering hardware (motors, thermal), connectivity (ethernet speed, signal), environment (water, obstruction), and policy (roaming, movement). Only active alerts are shown. |
| starlink_obstructionA | Get obstruction data: fraction obstructed, 12-wedge directional map, and timing. Shows overall obstruction percentage, whether currently obstructed, average obstruction duration and interval, and per-wedge fractions (12 directions around the dish). |
| starlink_historyA | Get recent throughput/latency/power history as statistical summary (min/avg/max). Returns aggregated stats over the requested sample window — much more token-efficient than raw per-second data. Covers ping drop rate, latency, download/upload throughput, power consumption, and SNR. |
| starlink_locationA | Get dish GPS location (latitude, longitude, altitude). Requires opt-in: Starlink app → Settings → Advanced → Debug Data. Returns 'unavailable' if GPS sharing is not enabled. |
| starlink_diagnosticsA | Get hardware diagnostics: firmware, GPS status, active alert count. Useful for troubleshooting — shows hardware version, software version, dish state with description, uptime, GPS satellite count, and total active alerts. |
| starlink_rebootA | Reboot the Starlink dish. Requires STARLINK_WRITE_ENABLED=true AND confirm=true. The dish will lose connectivity for 2-5 minutes during restart. Use this to recover from stuck states or apply pending firmware updates. |
| starlink_stowA | Stow the dish (point face-down for storage or transport). Requires STARLINK_WRITE_ENABLED=true AND confirm=true. The dish will lose connectivity while stowed. Use starlink_unstow to resume. |
| starlink_unstowA | Unstow the dish (resume normal satellite tracking). Requires STARLINK_WRITE_ENABLED=true AND confirm=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.