原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Oss Autopilot

作者:costajohnt版本 5.11.0i★ –i在你的电脑上运行
注册名称io.github.costajohnt/oss-autopilot

安装

概览

作者提供的说明(英文原文)

Open source contribution manager with PR tracking, issue discovery, and CI diagnosis

PopNx MCP 的三大支柱

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

它能帮你做什么

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

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他
  • 你需要填写:GITHUB_TOKEN

安装

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

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

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

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

{
  "mcpServers": {
    "oss-autopilot": {
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add oss-autopilot --env GITHUB_TOKEN=your-value -- npx -y @oss-autopilot/mcp

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

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "oss-autopilot": {
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "oss-autopilot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

  • GITHUB_TOKEN 机密 env
    GitHub personal access token or token from `gh auth token`

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

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 costajohnt 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

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

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

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

常见问题

Oss Autopilot 安全吗?

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

它需要哪些密钥或代码?

你需要填写:GITHUB_TOKEN

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

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

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(5.11.0)于6天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, AikenDewit

替代选择

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

如何看卡片:↓ 每周下载量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

AikenDewit

Read, add and schedule your AikenDewit tasks and today's top three from ChatGPT or Claude.

作者:aikendewit.com起步阶段今天更新

在云端运行✓ aikendewit.com

作者的 README

打开 README

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

@oss-autopilot/mcp

MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools for any MCP-compatible client.

What It Provides

FeatureCountDescription
Tools35daily, status, search, features, vet, vet-list, verify-issue, track, compliance-score, repo-vet, strategy, eval, comments, post, claim, config, init, setup, check-setup, startup, dismiss, undismiss, work-claim, work-finish, work-release, work-list, move, state-show, state-sync, state-unlink, guidelines-list, guidelines-get, guidelines-store, guidelines-reset, guidelines-fetch-corpus
Resources6oss://status, oss://config, oss://prs, oss://prs/shelved, oss://pr/{owner}/{repo}/{number}, oss://repo/{owner}/{repo}/guidelines
Prompts4triage (PR prioritization), respond-to-pr (draft response), find-issues (discover issues), extract-learnings (distill per-repo guidance from past PR feedback)

Supports stdio (default) and Streamable HTTP transports.

Prerequisites

  • Node.js 22+
  • GitHub CLI authenticated (gh auth login)

Quick Start

# 1. Add the server to your MCP client (see config examples below)

2. From your MCP client, call the init tool once with your GitHub username

(this writes ~/.oss-autopilot/state.json).

3. Use the other tools — e.g. daily to check your PRs, search to find issues.

Client Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{

"mcpServers": { "oss-autopilot": { "command": "npx", "args": ["@oss-autopilot/mcp@latest"] } } }

Cursor

Add to .cursor/mcp.json in your project or global config:

{

"mcpServers": { "oss-autopilot": { "command": "npx", "args": ["@oss-autopilot/mcp@latest"] } } }

Codex CLI
codex mcp add oss -- npx @oss-autopilot/mcp@latest
Windsurf

Add to your Windsurf MCP config:

{

"mcpServers": { "oss-autopilot": { "command": "npx", "args": ["@oss-autopilot/mcp@latest"] } } }

Streamable HTTP (any client)

Run the server in HTTP mode instead of stdio:

npx @oss-autopilot/mcp@latest --http --port 3001

The server listens at http://127.0.0.1:3001/mcp and accepts POST requests.

Authentication

HTTP mode requires a bearer token on every request (stdio mode does not — it inherits the parent process identity). On first --http startup, the server generates a random 32-byte token and writes it to ~/.oss-autopilot/mcp.token with 0600 permissions. The path and "newly generated" marker are logged to stderr at startup.

Every HTTP client must send:

Authorization: Bearer <contents of ~/.oss-autopilot/mcp.token>

Requests without a valid Authorization header return 401. The Bearer scheme is case-insensitive per RFC 7235; the token value itself is compared byte-for-byte in constant time. Requests with a non-loopback Host header return 403 (DNS-rebinding defense). Requests must declare a numeric Content-Length ≤ 1 MiB — missing, non-numeric, or oversize Content-Length values return 413.

The token persists across restarts. To rotate, delete the file and restart — a new token will be generated. To relocate the token (e.g. for multi-user or CI setups), set OSS_AUTOPILOT_MCP_TOKEN_PATH to the desired absolute path before starting the server.

Tools Reference

ToolDescriptionRead-only
dailyRun daily PR monitoring check with prioritized summaryNo
statusShow current PR tracking statusYes
searchSearch GitHub for contributable issuesYes
featuresFind feature-scoped opportunities in repos with 3+ merged PRs (relationship-anchored)Yes
vetAnalyze an issue for contribution suitability; records the vet-time prediction and issue traits (labels, author association, competing PRs, first PR in the repo) for calibrationNo
verify-issueDeterministically verify issue state and linked-PR claims before vetting; also returns the issue author, author association and comment countYes
vet-listRe-vet all available issues in the curated issue listNo
trackInspect a PR: read-only metadata lookup (nothing is tracked or persisted)Yes
compliance-scoreScore a PR against opensource.guide best practices (#1245)Yes
repo-vetCompute the repo health rubric (1–10 + verdict) for owner/repo (#1271)Yes
strategyOn-demand contribution strategy snapshot via computeStrategy() (#1243)Yes
evalCalibration and outcome report from the outcome ledger (#1825)Yes
commentsFetch and display PR commentsYes
postPost a comment on an issue or PRNo
claimClaim an issue by posting a commentNo
configGet or set configuration valuesNo
initInitialize with a GitHub usernameNo
setupConfigure preferences (languages, interests)No
check-setupCheck if setup is completeYes
startupRun startup checks (auth, state, config)No
dismissDismiss an issue from notificationsNo
undismissRe-enable notifications for a dismissed issueNo
work-claimClaim an issue (implementation, while a fix is built in the background) or a PR (pr, while a session works it) so other sessions and machines see it; a claim another session holds needs takeover (#1856, #1852)No
work-finishMark an implementation claim finished: its branch is ready to collect for a week (session refuses a claim held elsewhere)No
work-releaseDrop the claim on a URL, or every claim a session holdsNo
work-listList live work claims across sessions and machinesYes
moveMove a PR between states (attention, waiting, shelved, auto)No
state-showShow current state persistence mode (local or Gist) and sync statusYes
state-syncForce push current state to the backing GistNo
state-unlinkDisconnect from Gist persistence and switch to local-only modeNo
guidelines-listList repos that have stored guidelines (always empty in local mode)Yes
guidelines-getRead per-repo learning guidelines extracted from past PR feedbackYes
guidelines-storePersist per-repo guidelines (8 KB cap; requires Gist mode)No
guidelines-resetTombstone the guidelines file for a repoNo
guidelines-fetch-corpusFetch raw PR comment bundles for the host's extract-learnings prompt to consumeNo

Resources Reference

Resource URIDescription
oss://statusPR tracking status (cached local state)
oss://configCurrent configuration
oss://prsActive open PRs from last daily digest
oss://prs/shelvedShelved PRs
oss://pr/{owner}/{repo}/{number}Detail for a specific PR
oss://repo/{owner}/{repo}/guidelinesPer-repo learning guidelines (markdown)

Prompts Reference

PromptArgsDescription
triagenoneFetches daily digest and builds a prioritized triage list
respond-to-prprUrlFetches PR comments and context for drafting a response
find-issuesmaxResults?Searches for issues ranked by viability score
extract-learningsrepo, corpus, existingGuidelines?Distills durable per-repo guidance from raw PR comment bundles (#867)

Multiple Machines

With Gist persistence, every client that runs oss-autopilot (the plugin on each machine, and every MCP server process) reads and writes the same state. Since core 3.35.0, a client keeps state fields it does not recognise instead of dropping them, and warns when the state was written by a different release. Clients on older releases still drop newer fields when they save, so update every machine after a release and restart running MCP servers, which keep the version they started with.

Programmatic Usage

The server can also be imported and used as a library:

import { createServer } from '@oss-autopilot/mcp';

const server = createServer(); // Connect to your own transport

More Information

See the main repository README for the full documentation, including the Claude Code plugin, CLI usage, dashboard, and contributing guide.

License

MIT

问 PopNx