GitLab MCP Server vs graft

GitLab MCP Server 85

The tools reference documents every parameter with its type, required flag and enum values, and the server exposes JSON Schema through MCP; we read the reference, not the source (22). docs.gitlab.com/llms.txt is served (10). Each tool says what it does, and superseded tools name their replacement (Use get_merge_request with include: commits), though few say when not to use one (14). Enums for include facets, states, scopes and methods, with documented maximums such as first up to 100 and byte_limit up to 1 MB (13). The docs cover 403 insufficient_scope, 400 for an unknown toolset, 429 headers and troubleshooting for Windows and Claude Code, but give few example responses (11). Per-tool version history and monthly release notes (15). 22 + 10 + 14 + 13 + 11 + 15 = 85.

graft 32

No OpenAPI or other machine-readable contract. Request and response shapes exist only as Go structs in internal/api (0). No llms.txt. README, DESIGN.md and ACCESS.md are Markdown on GitHub (5). The README's endpoint table gives one line per endpoint with its query parameters and nothing on when to use one over another (6). Parameters are named but types, defaults and bounds are found only in the source (6). Many CLI examples, but no HTTP request or response examples, and the 400, 403, 404, 409, 412 and 422 responses are not documented (5). Paths under /v1 and release notes on GitHub for three releases (10). Total 32.

GitLab MCP Server 30

No x402, MPP or L402 (0). Plan prices are public for Free and Premium, Ultimate is by quote and GitLab Credits are $1 each, but the MCP server has no per-call price (10). GitLab.com Free needs no card, and the MCP server is on every tier (20). A person signs up, and an administrator must enable MCP and a user must authorise in a browser (0). 0 + 10 + 20 + 0 = 30.

graft 60

No payment protocol (0). Read with the self-hosted rule. Free under Apache 2.0 with nothing to buy (20). No card or account (20). Download or go install with no signup (20). Total 60.

GitLab MCP Server 87

GitLab's code is public in gitlab-org/gitlab, with the core under MIT and enterprise functions under GitLab's own licence; we didn't establish which licence covers the MCP server code (20). The privacy statement and a sub-processor page of 63 entries name AI providers and their purposes, but that page shows no update date and links no DPA (20). A dated deprecations and removals page and per-tool version history, with superseded tools kept as callable aliases (20). Sub-processors and their locations are disclosed, and Dedicated customers choose their AWS region (18). 20 + 20 + 20 + 18 = 78.

graft 57

Apache 2.0 in LICENSE and as detected by GitHub (30). No privacy or data-handling statement. The software is self-hosted and the source we read sends nothing to the author, so data stays with the operator, but nothing says so (10). No deprecation policy, and the release notes are dated only by their GitHub release (2). No telemetry or analytics calls found in the source, and the docs don't address it (10). Total 52.

GitLab MCP Server 66

OAuth with dynamic registration and a single mcp scope that carries the user's own GitLab permissions, or fine-grained personal access tokens scoped to the MCP tool resource. The docs say GitLab doesn't verify which client uses a client ID and that REST-created apps don't enforce PKCE (22). Toolset and tool headers narrow the surface, an administrator must enable MCP for the group or instance, 19.4 governance defaults writes to Always Ask in Duo settings and 19.6 adds group rules enforced for every client, in beta (16). The docs leave prompt injection to the user ("use MCP tools only on GitLab objects you trust") (5). GitLab audit events exist on paid tiers, but we didn't read whether MCP calls are recorded (8). security.txt is valid until 31 January 2027 and points at a public HackerOne programme; certifications weren't read this run (15). 22 + 16 + 5 + 8 + 15 = 66.

graft 37

Self-hosted server read with the API lines. With no policy, every caller can read and write everything. With --acl, static bearer tokens map to principals and can be stored hashed, and revoking means editing the policy. Tokens go only in the Authorization header, but the server has no TLS option (12). Roles none, read, write and admin, directory-level read and write rules checked on every path and on the whole diff of each ref move, admin-only ref deletion, and review gates where authors cannot approve their own changes (17). The API returns repository files and commit messages with no guidance on untrusted content (2). The server logs errors only. Change request comments and approvals record the principal, but a changeset's author is whatever the client sends (4). No SECURITY.md, security.txt or bug bounty. Release checksums are published (2). Total 37.

GitLab MCP Server 85

GitLab 19.5 made the server generally available on 15 October 2026, 22 days before this check, and 19.6 changes are already on GitLab.com (30). Monthly releases 19.3, 19.4 (17 September) and 19.5 each changed MCP tools (20). Issues are public on gitlab.com, with a feedback issue (630189) for the server, but we didn't measure reply times (15). The registry entry com.gitlab/mcp sits under a domain-verified namespace with the right remote, though its version is still 0.0.1 from 2 October 2025 (10). GitLab ships through its own CI with monthly and patch releases; no official multi-language API SDK was found (10). 30 + 20 + 15 + 10 + 10 = 85.

graft 63

v0.1.2 on 14 October 2026 UTC, read from the git tags (30). Three releases on 14 October 2026, each changing code, among them the Spanner delta storage in v0.1.2 (20). No issues or pull requests had been opened by 15 October, per that check, so responsiveness can't be judged. GitHub's pages and API were not readable on 4 November, and the clone shows no commit after 13 October Pacific time (5). No MCP server and no SDK (0). Go 1.26 in go.mod and CI passing on main on 14 October, per the 15 October check (8). Total 63.