telescopius-mcp
Related Servers
Alternatives to telescopius-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceThis MCP server lets AI clients inspect N.I.N.A. equipment and telemetry, write and persist observation plans, and load, run, and tear down imaging sequences. It also supports hardware actions like parking, homing, and warming the camera for complete astrophotography sessions.141MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP hosts to control ZWO Seestar telescopes over ASCOM Alpaca, including pointing, imaging, and downloading frames. It also provides a companion astro-mcp server for stacking and processing captured frames.5 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps the NASA Space-Track API to provide tools for TLE lookup, conjunction query, and satellite catalog search.-
- AlicenseNot gradedqualityCmaintenanceMCP server for the INDIGO astronomy automation protocol, enabling AI agents to control telescopes, cameras, focusers, filter wheels, domes, and other observatory equipment through natural language.MIT
- AlicenseAqualityBmaintenanceA local, open-source MCP server that wraps astronomy data services (SIMBAD, JPL Horizons, VizieR, etc.) behind a conversational interface, enabling AI assistants to answer astronomy questions with real, typed, and provenance-tracked data.13MIT
- 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
TDQS
Scored across 13 tools
Most tools target clearly distinct resources and actions (sky_times, weather_forecast, target_info, show_framing/close_framing), and the two-list pattern (my_observing_lists vs observing_list) is well differentiated. The main ambiguity is between astro_events (full computed calendar) and event_highlights (curated upcoming events with visibility flags), which an agent could easily conflate, and tonight_highlights vs search_targets partially overlap in purpose.
All names are clean snake_case with a coherent convention (my_ prefix for account resources, noun-phrase domain names, verb_noun for actions). The only deviation is that a few tools are verb-first (search_targets, show_framing, close_framing) while most are noun phrases, which is minor and still readable.
13 tools is well within the ideal range and each earns its place across distinct functional areas: time, targets, framing, events, weather, lists, equipment, and news. No redundancy or bloat.
The surface covers the observing workflow well: sky timing, target discovery/inspection, framing, events, weather, saved lists, gear, and news. The notable gap is that the observing-list tools are read-only (no way to add, remove, or create lists/targets), and equipment/news are read-only, but these are minor for a largely informational server.