MCP.Market

PixInsight Connector MCP server

by mxcoppell·io.github.mxcoppell/pixinsight-connector·v2.5.2

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

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed PixInsight Connector yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PixInsight Connector tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How PixInsight Connector compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 73% of 4,460 AI and agents servers

Release history: 7 versions in the registry since 2026-09-24, latest 2026-10-29, typically one every 5 days.

Install PixInsight Connector in Claude Code, Cursor or VS Code

Runs npx -y pixinsight-connector on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pixinsight-connector -- npx -y pixinsight-connector
Add to Cursor

What the publisher says

From the PixInsight Connector repository's README, as published. We do not edit it. Read it on GitHub

PixInsight Connector

An MCP connector that lets any AI agent operate PixInsight: about 80 PixInsight operations as tools, for chat sessions and the skills that guide them.

Community project, not affiliated with or endorsed by Pleiades Astrophoto. PixInsight® is a registered

trademark of Pleiades Astrophoto S.L.

The principle: a toolbox, not a pipeline

The connector knows how to operate PixInsight, never what makes a good picture. No pipeline, no ordering, no recommended values, no verdicts: every tool takes the values that shape the image as inputs, and every measurement returns numbers. The knowledge (which tools, in what order, with which values, what counts as good enough) lives in skills: markdown in your own repositories, public or private.

%%{init: {'theme': 'base', 'flowchart': {'wrappingWidth': 400, 'curve': 'basis', 'padding': 18}, 'themeVariables': {'fontFamily': "-apple-system, BlinkMacSystemFont, 'Segoe UI', Inter, Helvetica, Arial, sans-serif", 'lineColor': '#94a3b8', 'textColor': '#334155', 'edgeLabelBackground': '#e2e8f0'}}}%%
flowchart TB
    classDef know fill:#0f766e,stroke:#115e59,color:#f0fdfa,stroke-width:1px,rx:12,ry:12
    classDef harness fill:#475569,stroke:#334155,color:#f8fafc,stroke-width:1px,rx:12,ry:12
    classDef tool fill:#1e293b,stroke:#64748b,color:#f8fafc,stroke-width:1px,rx:12,ry:12
    classDef app fill:#e2e8f0,stroke:#94a3b8,color:#0f172a,stroke-width:1px
    You(["You, in a chat session"]):::know
    Skills("<b>The knowledge · yours</b><br/>your skills: order, values, quality gates<br/>kept in your own repositories"):::know
    Harness("<b>Any MCP agent harness</b><br/>Claude Code · Codex · Cursor · Gemini CLI · …"):::harness
    Tools("<b>The toolbox · this connector</b><br/>~80 PixInsight operations as MCP tools<br/>measurements return numbers, never verdicts"):::tool
    Bridge("<b>File bridge + watcher script</b><br/>starts PixInsight on the first call"):::tool
    PI(["PixInsigh

Install

Needs Node 22+ and PixInsight 1.9.5+. The same three steps work whether you or your agent runs them.

1. Install the connector from npm:

npm install -g pixinsight-connector

2. Register it with your agent harness as the MCP server pixinsight. Claude Code:

claude mcp add -s user pixinsight -- pixinsight-connector

Any harness configured with an mcpServers JSON file (Cursor, Windsurf, Gemini CLI, Claude Desktop, Cline, Kiro):

{ "mcpServers": { "pixinsight": { "command": "pixinsight-connector" } } }

Codex, OpenCode, VS Code and Zed use other shapes; each one, and where its file lives: docs/setup.md.

3. Check the machine:

pixinsight-connector doctor

PixInsight and its watcher script start on the first tool call; there is nothing else to launch. Upgrade with npm install -g pixinsight-connector@latest. Without installing, register npx -y pixinsight-connector as the command instead (npx fetches it from npm, so the first start needs the network).

Where files go

The tools work in a target folder: the one setworkspace names, else PIXINSIGHTCONNECTOR_WORKSPACE, else the folder the harness started in. The connector writes only /agentic/ (scratch, the bridge, call logs) and /output/, never your home folder. Details and every environment variable: docs/setup.md.

Tools, packs and skills

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PixInsight Connector: common questions

Is PixInsight Connector MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the PixInsight Connector safety report
How do I install PixInsight Connector?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PixInsight Connector need an API key?
No secret keys are declared. It reads 7 settings from the environment.
Is PixInsight Connector maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v2.5.2.
What can I use instead of PixInsight Connector?
Servers from other publishers that do the same job: Decionis Commerce Gate MCP server.

Alternatives to PixInsight Connector

Same job from other publishers: the closest match first, then the best rated.

  • Decionis Commerce Gate MCP
    Commerce preflights, D365 authorization; opt-in agent writes require authorized backend connectors.
    A