Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Operate PixInsight from any MCP agent. Community project, not affiliated with Pleiades Astrophoto
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PIXINSIGHT_BIN, PIXINSIGHT_DIR, PIXINSIGHT_CONNECTOR_PACKS, PIXINSIGHT_CONNECTOR_AUTOSTART, PIXINSIGHT_CONNECTOR_WORKSPACE, PIXINSIGHT_CONNECTOR_STATE, PIXINSIGHT_CONNECTOR_LOGYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pixinsight-connector": {
"command": "npx",
"args": [
"-y",
"pixinsight-connector"
],
"env": {
"PIXINSIGHT_BIN": "your-value",
"PIXINSIGHT_DIR": "your-value",
"PIXINSIGHT_CONNECTOR_PACKS": "your-value",
"PIXINSIGHT_CONNECTOR_AUTOSTART": "your-value",
"PIXINSIGHT_CONNECTOR_WORKSPACE": "your-value",
"PIXINSIGHT_CONNECTOR_STATE": "your-value",
"PIXINSIGHT_CONNECTOR_LOG": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pixinsight-connector --env PIXINSIGHT_BIN=your-value --env PIXINSIGHT_DIR=your-value --env PIXINSIGHT_CONNECTOR_PACKS=your-value --env PIXINSIGHT_CONNECTOR_AUTOSTART=your-value --env PIXINSIGHT_CONNECTOR_WORKSPACE=your-value --env PIXINSIGHT_CONNECTOR_STATE=your-value --env PIXINSIGHT_CONNECTOR_LOG=your-value -- npx -y pixinsight-connectorFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pixinsight-connector": {
"command": "npx",
"args": [
"-y",
"pixinsight-connector"
],
"env": {
"PIXINSIGHT_BIN": "your-value",
"PIXINSIGHT_DIR": "your-value",
"PIXINSIGHT_CONNECTOR_PACKS": "your-value",
"PIXINSIGHT_CONNECTOR_AUTOSTART": "your-value",
"PIXINSIGHT_CONNECTOR_WORKSPACE": "your-value",
"PIXINSIGHT_CONNECTOR_STATE": "your-value",
"PIXINSIGHT_CONNECTOR_LOG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pixinsight-connector": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pixinsight-connector"
],
"env": {
"PIXINSIGHT_BIN": "your-value",
"PIXINSIGHT_DIR": "your-value",
"PIXINSIGHT_CONNECTOR_PACKS": "your-value",
"PIXINSIGHT_CONNECTOR_AUTOSTART": "your-value",
"PIXINSIGHT_CONNECTOR_WORKSPACE": "your-value",
"PIXINSIGHT_CONNECTOR_STATE": "your-value",
"PIXINSIGHT_CONNECTOR_LOG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PIXINSIGHT_BIN envPIXINSIGHT_DIR envPIXINSIGHT_CONNECTOR_PACKS envPIXINSIGHT_CONNECTOR_AUTOSTART envPIXINSIGHT_CONNECTOR_WORKSPACE envPIXINSIGHT_CONNECTOR_STATE envPIXINSIGHT_CONNECTOR_LOG envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account mxcoppell, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.5.2) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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. New here? Start with the [Quick start](QUICKSTART.md).
Community project, not affiliated with or endorsed by Pleiades Astrophoto. PixInsight® is a registered
trademark of Pleiades Astrophoto S.L.
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(" The knowledge · yours your skills: order, values, quality gates kept in your own repositories"):::know Harness(" Any MCP agent harness Claude Code · Codex · Cursor · Gemini CLI · …"):::harness Tools(" The toolbox · this connector ~80 PixInsight operations as MCP tools measurements return numbers, never verdicts"):::tool Bridge(" File bridge + watcher script starts PixInsight on the first call"):::tool PI(["PixInsight 1.9.5+"]):::app You --> Harness Skills -. guides .-> Harness Harness -- MCP tool calls --> Tools Tools --> Bridge Bridge <--> PI linkStyle default stroke:#8b949e,stroke-width:1.5px
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). From pixinsight-mcp 1.x: point your pixinsight entry at pixinsight-connector (not a second server) and npm uninstall -g pixinsight-mcp.
The tools work in a target folder: the one set_workspace names, else PIXINSIGHT_CONNECTOR_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.
PIXINSIGHT_CONNECTOR_PACKS. A pack is arbitrary code running with your privileges; only packs you configure load. See CONTRIBUTING.md.A PixInsight capability with no tool yet is one module in src/tools/, no registry: CONTRIBUTING.md. Humans and agents are both welcome; npm test needs no PixInsight.
macOS, Windows and Linux are all first-class, for running this connector and for developing it. A change that works on one OS and breaks another is a bug, not a limitation.
ps, grep, awk, wc, df or && in src/ or in npm scripts. OS-specific behaviour goes behind src/platform.mjs (paths) or src/process-probe.mjs (process inspection), one implementation per OS.path.join. Use forward slashes only when handing a path to PixInsight, which accepts them everywhere.PIXINSIGHT_BIN for the executable, PIXINSIGHT_DIR for the install root.Tests need no PixInsight and no astronomy software, so you can develop on any of the three.
Run pixinsight-connector doctor first. Common symptoms and fixes: docs/troubleshooting.md.
This project began as aescaffre/pixinsight-mcp by Alain Escaffre; parts of the original file bridge and watcher script remain. MIT licensed: see LICENSE.