GitChanger MCP Server
Related Servers
Alternatives to GitChanger MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Git repositories via MCP, supporting status checks, diffs, staging, commits, branch management, and log queries.12MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered GitHub interactions including repository analysis, code search, PR reviews, and more through the MCP protocol.4MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.10130 npmISC
- AlicenseAqualityBmaintenanceEnables AI assistants and MCP hosts to inspect GitHub repositories, pull requests, issues, and activity, and to create issues through schema-validated tools, resources, and prompts, with write actions gated by host or CLI confirmation.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to drive role-aware Git collaboration through nine MCP tools, including starting tasks, staging/committing/pushing changes, submitting pull requests with GitHub-native auto-merge, checking status, syncing, and listing team rosters.MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct operations (add/delete/switch/scan/test_ssh vs. MCP token set/get/remove/sync/test). The main potential confusion is gitchanger_status vs gitchanger_mcp_status and gitchanger_list, which all report state, but descriptions make the split (identity/remote vs. token status vs. profile inventory) reasonably clear.
All tools use a consistent gitchanger_ prefix with snake_case verb/noun suffixes, and the MCP subgroup cleanly nests as gitchanger_mcp_*. No mixed camelCase or inconsistent verb styles.
14 tools is well within a reasonable range and each maps to a concrete operation across two coherent sub-domains (profile lifecycle and MCP token lifecycle). No obvious filler tools.
Profile CRUD is largely covered (add, delete, list, switch, set_default, status) plus SSH testing/scanning and full MCP token management (set/get/remove/sync/status/test). The notable gap is an update/edit operation for an existing profile's fields (e.g., changing name/email/SSH key without deleting and re-adding).