Skip to main content
Glama
Groupthink-dev

starlink-blade-mcp

by Groupthink-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to starlink-blade-mcp

No user-submitted related servers found.

    Related Servers

    • Astro Agent

      Aamish-001
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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

    • Samsung TV MCP Server

      andresgarcia0313
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      1
      MIT

    • Unoffical Polestar 2 MCP

      holger1411
      A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      1
      MIT

    • OBD MCP Server

      ayhammouda
      A
      license
      A
      quality
      B
      maintenance
      A local-first, read-only MCP server for vehicle diagnostics that exposes structured OBD-II tools for reading PIDs, DTCs, and ECU snapshots without raw protocol access.
      7
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources