Skip to main content
Glama
mxcoppell

pixinsight

by mxcoppell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to pixinsight

No user-submitted related servers found.

    Related Servers

    • 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

    • 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 Bridge

      priestjim
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with PixInsight's image processing capabilities through a local HTTP/SSE server, allowing listing processes, invoking them, viewing images, and more.
      MIT

    • PS-MCP-IMT

      Immersive-Media-Technologies
      F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets AI agents drive a running Adobe Photoshop from natural language — documents, layers, text, masks, selections, filters, adjustments, Smart Objects, artboards, generative tools and export — through a 9-tool facade backed by 134 operations. A dual ExtendScript/UXP transport keeps reads, saves and exports working even when Photoshop is modal, returning honest busy/timeout errors instead of silent hangs.
      66 npm
      2
      -
    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 91 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and detailed descriptions clarify boundaries between similar operations (e.g., run_pixelmath vs pixelmath_new_image, run_abe vs run_per_channel_abe). Minor overlap exists between generic runners (run_process, run_pjsr) and dedicated process wrappers, and save_preview/save_and_show_preview are explicitly aliased, but an agent can generally tell them apart.

    Naming Consistency4/5

    The vast majority of tools follow a snake_case verb_noun pattern (run_*, measure_*, list_*, get_*), with a few noun-first exceptions like catalog_stars, lrgb_combine, job_status, and workspace_info. The deviations are minor and still readable, so naming is mostly predictable.

    Tool Count2/5

    91 tools is far beyond the ideal 3–15 range and is excessive for effective agent selection, even for a broad image-processing suite. Many dedicated wrappers duplicate what the generic run_process or run_pjsr tools already cover, so the count is not well-scoped.

    Completeness5/5

    The server covers file handling, image lifecycle, many processing operations, measurement, job control, and workspace management. The generic run_process and run_pjsr/run_pjsr_file tools act as escape hatches for any missing PixInsight process, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources