junai Pipeline MCP

Name: junai Pipeline MCP
Author: saajunaid

by saajunaidversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.saajunaid/junai-mcp

Install

Overview

Description from the maker (original English)

Agentic pipeline orchestration MCP server for AI-driven development workflows.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 45/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: PIPELINE_STATE_PATH, JUNAI_WORKSPACE_ROOT

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "junai": {
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add junai --env PIPELINE_STATE_PATH=your-value --env JUNAI_WORKSPACE_ROOT=your-value -- uvx junai-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "junai": {
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "junai": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "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.

Values you fill in

PIPELINE_STATE_PATH env
Path to pipeline-state.json. Defaults to .github/pipeline-state.json relative to the workspace root (detected by searching upward from the current directory for a .github folder).
JUNAI_WORKSPACE_ROOT env
Explicit workspace root path override. Use if automatic detection (searching upward for .github) does not find the correct root.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account saajunaid, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18513 servers in this category
Published to the registry more recently than 2% of the other 18513 servers in this category
Basic checks equal to or better than 100% of the other 18513 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is junai Pipeline MCP safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Cape Winelands Visit Planner

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Cape Winelands Visit Planner

Cape Winelands wine farm finder and day-route planner

by aiagenttools.co.zaEarlyUpdated today

Runs in the cloud✓ aiagenttools.co.za

Install

README from the maker

Open the README

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.

caddis — a Claude Code harness

[Browse every command, skill, agent and hook -> saajunaid.github.io/caddis-plugin](https://saajunaid.github.io/caddis-plugin/) — the reference site, rebuilt on every publish.

caddis is a Claude Code harness — a plugin (plus a shared pool of skills, subagents, slash-commands, and hooks) that makes a single Claude Code session dramatically more capable and much harder to derail. It's *agent-agnostic*: the same pool is exported to other AI CLIs (Codex, Antigravity, Copilot), and CLAUDE.md↔AGENTS.md are mirrors so every agent reads the same conventions.

Before you start

You need	Why
Claude Code, installed and signed in	caddis is a plugin for it
Python 3.11+ on `PATH`	the hooks and the cross-review tool are Python
Git	several commands read repository state
(optional) an API key for DeepSeek or GLM	only for cross-vendor review and the OSS lanes

Honest about the platform: caddis is developed and used daily on Windows with PowerShell. The hooks are pure Python and cross-platform, and the skills, commands and agents are plain markdown that work anywhere — but some launchers ship as both .ps1 and .sh, the deployment skill is Windows-specific, and the publishing machinery (sync.ps1) is PowerShell-only. Nothing here is hostile to macOS or Linux; it is simply less travelled, so expect rough edges and please report them.

Your first five minutes

claude plugin marketplace add saajunaid/caddis-plugin

claude plugin install caddis@caddis

Then, in a Claude Code session, confirm it actually loaded:

/caddis:version

If that prints a version, you are installed. From there, the shortest path to seeing what caddis is *for*:

Try this	What it does
`/caddis:feature-plan add CSV export`	writes a phased, TDD-structured plan to `.caddis/plans/` — the durable spine the rest of the harness reads
`/caddis:implement`	executes that plan phase by phase, committing each, and stops only at a real boundary
`/caddis:cross-review`	has a different vendor's model review your diff, because a same-vendor reviewer shares your blind spots
`/caddis:handoff`	writes the resume doc, so the next session starts with zero re-discovery

Everything else is optional. If you only ever use feature-plan → implement → cross-review, you have most of the value.

This repository is the published marketplace mirror: it hosts the caddis and caddis-extras Claude Code plugins, the portable per-harness bundles under bundles/, and the shared pool. It is generated and pushed by the caddis authoring repo's exporter — issues are welcome here, but code changes land upstream and are synced in.

Install (Claude Code)

# 1. Register this repo as a plugin marketplace (once)

claude plugin marketplace add saajunaid/caddis-plugin

2. Install the core plugin (always-on, lean context)

claude plugin install caddis@caddis

3. (optional) Add the long-tail skill library — cloud/data/media/etc. Disabled by default,

so it costs zero always-on context until you enable it.

claude plugin install caddis-extras@caddis

Then, in any repo:

/caddis:setup-project-ai     # deploy the harness into the project

A normal working loop looks like:

/feature-plan      # (or /prd first) → writes .caddis/plans/<slug>.md, the durable spine

/implement # executes the plan phase-by-phase, TDD, commit per phase /ship # express lane: commit → push → CI (hotfixes); feature work: /ship-pr then /ship-merge /handoff # ALWAYS end a session with this — writes the resume doc

The one habit that matters most: end every session with `/handoff`. It writes .caddis/relay.md, which is re-injected automatically at the next session start — you resume with zero re-discovery instead of a cold, forgetful session.

See USERGUIDE.md for the full command/skill/hook reference and the mental models.

What you get

Slash-commands — /feature-plan, /prd, /implement, /tdd, /ship · /ship-pr · /ship-merge, /handoff, /kb, /digress · /resume, /cross-review, /usage-review, /mermaid-db · /excalidraw-db, /setup-project-ai, /migrate-dir.
Subagents — lean, own-context helpers: anchor (evidence-first verification), code-reviewer, preflight (plan-vs-codebase validation), tester, debug, codebase-audit, security-analyst, data-engineer, sql-expert, knowledge-transfer.
A four-layer memory model — session relay (relay.md), automatic Dream Memory (memory.jsonl), a per-repo knowledge base (.caddis/kb/ + DOC-MAP.md), and cross-repo memory.
Hooks & safety — a PreToolUse guard for secret/destructive writes, auto-lint on edit, and the SessionStart/Stop hooks behind relay + memory.
Tiered skills — the core dev set ships in caddis; the long tail (cloud, data, media, productivity) lives in caddis-extras, off by default.

Installing outside Claude Code (Codex, Antigravity, …)

The knowledge layer (skills + AGENTS.md conventions) works in any harness. Per-harness bundles are published under bundles/ and installed with caddis-init:

# from a checkout of this repo (the installer ships in plugin/scripts/)

python plugin/scripts/claudster_init.py --target codex --dest /path/to/project python plugin/scripts/claudster_init.py --target antigravity --dest /path/to/project

Safe by design: a sha256 manifest tracks what the installer wrote; re-runs update only unmodified files, and anything you edited locally is reported as a conflict, never overwritten.

Repo layout

Path	What it is
`.claude-plugin/marketplace.json`	The marketplace manifest (`caddis` + `caddis-extras`)
`plugin/`	The core `caddis` Claude Code plugin (agents, commands, hooks, core skills)
`plugin-extras/`	The `caddis-extras` skill library (disabled by default)
`bundles/`	Portable per-harness exports (codex, antigravity) for `caddis-init`
`.github/`	The shared pool: skills, agents, prompts, instructions, tools
`sync.ps1`, `export_runtime_resources.py`, `validate_pool.py`	The build/sync machinery

A note on names

caddis was previously published as claudster (and, before that, this repo hosted the junai Copilot pipeline — see the pre-1.2 entries in CHANGELOG.md). Repos set up under the old name have a .claudster/ artifact dir; everything reads both .caddis/ and .claudster/ and writes where the repo already lives, so nothing breaks. Run /caddis:migrate-dir when you want a repo converted. The ~/.claudster/ user scope (keys, install records) is permanent.

License

MIT. The published plugin bundles (caddis / caddis-extras) carry the same license in their manifests.

junai Pipeline MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Cape Winelands Visit Planner

README from the maker

caddis — a Claude Code harness

Before you start

Your first five minutes

Install (Claude Code)

2. Install the core plugin (always-on, lean context)

3. (optional) Add the long-tail skill library — cloud/data/media/etc. Disabled by default,

so it costs zero always-on context until you enable it.

What you get

Installing outside Claude Code (Codex, Antigravity, …)

Repo layout

A note on names

License