Head to head · Code repositories · October 2026 research run

GitHub MCP Server vs Sourcegraph MCP Server

GitHub MCP Server scores 74.9 (BB) on agent readiness against Sourcegraph MCP Server's 62.5 (B), and leads in every scored category. Both do code repositories.

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

Which one, for what

GitHub MCP Server BB

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

Ahead on

  • Reliability, 65 against 60
  • Schema & documentation, 83 against 71
  • Agent ergonomics, 78 against 72
  • Security & auth, 84 against 76
  • Payments & pricing, 60 against 23
  • Maintenance & community, 93 against 83
  • Transparency & trust, 84 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 B

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing GitHub MCP Server +37

GitHub MCP Server 60

No x402, MPP or L402 (0). The server costs nothing and says so in public (20). A free GitHub account needs no card (20). An agent can't get access without a person creating an account and approving OAuth or minting a PAT (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Sourcegraph MCP Server 23

No x402, MPP or L402 (0). The pricing page publishes a starting figure, a $16K minimum annual contract, with no per-user or per-call price and a contact-sales button, so half of the plan-pricing credit (5). A free Sourcegraph Cloud trial exists by request, with eligibility reviewed and a wait of up to an hour in business hours. No card is mentioned, so half credit (10). An agent cannot gain access alone. A company needs a contract or an approved trial, and a user approves OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Schema & documentation GitHub MCP Server +12

GitHub MCP Server 83

Every tool has a JSON Schema input, snapshotted in the repository for review (25). docs.github.com/llms.txt exists per the 30 September check, and the server docs are Markdown (10). Descriptions are short (median 82 characters) and mostly state purpose. Some say when to use them (search_code for exact symbols) or point elsewhere (label_write names update_issue), most don't (12). Enums for state, order and merge method, perPage bounded 1 to 100, required fields marked. Three tools take free-form objects (create_repository_ruleset, actions_run_trigger, projects_write) (12). The README lists every parameter per tool. Errors come back as tool results with GitHub's message, and the error-handling doc is aimed at contributors, not models (9). Semver releases with notes, and a tool-renaming doc with a table of 25 deprecated aliases that still resolve (15). Since v2.0.0 (7 October 2026) repository, issue, pull request, search and other tools also publish output schemas and typed structuredContent to clients that negotiate MCP protocol 2026-07-28 or newer, with older clients getting the earlier text results. Score unchanged.

Sourcegraph MCP Server 71

The docs list each tool's parameters with required and optional marks, defaults and maximums. We could not read the tool definitions themselves, because every endpoint needs an Enterprise instance, so the machine-readable contract earns partial credit (15). /llms.txt and /docs/llms.txt return 404, but every docs page is served as Markdown at its URL plus .md (10). Tool entries state use cases, code_finder has best practices and a contrast with deepsearch, and a matrix shows which endpoint carries which tool (14). Required fields, defaults and bounds are documented, while search filters travel inside one query string and evaluator takes a free Lua script (9). list_refs has JSON examples and the authentication page has a troubleshooting table for invalid_scope, 401, 403 and 404, with no catalogue of tool errors (8). Versioned releases with dated MCP entries in the changelog (15).

Maintenance & community GitHub MCP Server +10

GitHub MCP Server 93

