Skip to main content
Glama

Related Servers

Alternatives to dda-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that integrates with Siril astronomical image processing software to process Seestar telescope images, offering tools for binary detection, version checking, mosaic processing, and project analysis.
      7
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      13
      MIT

    TDQS

    B3.4/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools clearly specify the device type and action (e.g., alpaca_telescope_slew, open_roof). However, a few pairs like get_mount_sensors vs. get_mount_sensor_status and alpaca_switch_set vs. alpaca_switch_set_value could cause misselection.

    Naming Consistency4/5

    Native device tools use verb_noun (open_roof, get_device_status), while Alpaca tools follow alpaca_<device>_<action> consistently. The dual scheme is predictable, though alpaca_device_connect slightly deviates from the standard pattern.

    Tool Count2/5

    At 43 tools, the server far exceeds the 25-tool threshold for 'too many'. Many tools are simple status or control operations per device that could be consolidated into generic get_status or set_command functions.

    Completeness4/5

    The set covers discovery, connection, status, and control for all major device types (telescope, focuser, dome, camera, etc.). Minor gaps exist, such as no set_device_settings for native devices and no image retrieval for camera, but core workflows are represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues