open-source-contribution-mcp-server
Related Servers
Alternatives to open-source-contribution-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.2 npmISC
- AlicenseAqualityDmaintenanceAn MCP server that scouts truly beginner-friendly open-source issues from GitHub, checking availability and summarizing them for AI consumption.132 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that enables autonomous code development by pulling GitHub issues, fixing them in a sandboxed environment, running tests, opening PRs, and promoting to production upon human approval.3AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- FlicenseNot gradedqualityCmaintenanceA custom MCP server that lets AI assistants interact with GitHub accounts, offering tools for repository creation, file viewing, code search, and issue management.-
- AlicenseNot gradedqualityCmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.5 npmMIT
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.