Repository Manager
Related Servers
Alternatives to Repository Manager
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server for local git repositories that provides tools for code search, git history analysis, complexity metrics, test discovery, and dependency management.MIT
- AlicenseBqualityDmaintenanceMCP Server for Git operations, agent templates, and project utilities.953 npmMIT
- AlicenseCqualityBmaintenanceMCP server for interacting with GitLab API, supporting dynamic tool selection and enterprise-grade security.20810MIT
- AlicenseNot gradedqualityDmaintenanceA production-oriented MCP server for coding agents that enables multi-project management through secure file operations, Git integration, and safe command execution. It supports project discovery across multiple root directories and provides robust audit logging with both STDIO and HTTP transport options.2MIT
- AlicenseCqualityDmaintenanceA production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.27MIT
- AlicenseNot gradedqualityDmaintenanceA secure, git-aware MCP server for working with local repositories, enabling file management, shell commands, and full git operations within allowed directories.1GPL 3.0
TDQS
Scored across 120 tools
There is massive overlap across families: repository_manager_add_project vs rm_git_add, pull_project vs rm_git_pull, commit_project vs rm_git_commit, and many rm_gates_* tools share nearly identical descriptions. Several families (rm_lane, rm_merge_queue, rm_build, rm_worktree, rm_concepts, rm_remote_workers) repeat the same description for every action, so an agent cannot reliably infer which tool to use.
Names are snake_case throughout, but the surface mixes long repository_manager_* prefixes with shorter rm_* families, and some tools use vague or internal action suffixes such as rm_gates_phase_direction_here and rm_gates_explain/profile. The repeated family prefixes help somewhat, but the inconsistent dual naming scheme and duplicated action vocabulary make it feel ad hoc.
At 120 tools, the server is far beyond a reasonable tool surface for repository management. Many tools are near-duplicates, internal workflow phases, or thin wrappers around the same Git operations, so the count is an extreme mismatch rather than a well-scoped set.
The surface broadly covers cloning, pulling, pushing, committing, building, testing, validation, worktrees, merge queues, and workspace setup, so core repository workflows are present. However, there are notable gaps and placeholder-like areas such as empty rm_rollout descriptions, no clear project deletion/removal path, and no obvious branch creation/checkout/diff/log lifecycle outside a generic git action.