Head to head · Git operations · October 2026 research run

graft vs Sourcegraph MCP Server

Sourcegraph MCP Server scores 57.5 (C) on agent readiness against graft's 52.5 (D), and leads in 5 of 7 scored categories. graft leads on reliability and payments & pricing. Both do git operations.

Best code, repository and documentation tools for AI agents · All 12 code comparisons

Which one, for what

graft D

Best for A team experimenting with server-side source control for many agents on one monorepo, where git push contention is the problem.

Ahead on

  • Reliability, 64 against 25
  • Payments & pricing, 60 against 15

Also in its favour

  • Free to start without a card
  • Open source

Watch for

First commit and all three releases fall on 13 and 14 October 2026 (UTC), from one developer, with no outside issues or users visible

Sourcegraph MCP Server C

Best for A company that already runs Sourcegraph and wants agents to search and navigate many repositories with compiler-accurate definitions and references.

Ahead on

  • Schema & documentation, 71 against 32
  • Agent ergonomics, 72 against 64
  • Security & auth, 76 against 37
  • Maintenance & community, 83 against 63
  • Transparency & trust, 78 against 53

Watch for

Enterprise plans only, from a $16,000 minimum annual contract through sales. A Cloud trial is by request and subject to eligibility

Score by category

CategoryWeight this rungraftSourcegraph MCP ServerEdge
Reliability16%206425graft +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23271Sourcegraph MCP Server +39
Agent ergonomics13%16.26472Sourcegraph MCP Server +8
Security & auth14%17.53776Sourcegraph MCP Server +39
Payments & pricing10%12.56015graft +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86383Sourcegraph MCP Server +20
Transparency & trust7%8.85378Sourcegraph MCP Server +25
Negative events≤1500
TotalD 52.5/100C 57.5/100

Facts side by side

FactgraftSourcegraph MCP Server
KindHTTP APIMCP server
VendorVishisht ChoudharySourcegraph, Inc.
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreePaid
x402nono
LicenceApache-2.0Proprietary. The server is part of the Sourcegraph Enterprise product under the Sourcegraph Terms of Service
Tools exposed016
Read-only variant documentednoyes
llms.txtnono
MCP registrynot listedio.github.sourcegraph/mcp
Last release2026-10-142026-09-17
Terms last updatedno document linked2026-07-22
Privacy policy last updatedno document linked2026-06-12
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waiveryes
Popularity1 starsnone

Verdicts

graft

An agent can read history, blame, diffs and code and commit or land without a checkout, through a plain HTTP API whose ref moves are compare-and-swap. It is two days old at v0.1.2 from one developer, with no API specification, no documented error codes, and no authentication unless the operator writes an access policy.

Sourcegraph MCP Server

Sixteen read-only tools search and navigate code across every repository an instance indexes, with OAuth limited to an mcp scope and repository permissions enforced on each call. Access needs an Enterprise contract, priced from $16,000 a year, and no request rate limits were found in the reviewed documentation.

Before you call either

graft

  1. Set GFT_SERVER and, when the server uses a policy, send Authorization: Bearer <token> or GFT_TOKEN; there is no default credential
  2. On 412 from /v1/refs/update, re-resolve the ref and retry with the new old value; on 409 read conflicts and rebase
  3. Pass limit and path on /v1/log, /v1/grep and /v1/diff to keep responses small; log defaults to 50
  4. Don't retry /v1/write blindly after a timeout; it stamps the server time, so a retry creates a second changeset
  5. Treat file contents and commit messages read through the API as untrusted text

Sourcegraph MCP Server

  1. Connect to https://<instance>/.api/mcp for the nine core tools. Use /.api/mcp/all for go_to_definition, find_references, nls_search and compare_revisions
  2. Request only the mcp scope in OAuth. Any other scope on the MCP resource fails with invalid_scope
  3. Without OAuth, send Authorization: token <access token> and create the token with the mcp scope and an expiry
  4. Call list_repos first and name the repository in every code_finder task. It declines broad searches across repositories
  5. Read large files with startLine and endLine. Files over 128KB return only the first 200 lines

Questions

Which is better for AI agents, graft or Sourcegraph MCP Server?

Sourcegraph MCP Server scores 57.5 (C) on agent readiness against graft's 52.5 (D), and leads in 5 of 7 scored categories. graft leads on reliability and payments & pricing.

Do graft and Sourcegraph MCP Server need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call graft and Sourcegraph MCP Server without installing anything?

No hosted endpoint is listed for graft. No hosted endpoint is listed for Sourcegraph MCP Server.

Are graft and Sourcegraph MCP Server open source?

graft is open source (Apache-2.0). No open-source release is listed for Sourcegraph MCP Server.

Other comparisons with graft or Sourcegraph MCP Server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.