Oss Autopilot

What costajohnt/oss-autopilot MCP server does

The costajohnt/oss-autopilot MCP server helps contributors keep track of open GitHub pull requests across repositories. It retrieves open PRs and classifies them by conditions such as failed CI, requested changes, unanswered maintainer comments, merge conflicts, incomplete checklists, or work waiting on a maintainer.

It also supports finding new contribution opportunities. Search can match open issues against configured languages and labels, then evaluate whether an issue is claimed, linked to an existing pull request, suitable for outside contributions, and associated with responsive maintainers. Repositories that state they do not accept AI-assisted contributions are skipped.

For PRs requiring attention, an agent can inspect the discussion and diff, draft a response, diagnose a CI failure, or prepare a branch update. The system is designed around review before external side effects: comments and pushes are not sent until the user approves the specific action.

How it works

The MCP package runs through a standard command-based configuration using npx. Its underlying packages fetch GitHub data and provide the MCP client with tools, resources, and prompts.

A daily workflow retrieves and classifies open pull requests, presents the items needing attention first, and offers follow-up actions. Overnight mode can prepare a fix branch in a local Git worktree for CI failures, conflicts, or requested changes, run the project tests, and write a report under ~/.oss-autopilot/reports/. The next daily check can show that report for review.

The same underlying data is available through the standalone CLI and Claude Code plugin, although the specialized agents and slash commands belong to the plugin rather than the MCP server.

Setup and configuration

Before running the costajohnt/oss-autopilot MCP server, use Node.js 22 or newer and authenticate to GitHub. Authentication can come from a logged-in GitHub CLI installation or from GITHUB_TOKEN in the environment. Windows is untested; CI is documented for Ubuntu and macOS.

Initialize the tool with a GitHub username:

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

Then register the MCP server in the client configuration:

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

Using @latest installs new releases automatically. Pinning a package version is available when updates should be controlled manually. The initialization step stores the GitHub username used by the tool.

Tools and capabilities

• Review open GitHub pull requests across repositories.
• Classify PRs by review, CI, conflict, checklist, and response status.
• Search for issues using configured languages and labels.
• Evaluate issue and repository suitability for outside contributions.
• Diagnose CI failures and stale or conflicting branches.
• Draft replies to maintainer feedback.
• Prepare local fix branches and run project tests in overnight mode.
• Expose MCP tools, resources, and prompts to compatible clients.

Limitations and notes

The server depends on GitHub authentication and network access. Specialized Claude Code agents, slash commands, and the local dashboard are features of the plugin or broader project rather than capabilities specifically listed as MCP tools.

The server can prepare changes, but the documented workflow requires approval before pushing commits or posting comments. Overnight mode is not described as unattended publishing: it creates local work and a report for later review.