v2.0.3 on 21 October 2026 (30). Thirteen releases since 3 August, from v1.9.0 on 10 August to v2.0.3, among them v2.0.0 on 7 October (20). 159 open issues and triage labels within days per the 1 October check, not re-read on 1 November (GitHub's pages answered 403). An AI triage workflow and an inactive-issue closer run. We couldn't read reply times (18). Listed in the official MCP registry as io.github.github/github-mcp-server at 2.0.3, marked latest and published on 21 October (15). Go CI, lint, code scanning, licence checks and a tool-diff check on pull requests (10).

Sourcegraph MCP Server 83

Self-hosted releases in the window are 7.6.0 (6 August), 7.7.0 (26 August), 7.7.359 (27 August), 8.0.0 (17 September), 8.1.0 (14 October), 8.1.1335 (22 October) and 8.1.2687 (29 October 2026). 7.6.0, 7.7.0, 8.0.0 and 8.1.0 change the MCP server, and the two 8.1 patches don't. The weekly Cloud update notes of 2 November 2026 add a warning to MCP tool results when a code host connection has expired (30). Four releases that change the MCP server since 6 August 2026, plus weekly Cloud notes (20). A closed service with a public changelog, support at support@sourcegraph.com and published response times from two business hours for Enterprise. No public issue tracker for the server was found (12). Listed in the official MCP registry as io.github.sourcegraph/mcp per the 8 October check; the registry's API wasn't requested on 4 November (15). Release 7.6.0 moved to the MCP Go SDK v1.7.0 and protocol version 2026-07-28, and releases name the CVEs they fix. No public CI to read (6). 30+20+12+15+6 = 83.

Security & auth GitHub MCP Server +8

GitHub MCP Server 84

OAuth with scopes is the remote default, with fine-grained PATs and GitHub App tokens for headless use, all in the Authorization header. v1.11.0 added per-call OAuth scope challenges (30). --read-only, /readonly URLs and X-MCP-Readonly drop write tools. delete_repository asks the user to type the full repository name through elicitation. delete_file and the other destructive tools run without a confirmation step (17). Lockdown mode filters public-repository content from authors without push access, and the README says plainly it's a best-effort filter, not a boundary. July 2026 commits made lockdown fail closed (13). MCP calls show in GitHub's audit log as ordinary API calls, and the governance doc says MCP-specific audit logs aren't available yet (8). SECURITY.md with coordinated disclosure, GitHub's bug bounty (open-source repositories are out of scope for rewards), two advisories published in public in 2026, and github.com's security.txt expired per the 30 September check (16).

Sourcegraph MCP Server 76

OAuth 2.0 with PKCE, dynamic client registration held to the mcp scope, one-hour access tokens, a revocation endpoint and bearer tokens in the header only. Access tokens can also carry the mcp scope and default to a 90-day expiry (30). Every documented tool reads, repository permissions apply to each call, and admins can gate MCP by RBAC role or disable single tools. There is no per-repository grant narrower than the user's own access (18). The tools return repository content, which is untrusted input. The consent screen warns that the mcp scope grants read access to private code, and no prompt-injection guidance was found (4). The audit log records access token use, repository access and API requests as structured logs for a SIEM. No MCP-specific call log is documented (9). SOC 2 and ISO/IEC 27001:2022 on the security portal, annual third-party penetration tests, CVE fixes named in release notes and an invite-only HackerOne programme reached through security@sourcegraph.com. security.txt returned 404 again on 4 November 2026 (15).

Agent ergonomics GitHub MCP Server +6

GitHub MCP Server 78

92 documented tools across 22 toolsets, about 121,000 characters or 30,000 tokens with everything on. The default five toolsets load 45 tools, about 13,600 tokens (5). Toolsets, per-tool selection, /readonly URLs, X-MCP-Toolsets headers and scope-based hiding of tools a PAT can't use add back 10. Page, cursor and perPage paging, plus a fields parameter on list and search tools to trim responses. Issue #3236 says pull_request_read get_files always returns full patches (18). Errors are tool results with GitHub's message, and OAuth calls get a scope challenge instead of a bare 403 (16). Every tool sets readOnlyHint, eight write tools set destructiveHint: true, but 27 of 35 write tools leave destructiveHint unset (open issue #3281) and no read tool sets idempotentHint. merge_pull_request takes an expectedHeadSha guard (14). Default toolsets, owner and repo as the usual required pair, and official Octokit SDKs in several languages (15).

Sourcegraph MCP Server 72

Sixteen documented tools on /.api/mcp/all, nine on the default endpoint and two on /.api/mcp/deepsearch, and admins can remove tools with mcp.tools.disabled. Definition sizes are unread (23). Result limits on every list and search tool, an after cursor on compare_revisions, count on searches and line ranges on read_file (17). Search tools report incomplete results with retry advice per the 8.0.0 notes, and 8.1.0 (14 October 2026) reports timeouts as errors and query-planning failures as invalid-argument errors rather than server errors, and HTTP 401, 403 and 404 causes are documented, but no tool error list was found (10). No tool writes to a repository, so repeating a call is safe. deepsearch creates a conversation each time, and we could not read the readOnlyHint or destructiveHint annotations (10). Most tools need one to three parameters with stated defaults. There is no SDK to count, as the surface is MCP only (12).

Transparency & trust GitHub MCP Server +6

GitHub MCP Server 84

MIT, with third-party licences listed per platform (30). Data handling falls under GitHub's general privacy statement and DPA. There's no MCP-specific statement of what the remote server logs or keeps (20). Renamed tools keep working through aliases listed in docs/tool-renaming.md, but the table has no removal dates (12). The local server's metrics sink is a no-op. The hosted server records fields usage and payload sizes, which the source shows and the docs don't mention (15).

Sourcegraph MCP Server 78

Closed source under the Sourcegraph Terms of Service, last modified 22 July 2026, with supplemental terms listed in one index (15). The terms, the DPA, the security page and the privacy policy describe data handling. Cloud logs are kept up to 365 days, partner LLMs keep inputs only for abuse detection, and the privacy policy excludes customer code, which falls under the customer agreement. No retention period for code or search queries on Cloud was found (22). The current and previous major versions are supported, and release notes date removals such as the end of GitHub Enterprise Server 3.3 support, but no deprecation policy with a notice period for MCP tools was found (10). Sub-processors are listed with locations and purposes, last modified 21 August 2026, with email notice of changes, and instance telemetry is documented (18).

Score by category

CategoryWeightGitHub MCP ServerSourcegraph MCP ServerEdge
Reliability16%6560GitHub MCP Server +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8371GitHub MCP Server +12
Agent ergonomics13%7872GitHub MCP Server +6
Security & auth14%8476GitHub MCP Server +8
Payments & pricing10%6023GitHub MCP Server +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9383GitHub MCP Server +10
Transparency & trust7%8478GitHub MCP Server +6
Negative events≤15-2-3
TotalBB 74.9/100B 62.5/100

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-212026-10-14
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

How the scores have moved

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, list_refs, get_contributor_repos, compare_revisions, deepsearch and nls_search
  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 74.9 (BB) on agent readiness against Sourcegraph MCP Server's 62.5 (B), 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.