Oss Autopilot
Let your agent track open-source PRs, surface good-first issues, and explain failing CI from GitHub in one stdio MCP server.
Overview
OSS Autopilot is a Build-phase MCP server that manages open-source contributions with GitHub PR tracking, issue discovery, and CI diagnosis tools.
What is this MCP server?
- Open-source contribution manager: PR tracking, issue discovery, and CI diagnosis
- stdio npm package @oss-autopilot/mcp (v2.0.1) for local agent wiring
- Uses GITHUB_TOKEN from a PAT or `gh auth token`
- Repository: github.com/costajohnt/oss-autopilot (mcp-server subfolder)
- Fits maintainers and contributors who want agent-assisted triage without leaving the IDE
- Package @oss-autopilot/mcp version 2.0.1
- stdio transport via npm registry
- Requires GITHUB_TOKEN environment variable
Community signal: 9 GitHub stars.
What problem does it solve?
Contributing to OSS while building solo means losing hours jumping between PRs, issues, and cryptic CI logs without agent-native GitHub tools.
Who is it for?
Solo developers who regularly file or review PRs on GitHub and want Cursor or Claude Code to orchestrate issue pick-up and CI triage.
Skip if: Teams on GitLab-only workflows or builders who do not want to store a GitHub PAT for an MCP process.
What do I get? / Deliverables
With GITHUB_TOKEN configured and the MCP server running, your agent can query and act on contribution workflows from the same session as your code edits.
- Configured stdio MCP server linked to your GitHub identity
- Agent-accessible PR, issue, and CI diagnosis operations for chosen repositories
Recommended MCP Servers
Journey fit
OSS contribution work sits in the build phase when you are actively shipping fixes and integrations to external repos. GitHub-backed PR, issue, and CI tools are classic third-party integrations exposed via MCP to your coding agent.
How it compares
GitHub-focused contribution MCP, not a generic code-review SKILL or full CI replacement.
Common Questions / FAQ
Who is OSS Autopilot for?
Open-source contributors and indie maintainers who use AI coding agents and need structured GitHub PR, issue, and CI tooling.
When should I use OSS Autopilot?
Use it during active build cycles when you are hunting issues, pushing PRs, or debugging failed checks on repositories you contribute to.
How do I add OSS Autopilot to my agent?
Install/run @oss-autopilot/mcp via npm stdio in your MCP config and set GITHUB_TOKEN to a personal access token or output from `gh auth token`.