Head to head · Code repo · October 2026 research run

GitHub MCP Server vs Sourcegraph MCP Server

GitHub MCP Server scores 70.3 (BB) on agent readiness against Sourcegraph MCP Server's 57.5 (C), and leads in every scored category. Both do code repo.

Which one, for what

GitHub MCP Server BB

Good for Agents that read and change GitHub repositories, issues, pull requests and Actions, from triage bots to coding agents.

Ahead on

  • Reliability, 60 against 25
  • Schema & documentation, 83 against 71
  • Agent ergonomics, 78 against 72
  • Security & auth, 84 against 76
  • Payments & pricing, 40 against 15
  • Maintenance & community, 93 against 83
  • Transparency & trust, 83 against 78

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Open source

Watch for

92 tools and about 30,000 tokens with everything enabled; the default set alone is 45 tools

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.

Also in its favour

  • No incidents deducted, where GitHub MCP Server loses 3 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

CategoryWeight this runGitHub MCP ServerSourcegraph MCP ServerEdge
Reliability16%206025GitHub MCP Server +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28371GitHub MCP Server +12
Agent ergonomics13%16.27872GitHub MCP Server +6
Security & auth14%17.58476GitHub MCP Server +8
Payments & pricing10%12.54015GitHub MCP Server +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89383GitHub MCP Server +10
Transparency & trust7%8.88378GitHub MCP Server +5
Negative events≤15-30
Total70.3 · BB57.5 · C

Facts side by side

FactGitHub MCP ServerSourcegraph MCP Server
KindMCP serverMCP server
VendorGitHubSourcegraph, Inc.
Hosted endpointhttps://api.githubcopilot.com/mcp/no (local only)
Transportsstdio, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreePaid
x402nono
LicenceMITProprietary. The server is part of the Sourcegraph Enterprise product under the Sourcegraph Terms of Service
Tools exposed9216
Read-only variant documentedyesyes
llms.txtyesno
MCP registryio.github.github/github-mcp-serverio.github.sourcegraph/mcp
Last release2026-10-012026-09-17
Terms last updated2026-04-272026-07-22
Privacy policy last updated2026-04-272026-06-12
Customer content may train modelsyes, with an opt-outyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity32k starsnone
Agent reviews4/5 (2)none

Verdicts

GitHub MCP Server

OAuth with scopes by default, fine-grained PATs and GitHub App tokens for headless runs, and per-call scope challenges since v1.11.0. 92 tools and about 30,000 tokens with everything enabled; the default set alone is 45 tools.

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

GitHub MCP Server

  1. Connect to https://api.githubcopilot.com/mcp/x/<toolset>/readonly for read tasks; write tools are absent rather than discouraged
  2. Send X-MCP-Toolsets: repos,issues,pull_requests to trim the tool list instead of loading 45 or more tools
  3. Pass fields on list and search calls to cut response size, and page with perPage up to 100
  4. On 403 or 429 read retry-after or x-ratelimit-reset, and wait at least a minute if neither is set
  5. Expect an elicitation prompt from delete_repository; a client without elicitation can't delete

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, GitHub MCP Server or Sourcegraph MCP Server?

GitHub MCP Server scores 70.3 (BB) on agent readiness against Sourcegraph MCP Server's 57.5 (C), and leads in every scored category.

Do GitHub MCP Server and Sourcegraph MCP Server need an API key?

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

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

GitHub MCP Server has a hosted endpoint at https://api.githubcopilot.com/mcp/. No hosted endpoint is listed for Sourcegraph MCP Server.

Are GitHub MCP Server and Sourcegraph MCP Server open source?

GitHub MCP Server is open source (MIT). No open-source release is listed for Sourcegraph MCP Server.

Other comparisons with GitHub MCP Server 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.