Can AI agents automate Sourcegraph?

Sourcegraph is automatable today through the official `src` CLI. This record is Sourcegraph instance code search, navigation, and Deep Search. It is not GitHub or GitLab. `src` installs as a standalone binary on macOS, Linux, and Windows. Interactive use is `src login` OAuth against `SRC_ENDPOINT`. CI and scripts use `SRC_ACCESS_TOKEN`. Documented commands include `src search` (optional `-stream`) and `src api` for GraphQL. Pricing lists single-tenant cloud and self-hosted; this pass did not open pages that establish feature parity between those deployments. HTTP APIs on an instance include GraphQL at `/.api/graphql`, streaming search at `/.api/search/stream`, and a versioned REST surface advertised from Sourcegraph 7.0 at `/api-reference`. GraphQL is documented as a debug API without compatibility guarantees. The new REST API is a work in progress. Auth is an access token (`Authorization: token`) or an OAuth bearer token. GraphQL OAuth needs the `user:all` scope. First-party MCP is HTTP on the instance at `/.api/mcp`, `/.api/mcp/all`, and `/.api/mcp/deepsearch`. Vendor docs state MCP is supported on Enterprise plans. MCP auth is OAuth 2.0 (DCR or pre-registered clients) or access tokens; MCP endpoints require the `mcp` scope and the `MCP#ACCESS` permission. Named tools include `read_file`, `list_files`, `list_repos`, `keyword_search`, `code_finder`, and `deepsearch`. Outgoing webhooks exist for batch-change, changeset, and user events. iPaaS connector catalogs were not opened. Computer-use viability is unassessed. The CLI scores 7 and is the best path because it is official, works with token or OAuth auth, and does not depend on the Enterprise MCP gate documented for `/.api/mcp`.

Best path today: cli · Overall automatability: 7/10