The MCP server provides a standardized interface for accessing Sourcegraph code search and code intelligence capabilities. Configurable against Sourcegraph Cloud or private deployments, it enables MCP-compatible clients to connect and leverage repository discovery, file reads, keyword and semantic search, symbol navigation, references, and code-change workflows.

🛠️ Key Features

Code search, semantic search, and go-to-definition via MCP
Find references, symbol navigation, and file reads
Repository discovery and integration with Sourcegraph deployments
Readme excerpt reflects core capabilities and workflows

🚀 Use Cases

Connect external agents to a Sourcegraph instance
Enable programmatic code intelligence in custom tooling
Standardized access for repository search, navigation, and references

⚡ Developer Benefits

Standard MCP interface for interoperability
Configurable for Sourcegraph Cloud or private deployments
Clear exposure of core code search and intelligence workflows

⚠️ Limitations

Grounded in provided description and readme excerpt; no speculative features

Sourcegraph MCP Server

This registry entry represents the Sourcegraph MCP server for a Sourcegraph instance. It can be configured against Sourcegraph Cloud or a private Sourcegraph deployment, so users can connect MCP-compatible clients to their own Sourcegraph server.

At a high level, the Sourcegraph MCP server gives agents and applications access to Sourcegraph code search and code intelligence capabilities through a standard MCP interface. That includes common workflows such as repository discovery, file reads, keyword and semantic search, symbol navigation, references, and code-change exploration.

Configuration

Configure the server with the hostname of your Sourcegraph instance. This entry uses the standard Sourcegraph MCP endpoint:

https://{sourcegraph_hostname}/.api/mcp

For private Sourcegraph instances, set sourcegraph_hostname to your internal or company-hosted Sourcegraph server hostname.

Authentication is handled by Sourcegraph. Depending on the MCP client, this is typically done with browser-based OAuth or a Sourcegraph access token. This MCP config defaults to OAuth.

Notes

This README intentionally keeps client-specific setup details light because MCP integration steps can change over time. For the current Sourcegraph MCP server behavior, supported authentication modes, and client-specific setup instructions, see the official Sourcegraph documentation:

Install

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://{sourcegraph_hostname}/.api/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://{sourcegraph_hostname}/.api/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.