Sourcegraph MCP server extends Copilot across all repos

GitHub Copilot's context is bounded by the repository currently open in the editor — if the relevant code lives in another repo or on a different code host such as GitLab, Copilot cannot access it. Sourcegraph's MCP server is presented as a direct solution to this limitation, acting as a bridge that gives Copilot visibility into an organization's entire codebase spread across hundreds of repositories.

The integration works by pointing Copilot at a Sourcegraph instance through the MCP server.

The integration works by pointing Copilot at a Sourcegraph instance through the MCP server. Authentication uses the user's existing login, and access is scoped to only the repositories the user already has permission to view. When a question is asked in Copilot chat — the video uses the example of how authentication works across Kubernetes and Grafana — Sourcegraph runs indexed search across all connected repos, finds the real definitions and dependencies, and hands that context back to Copilot. The result is described as "same chat, real answers." The video notes that the Sourcegraph MCP server and deep search are compatible with tools teams already use, and directs viewers to sourcegraph.com/mcp for more information.

Key facts

1. 01GitHub Copilot is limited to the single repository currently open in the editor.
2. 02The Sourcegraph MCP server connects Copilot to a user's entire codebase across multiple repositories and code hosts, including GitLab.
3. 03Authentication uses the user's own login, and access is restricted to repos the user already has permission to view.
4. 04Sourcegraph runs indexed search across all connected repos to find real definitions and dependencies.
5. 05The video demonstrates a cross-repo query about authentication across Kubernetes and Grafana as an example.
6. 06More information is available at sourcegraph.com/mcp.

Topics