# Git (MCP reference server) vs Sourcegraph MCP Server

> Sourcegraph MCP Server scores 57.5 (C) on agent readiness against Git (MCP reference server)'s 51.9 (D), and leads in 5 of 7 scored categories. Git (MCP reference server) leads on reliability and payments & pricing. Both do code git. Category scores, facts, verdicts and agent…

- Canonical: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp
- Markdown: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp.md (~2,150 tokens)
- Slim: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

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

- Git (MCP reference server): grade D, 51.9/100, rank #499 of 629. Markdown https://www.anchorterminal.com/tools/git-reference-server.md · JSON https://www.anchorterminal.com/api/v1/tools/git-reference-server.json
- Sourcegraph MCP Server: grade C, 57.5/100, rank #420 of 629. Markdown https://www.anchorterminal.com/tools/sourcegraph-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/sourcegraph-mcp.json

## Which one, for what

### Git (MCP reference server) (D)

Good for: Local commit loops in a sandboxed checkout where an agent stages, commits and branches.

Ahead on:
- Reliability, 55 against 25
- Payments & pricing, 60 against 15

Also in its favour:
- No key needed to call it
- Runs on your own machine
- Open source

Watch for: Four advisories in the last year (argument injection, path validation, `git_init`, `git_add` traversal), all fixed

### Sourcegraph MCP Server (C)

Good 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 61
- Security & auth, 76 against 37
- Maintenance & community, 83 against 39
- Transparency & trust, 78 against 73

Also in its favour:
- No incidents deducted, where Git (MCP reference server) loses 4 points for them

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

| Category | Weight | Git (MCP reference server) | Sourcegraph MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 25 | Git (MCP reference server) +30 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 71 | Sourcegraph MCP Server +10 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 72 | Sourcegraph MCP Server +3 |
| Security & auth | 14% (17.5 this run) | 37 | 76 | Sourcegraph MCP Server +39 |
| Payments & pricing | 10% (12.5 this run) | 60 | 15 | Git (MCP reference server) +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 39 | 83 | Sourcegraph MCP Server +44 |
| Transparency & trust | 7% (8.8 this run) | 73 | 78 | Sourcegraph MCP Server +5 |
| Negative events | ≤15 | -4 | 0 | |
| **Total** | | **51.9 · D** | **57.5 · C** | |

## Facts side by side

| Fact | Git (MCP reference server) | Sourcegraph MCP Server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | MCP project (reference servers) | Sourcegraph, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | MIT and Apache-2.0 | Proprietary. The server is part of the Sourcegraph Enterprise product under the Sourcegraph Terms of Service |
| Tools exposed | 12 | 16 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| MCP registry | not listed | `io.github.sourcegraph/mcp` |
| Last release | 2026-08-18 | 2026-09-17 |
| Terms last updated | 2021-09-08 | 2026-07-22 |
| Privacy policy last updated | 2023-03-15 | 2026-06-12 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 90k stars, 41k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | none |

## Verdicts

**Git (MCP reference server).** Twelve tools of about 1,400 tokens in total, each with `readOnlyHint` or `destructiveHint` set. Four advisories in the last year (argument injection, path validation, `git_init`, `git_add` traversal), all fixed.

**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

### Git (MCP reference server)

1. Pass `repo_path` on every call, even when the server was started with `--repository`
2. Use `git_diff_staged` before `git_commit`; commit takes whatever is staged and can't be undone through the server
3. Set `max_count` and a date range on `git_log`; diffs and `git_show` have no size cap
4. Send `branch_type` as one of `local`, `remote` or `all`; anything else returns an error string, not a schema error
5. Push with another tool; this server has no remote operations

### 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, Git (MCP reference server) or Sourcegraph MCP Server?

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

### Do Git (MCP reference server) and Sourcegraph MCP Server need an API key?

Git (MCP reference server) needs no key. Sourcegraph MCP Server takes an API key or an OAuth sign-in.

### Can an agent call Git (MCP reference server) and Sourcegraph MCP Server without installing anything?

Git (MCP reference server) runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Sourcegraph MCP Server.

### Are Git (MCP reference server) and Sourcegraph MCP Server open source?

Git (MCP reference server) is open source (MIT and Apache-2.0). No open-source release is listed for Sourcegraph MCP Server.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/git-reference-server-vs-sourcegraph-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "git-reference-server", "b": "sourcegraph-mcp"}`. From a terminal: `anchor compare git-reference-server sourcegraph-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/git-reference-server.json and https://www.anchorterminal.com/api/v1/tools/sourcegraph-mcp.json

## Other comparisons with Git (MCP reference server) or Sourcegraph MCP Server

- [Azure DevOps MCP Server vs Sourcegraph MCP Server](https://www.anchorterminal.com/compare/azure-devops-mcp-vs-sourcegraph-mcp.md)
- [GitHub MCP Server vs Sourcegraph MCP Server](https://www.anchorterminal.com/compare/github-mcp-server-vs-sourcegraph-mcp.md)

## Disclosure

- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.