Public server profile · MCR-20260906-SOURCEGRAPH
Sourcegraph MCP Server
A sourced reference profile for Sourcegraph’s documented MCP endpoints, access controls and client configuration paths.
Official vendor sources only
- Vendor
- Sourcegraph
- Product version
- Live documentation; deployment version not specified
- Protocol version
- Not established by cited pages
- Transport
- Remote HTTP endpoints
- Authorization
- OAuth 2.0 or Sourcegraph access token
- Profile updated
- 06 September 2026
Vendor-declared surface
What the documentation says.
Purpose
Programmatic access to Sourcegraph code search, navigation and analysis for AI agents and applications. The documentation states that MCP support is available on Enterprise plans.
Endpoints
The docs describe /.api/mcp, /.api/mcp/all and /.api/mcp/deepsearch, with different tool suites.
Authentication
OAuth 2.0 using dynamic or pre-registered clients, or Sourcegraph access tokens. The documented MCP OAuth scope is mcp.
Access controls
Site enablement, tool-level disabling and MCP#ACCESS RBAC are documented. Repository permissions remain a separate boundary.
Documented clients
Configuration guides exist.
The client-integration page lists Claude Code, Codex, Cursor, Copilot, OpenCode, Amp, Google Gemini Code Assist, VS Code, Antigravity and Windsurf. A listed guide is not an independent compatibility result.
Specific documented caveat: Sourcegraph states that Codex must request only the mcp OAuth scope for this connection; otherwise login fails with invalid_scope. This has not been reproduced in this profile.
Evidence register
Sources behind this profile.
SR-01Sourcegraph MCP client integrations
official documentation · accessed 06 September 2026 · Live documentation; product version not stated
Primary source for named client setup guides and the documented Codex OAuth scope requirement.
SR-02Sourcegraph MCP server
official documentation · accessed 06 September 2026 · Live documentation; product version not stated
Primary source for endpoints, authentication, access controls and documented tool suites.
Still unknown
What this page cannot tell you.
- Whether any specific Sourcegraph deployment supports a particular protocol version.
- Whether a named client connects successfully in a buyer's identity, network and permission environment.
- Whether individual tools return correct results for a buyer's repositories and workflows.
- Performance, resilience, security posture or marketplace acceptance.
A scoped, authorized test is required before any of these become observed results.