contribos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token needed for find, claim/brief from an issue URL, review, and record. | |
| CONTRIBOS_LLM | No | Optional AI summaries provider. Set to 'anthropic' or 'openai'. | |
| OPENAI_API_KEY | No | API key for OpenAI, used when CONTRIBOS_LLM=openai. | |
| CONTRIBOS_CACHE | No | Cache directory for clones and indexes. Defaults to ~/.cache/contribos. | |
| CONTRIBOS_MODEL | No | Optional model name for AI summaries. | |
| ANTHROPIC_API_KEY | No | API key for Anthropic, used when CONTRIBOS_LLM=anthropic. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| contribos_policyA | What a GitHub repository expects from outside contributors: AI policy, vouch/trust gates, claim-first norms, tests, changelog, sign-off, activity. Every finding cites file:line. Call this before starting work on any repo. |
| contribos_briefC | Evidence-backed contribution brief for an issue: files to read with reasons, similar past PRs, related tests, look-alike files to avoid, house rules and likely review questions. |
| contribos_setupC | Exact steps to set up and test a repository, taken from its CI and contributing docs. |
| contribos_diagnoseB | Explain a failed install or test run: missing dependency, wrong version, service not running, missing env var, flaky test, or a real test failure. |
| contribos_checkB | Pre-submit review of the local branch against the repo's rules and history: scope versus similar past changes, tests, changelog, sign-off, debug leftovers, AI policy, and whether the contributor's own explanation covers the change, AI-disclosure trailers, competing PRs, and (with verify_test) whether the test fails without the fix. Do not write the explanation for the user. |
| contribos_reviewA | Review coach for an open PR: classifies each reviewer comment, shows the code it points at, drafts replies, and lists comments still waiting on the author. |
| contribos_claimB | Draft the short proposal a contributor posts on an issue before coding (and a vouch introduction where the repo needs one). The human rewrites and posts it; never post it. |
| contribos_toneB | Check text the human is about to post for machine-written tells, length, and a clear question. Points at problems; the human rewrites. |
| contribos_findC | Find open issues where a newcomer is actually welcome, with takeability evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct stage of the contribution workflow (find, policy, brief, setup, diagnose, claim, tone, check, review). Overlaps like check-vs-review and claim-vs-tone are resolved by the descriptions, which clearly bound one to pre-submit local work and the other to open PRs, and one to drafting versus checking text.
Every tool follows the identical contribos_verb pattern with a single lowercase word (policy, brief, setup, diagnose, check, review, claim, tone, find). No deviations in casing or verb style.
Nine tools is well within the ideal 3-15 range and each maps to a discrete workflow step with no filler. The count feels deliberately scoped to the contribution lifecycle rather than padded.
The surface covers discovery, repo-policy intake, briefing, setup, diagnostics, claiming, tone, pre-submit review, and PR review commentary. Deliberately omits automated posting (human stays in the loop), leaving only minor gaps such as a way to locate repos or matching to review history.