junai Pipeline MCP

Name: junai Pipeline MCP
Author: saajunaid

作者：saajunaid版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.saajunaid/junai-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 45/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PIPELINE_STATE_PATH, JUNAI_WORKSPACE_ROOT

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "junai": {
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "junai": {
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "junai": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "junai-mcp"
      ],
      "env": {
        "PIPELINE_STATE_PATH": "your-value",
        "JUNAI_WORKSPACE_ROOT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 saajunaid 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18594 个服务器的 0%
发布到注册中心的时间比此分类中其他 18594 个服务器的 2% 更新
基础检查结果等于或优于此分类中其他 18594 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

junai Pipeline MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于9个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Commonly

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

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

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

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

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Commonly

Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.

作者：Team-Commonly正在增长↓ 4908/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.