Sourcegraph MCP Server

Why it got an A

Sourcegraph's own MCP server, built into Sourcegraph Enterprise instances rather than shipped as a package: point a client at https:///.api/mcp (core search, repo, history and Deep Search reading tools), /.api/mcp/all (full tool set) or /.api/mcp/deepsearch. Sign-in is OAuth 2.0 or an access token, users need the MCP access permission, and repository permissions still apply, so a session sees only what that user can already read. The tools are search, read and analysis (read_file, list_files, keyword_search, nls_search, go_to_definition, find_references, commit_search, diff_search, compare_revisions and Deep Search); the docs describe no write tools. Admins can switch it off with mcp.enabled or remove tools such as code_finder and deepsearch with mcp.tools.disabled. No advisories on record. Biggest deduction: it is closed source with no repo or versioned releases, so maintenance rests on Sourcegraph's dated changelog (latest verified entry November 2026) and sits one band lower; the docs also don't state the MCP transport variant beyond "http", and code_finder is metered. This is not the sourcegraph-community plugin, and it is separate from third-party open-source Sourcegraph MCP wrappers.