PluginBench
MCP Server
Active

PixInsight Connector MCP Server

io.github.mxcoppell/pixinsight-connector

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the PixInsight Connector MCP server?

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

How to install PixInsight Connector

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • 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.

~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "pixinsight-connector": {
      "command": "npx",
      "args": [
        "-y",
        "pixinsight-connector"
      ],
      "env": {
        "PIXINSIGHT_BIN": "<YOUR_PIXINSIGHT_BIN>",
        "PIXINSIGHT_DIR": "<YOUR_PIXINSIGHT_DIR>",
        "PIXINSIGHT_CONNECTOR_PACKS": "<YOUR_PIXINSIGHT_CONNECTOR_PACKS>",
        "PIXINSIGHT_CONNECTOR_AUTOSTART": "<YOUR_PIXINSIGHT_CONNECTOR_AUTOSTART>",
        "PIXINSIGHT_CONNECTOR_WORKSPACE": "<YOUR_PIXINSIGHT_CONNECTOR_WORKSPACE>",
        "PIXINSIGHT_CONNECTOR_STATE": "<YOUR_PIXINSIGHT_CONNECTOR_STATE>",
        "PIXINSIGHT_CONNECTOR_LOG": "<YOUR_PIXINSIGHT_CONNECTOR_LOG>"
      }
    }
  }
}

Related MCP servers

Spec-driven dev workflow MCP with orchestration, memory, code graph analysis, and quality gates.

35
TypeScript
MIT
View repository →

AI tech lead for coding agents with validation and impact analysis

7
TypeScript
MIT
View repository →

Modular MCP server for dynamic prompt generation and software development analysis tools

4
TypeScript
MIT
View repository →

MCP server for AI assistants: read, write, edit, and manage files securely on local filesystem.

Current weather and hourly forecasts for any place name, via the free Open-Meteo API. No API key.

0
Python
MIT
View repository →

Decentralized AI inference on Base: OpenAI-compatible chat via community GPUs, paid in MYAI

0
Python
View repository →