oss-autopilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dailyA | Run daily PR monitoring check. Fetches all open PRs, enriches with CI status, reviews, and conflicts, then returns a prioritized summary. |
| statusA | Show current PR tracking status including open PRs, shelved PRs, and dismissed issues. |
| searchA | Search GitHub for beginner-friendly open-source issues to contribute to. Returns issues matching configured languages and interests. |
| vetA | Analyze a GitHub issue to determine if it is a good candidate for contribution. Checks for clarity, scope, existing assignees, and staleness. |
| trackA | Start tracking a pull request. Adds the PR to your monitored list so it appears in daily checks and status reports. |
| untrackA | Stop tracking a pull request. Removes the PR from your monitored list. |
| readA | Mark PR notifications as read. Requires either prUrl or all to be specified. |
| commentsA | Fetch and display comments on a pull request, including review comments and issue comments. |
| postC | Post a comment on a GitHub issue or pull request. |
| claimA | Claim a GitHub issue by posting a comment expressing intent to work on it. |
| configA | Get or set OSS Autopilot configuration values. With no args, shows all config. With key and value, sets the value. |
| initA | Initialize OSS Autopilot with a GitHub username. Creates the state file and sets up initial configuration. |
| setupB | Run OSS Autopilot setup to configure preferences like languages, interests, and contribution goals. |
| check-setupA | Check whether OSS Autopilot is properly set up and configured. Returns setup status and any missing configuration. |
| startupB | Run startup checks including GitHub auth verification, state file validation, and configuration status. |
| shelveA | Shelve a PR to temporarily hide it from daily checks and status reports without untracking it. |
| unshelveA | Unshelve a previously shelved PR, returning it to active monitoring. |
| dismissA | Dismiss a GitHub issue so it no longer appears in notifications. |
| undismissA | Undismiss a previously dismissed issue, re-enabling notifications. |
| moveA | Move a PR between states: attention (need attention), waiting (waiting on maintainer), shelved (hidden), or auto (reset to computed status). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage | Get a prioritized list of PRs needing attention with recommended actions |
| respond-to-pr | Get context for a PR to help draft a response to maintainer feedback |
| find-issues | Search for good issues to contribute to, ranked by viability |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | Current PR tracking status including open PRs, shelved PRs, and dismissed issues. Uses cached local state only (no GitHub fetch). |
| config | Current OSS Autopilot configuration including languages, interests, contribution goals, and preferences. |
| active-prs | All open pull requests from the last daily digest, including CI status, review state, and priority information. |
| shelved-prs | Pull requests that have been manually shelved, temporarily hidden from daily checks and status reports. |
TDQS
Scored across 20 tools
Most tools are distinct, but several clusters overlap: init/setup/config/check-setup/startup all concern configuration, and move overlaps with shelve/unshelve by supporting a shelved state. Descriptions clarify intent, but an agent could easily select the wrong tool in these areas.
The set uses a consistent lowercase command style with clear un- reversals (untrack, unshelve, undismiss). A few names are nouns or adjectives (status, comments, daily, startup) and check-setup is hyphenated, but the overall pattern is readable and predictable.
At 20 tools, the server is on the heavy side for its scope. The count is justifiable given PR tracking, issue triage, state management, and setup clusters, but some tools (check-setup/startup, shelve/unshelve vs move) could be consolidated.
The core workflow is covered: discover issues, vet them, claim/comment, track PRs, run daily checks, and manage state via shelve/dismiss/move. Minor gaps exist such as no explicit reset/uninitialize and no dedicated single-PR detail fetch, but agents can work around these.