No user-submitted related servers found.
Scored across 16 tools
Every tool targets a distinct git/GitLab operation, and the descriptions actively disambiguate the risky pairs: `compare` explicitly never returns a patch and points to `diff_file`; `search` points to `pickaxe` for 'when' vs 'where'; `log`/`get_commit`/`blame` each own a different history view. Repo lifecycle tools (add/remove/sync/list_repos) and ref tools (list_refs/resolve_ref) also have clear, non-overlapping roles.
The dominant pattern is verb_noun (get_file, list_tree, get_commit, list_refs, list_repos, add_repo, remove_repo, sync_repo, resolve_ref, diff_file, parse_gitlab_url), which is predictable. The deviations (log, blame, compare, search, pickaxe) are deliberate git-subcommand parity, so they are still guessable, but it is a mixed convention rather than a single one.
16 tools is at the upper end of the comfortable range, but for a read-only git surface each one maps to a real, non-redundant operation (files, refs, history, diffing, repo registration). Nothing feels padded, though a few could arguably be folded (e.g. resolve_ref into list_refs).
The read-only domain is well covered end to end: registration/sync, ref discovery and resolution, tree/file reads, grep, pickaxe, log, commit, blame, and both branch-level and file-level diffs. Minor gaps remain — no way to discover projects on the GitLab host without knowing the path, and no merge request/issue/CI reads (explicitly refused), which limits use as a general GitLab API client.