PixInsight Connector MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    return fs.readFileSync(file, 'utf8');

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execFile(cmd, args, { timeout: 15000, windowsHide: true }, (error, stdout) => {

  return path.join(stateDir, 'watcher', version, path.basename(bridgeDir), 'watcher.js');

   return eval(__mcpCode);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add pixinsight-connector -- npx -y pixinsight-connector

{
  "mcpServers": {
    "pixinsight-connector": {
      "command": "npx",
      "args": [
        "-y",
        "pixinsight-connector"
      ]
    }
  }
}

[mcp_servers.pixinsight-connector]
command = "npx"
args = ["-y", "pixinsight-connector"]

{
  "mcpServers": {
    "pixinsight-connector": {
      "command": "npx",
      "args": [
        "-y",
        "pixinsight-connector"
      ]
    }
  }
}

{
  "servers": {
    "pixinsight-connector": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "pixinsight-connector"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: 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, <target>/agentic), PIXINSIGHT_CONNECTOR_LOG (0 turns off the per-session call logs in <target>/agentic/logs).