A
licenseNot graded
qualityD
maintenanceEnables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.
11 npm
Apache 2.0
SourceCraft MCP Server
by ramgml
Related Servers
Alternatives to SourceCraft MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage GitHub repositories, branches, issues, pull requests, releases, and actions through natural language.337 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub via natural language, supporting repository management, issue tracking, file commits, and more.ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GitHub repositories and automate workflows through natural language.-
- AlicenseAqualityBmaintenanceEnables AI assistants to perform Git workflows with semantic commit messages, pre-PR secret audits, conflict resolution, and release changelog generation.5MIT
- AlicenseBqualityCmaintenanceEnables compatible AI clients to open, inspect, edit, test, commit, and manage GitHub repositories through local STDIO or authenticated remote Streamable HTTP, including issues, pull requests, workflows, and repository creation.30MIT
TDQS
D1.5/5.0
Scored across 48 tools
Disambiguation2/5
There are duplicate tools (`_list_organization_repositories` and `list_organization_repositories`) and several similar lifecycle actions (`_create_release` vs `_publish_release`, `_update_pull_request` vs `_publish_pull_request`) that are hard to tell apart. Vague names like `_trigger_workflows` and `_get_cube_logs` further obscure their exact purpose relative to other CI tools.
Naming Consistency2/5
Most tools follow a snake_case verb_noun pattern, but the leading underscore prefix is applied inconsistently: some tools like `create_repository`, `list_branches`, and `get_file_tree` have no underscore. The duplicate `_list_organization_repositories` / `list_organization_repositories` pair and odd names like `_get_cube_logs` also break the naming pattern.
Tool Count2/5
48 tools is a very large surface for a source-management server, especially when several tools appear duplicative or could be consolidated (`_publish_release` vs `_discard_release`, `_trigger_workflows` vs `_get_workflow`). The scope spans users, orgs, repos, issues, PRs, releases, and CI, which feels heavy rather than focused.
Completeness3/5
Major workflows for repositories, issues, pull requests, releases, and CI are covered with CRUD/lifecycle actions in most areas. However, there are notable gaps for a source-management tool: no commit listing/inspection, no branch or tag creation/deletion, and no repository search or org member management beyond listing.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues