Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Oss Autopilot

by costajohntversion 5.11.0i★ –iRuns on your computer
Registry nameio.github.costajohnt/oss-autopilot

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

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

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
  • You need to fill in: GITHUB_TOKEN

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: GITHUB_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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": {
    "oss-autopilot": {
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add oss-autopilot --env GITHUB_TOKEN=your-value -- npx -y @oss-autopilot/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": {
    "oss-autopilot": {
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "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": {
    "oss-autopilot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@oss-autopilot/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "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

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

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 costajohnt, 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 18613 servers in this category
  • Published to the registry more recently than 87% of the other 18613 servers in this category
  • Basic checks equal to or better than 100% of the other 18613 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 Oss Autopilot 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?

You need to fill in: GITHUB_TOKEN

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 (5.11.0) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, DECIDE: Migration Discovery Risk Review

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

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

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.

@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

Ask PopNx