# costajohnt/oss-autopilot [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/costajohnt/oss-autopilot  
**GitHub Stars:** 14  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/costajohnt-oss-autopilot

## Description
Open source contribution manager with PR tracking across repos, issue discovery, CI failure diagnosis, and maintainer response drafting. Available as CLI, MCP server, and Claude Code plugin.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "oss-autopilot": {
    "command": "npx",
    "args": ["-y","@oss-autopilot/core"]
  }
}
```

## Documentation

## What costajohnt/oss-autopilot MCP server does

The costajohnt/oss-autopilot MCP server organizes recurring open source contribution work around GitHub pull requests and issues. It can monitor open PRs across repositories, identify maintainer feedback, help draft replies, analyze failed CI checks, and discover issues related to a contributor's history. The same functionality is available through the project's CLI and Claude Code plugin, while the MCP package makes it available to supported agent clients.

The server is intended for contributors who work across multiple projects and need a current view of review status, checks, conflicts, and follow-up actions. It keeps human approval in the loop: generated replies are drafts, and the project states that nothing is posted to GitHub without explicit approval.

## How it works

The MCP package uses the shared `@oss-autopilot/core` library, which connects to the GitHub API and manages contribution state. Each run fetches live data rather than relying on locally stored copies of pull requests. Retrieved PRs are enriched with CI results, review decisions, merge-conflict detection, maintainer comment classification, and checklist completion.

Core processing is implemented in TypeScript and includes deterministic PR status classification, CI failure categorization, state management, paginated requests, bounded concurrency, caching, and rate-limit retry behavior. The CLI and MCP layers use the same core behavior, so agents can consume structured command results instead of relying only on prompt-based analysis.

## Setup and configuration

Initialize the GitHub username once with the core package:

```bash
npx @oss-autopilot/core@latest init <your-github-username>
```

Then configure the MCP client to run the published package:

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

The README says the CLI uses the GitHub CLI authentication token automatically. The MCP server is documented for Cursor, Claude Desktop, Codex, and Windsurf. The repository also provides a Claude Code plugin installation path and a standalone dashboard command, but those are separate interfaces to the same project.

## Tools and capabilities

The costajohnt/oss-autopilot MCP server exposes 30 tools, six resources, and four prompts. Supported workflows include:

- Monitoring open pull requests across repositories.
- Finding issues matched to contribution history.
- Diagnosing CI failures using categories such as actionable, fork limitation, authentication gate, and infrastructure.
- Detecting maintainer feedback and preparing response drafts.
- Checking merge conflicts, review decisions, and contribution checklist status.
- Returning structured results through the shared core implementation.

The project also includes an interactive dashboard for PR management, charts, contribution statistics, and status overrides. Factual claims in drafted comments are checked against the relevant diff before being shown to the user.

## Limitations and notes

This project is centered on GitHub contribution workflows; the supplied material does not document support for other code-hosting services. GitHub data is fetched during each run, so operation depends on access to the GitHub API and valid local GitHub CLI authentication. A GitHub username must be initialized before using the MCP setup described in the README.

The server does not remove the need for review before external actions. Drafted maintainer responses require contributor approval, and the README specifically describes pre-commit review gates and protections against posting without explicit authorization. The repository is MIT licensed and publishes the MCP package as `@oss-autopilot/mcp`.

_Full upstream README: https://allmcps.com/mcp/costajohnt-oss-autopilot/readme_