Skip to main content
Glama
anarcoiris

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nina-mcp

No user-submitted related servers found.

    Related Servers

    • Nina Advanced API MCP

      PaDev1
      A
      license
      Not graded
      quality
      B
      maintenance
      A protocol server enabling AI agents to control astrophotography equipment through the N.I.N.A. (Nighttime Imaging 'N' Astronomy) software, allowing for natural language command processing of cameras, mounts, focusers, and other astronomy equipment.
      12
      MIT

    • pixinsight

      mxcoppell
      A
      license
      A
      quality
      A
      maintenance
      Enables any AI agent to operate PixInsight through MCP tools for image processing, measurements, and session control, with extensible runtime tool packs and skills.
      91
      301 npm
      2
      MIT

    • pixinsight-mcp

      iftahs
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to fully control PixInsight for astrophotography workflows, including calibration matching, WBPP stacking, blink review, and post-processing with visual previews.
      92
      MIT

    • pixinsight-mcp

      mxcoppell
      A
      license
      B
      quality
      A
      maintenance
      Enables any MCP-compatible AI agent to directly operate PixInsight through about 80 tools for opening and editing images, running processes, PixelMath, astrometry, and channel operations.
      78
      1
      MIT
    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

    A3.7/5.0

    Scored across 66 tools

    Disambiguation5/5

    Each tool targets a specific action on a distinct subsystem (camera, mount, sequence, etc.), with clear and unique purposes. Even within the same subsystem, tools like nina_camera_capture and nina_camera_abort_exposure are easily distinguishable.

    Naming Consistency5/5

    All tools follow a consistent nina_<subsystem>_<action> naming pattern (e.g., nina_camera_capture, nina_mount_slew). No mixing of conventions or unclear verb choices.

    Tool Count4/5

    At 66 tools, the count is high but appropriate for the extensive domain covering multiple equipment categories, sequence management, and a database interface. Each tool serves a distinct purpose, and no single subsystem has an excessive number.

    Completeness4/5

    The tool surface covers core operations for all major subsystems (connect/disconnect, control, info) and includes advanced features like sequence editing and target scheduler database access. A few minor gaps exist (e.g., no sequence creation from scratch), but overall coverage is strong.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources