open-source-contribution-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token with repo, workflow, and user:email scopes. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_skillsA | Get currently registered skills, proficiency levels, and scope preferences |
| set_user_skillsB | Set or overwrite user skill tags and scope preferences |
| add_user_skillsB | Dynamically add new skills or update existing skill proficiencies anytime |
| remove_user_skillA | Remove a specific skill tag from active profile |
| clear_user_skillsB | Reset all user skills and preferences |
| find_issuesB | Discover and rank open-source issues matching user skills across multiple sources |
| analyze_repo_contextA | Mandatory repo analysis: reads CONTRIBUTING guidelines, linter configs, test frameworks, and recent merged PRs |
| generate_code_fixB | Generate scoped, file-level diff fix for an issue adhering to target repo conventions |
| generate_unit_testsB | Generate matching unit tests for the proposed code fix |
| submit_pull_requestA | Submit approved pull request to target repository (Only runs when confirmed is set to true by human approval) |
| track_open_prsB | Track status of PRs (open, changes requested, approved, merged, closed) |
| get_review_feedbackA | Fetch maintainer review comments for a PR and generate follow-up fix instructions |
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 12 tools
Each tool has a clearly distinct purpose, with user skills tools covering separate CRUD operations (get, set, add, remove, clear) and the remaining tools targeting different workflow stages (issue discovery, repo analysis, PR tracking, code/test generation, submission, feedback). There is no meaningful overlap between any two tools, even within the skills family, as descriptions clarify the differences in behavior.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_user_skills, find_issues, generate_code_fix). The verbs and nouns are descriptive and align with the action, and there is no mixing of conventions or unusual naming styles.
With 12 tools, the server is well-scoped for its stated purpose of managing open-source contributions. Each tool covers a necessary step in the workflow, from profile management to submission and feedback, without redundancy or bloat.
The tool set covers the core workflow comprehensively: skills management, issue discovery, repository analysis, fix and test generation, PR submission, tracking, and review feedback. The main gap is the lack of a tool to update an existing PR with follow-up fixes after review feedback, leaving a potential dead end in the iterative contribution loop.