PixInsight Connector MCP Server

Operate PixInsight from any MCP agent. Community project, not affiliated with Pleiades Astrophoto

Local serverstdio

What is the PixInsight Connector MCP Server?

PixInsight Connector is an MCP integration. Operate PixInsight from any MCP agent. Community project, not affiliated with Pleiades Astrophoto.

Packages and local setup

The published npm package is pixinsight-connector, version 2.5.0. Its declared MCP transport is stdio.

The package declares PIXINSIGHT_BIN: Path to the PixInsight executable. When unset, the default install location for the OS is used.; PIXINSIGHT_DIR: PixInsight install root, from which the executable and its resources are derived. When unset, the default install location for the OS is used.; PIXINSIGHT_CONNECTOR_PACKS: Comma-separated tool packs to load: pack directories and .mjs files (an npm package by the path to its folder). Empty: no packs.; PIXINSIGHT_CONNECTOR_AUTOSTART: 0 stops the connector from starting PixInsight when a tool call finds it not running.; PIXINSIGHT_CONNECTOR_WORKSPACE: The target folder the tools work in (session files in its agentic folder, results in its output folder). When unset, the folder the connector was started in; the set_workspace tool overrides both.; PIXINSIGHT_CONNECTOR_STATE: Where the connector's session files (scratch, bridge, logs) go, resolved against the target folder. When unset, /agentic.; PIXINSIGHT_CONNECTOR_LOG: 0 turns off the per-session call logs in /agentic/logs..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
PIXINSIGHT_BINPath to the PixInsight executable. When unset, the default install location for the OS is used.Optional
PIXINSIGHT_DIRPixInsight install root, from which the executable and its resources are derived. When unset, the default install location for the OS is used.Optional
PIXINSIGHT_CONNECTOR_PACKSComma-separated tool packs to load: pack directories and .mjs files (an npm package by the path to its folder). Empty: no packs.Optional
PIXINSIGHT_CONNECTOR_AUTOSTART0 stops the connector from starting PixInsight when a tool call finds it not running.Optional
PIXINSIGHT_CONNECTOR_WORKSPACEThe target folder the tools work in (session files in its agentic folder, results in its output folder). When unset, the folder the connector was started in; the set_workspace tool overrides both.Optional
PIXINSIGHT_CONNECTOR_STATEWhere the connector's session files (scratch, bridge, logs) go, resolved against the target folder. When unset, /agentic.Optional
PIXINSIGHT_CONNECTOR_LOG0 turns off the per-session call logs in /agentic/logs.Optional