Can Lyro run a code search across the whole instance?

Not with this toolkit. It exposes file and directory listing, file contents, commit details, and diffs, but no search action, so Lyro navigates to a file or a commit rather than querying for a pattern across repositories. A repository name or path is the starting point.

Which branch does Get File Contents read from?

The default branch only. That is the documented scope of the action, so a file that exists on a feature branch and not on the default branch will not come back. Compare Commits is the way to see work that has not been merged yet.

Can Lyro change anything in Sourcegraph?

No. Even Check Site Settings Edit Permission only reports whether the API would allow a site settings edit; it does not make one. Every other action reads repositories, files, commits, or the current user, so the integration is safe to point at a production instance.

What decides which repositories Lyro can see?

The permissions on the connected Sourcegraph credentials. Get Current User confirms which identity the connection acts as, and List Repositories returns only what that identity can reach on the instance, so a private repository outside its access does not appear.

Sourcegraph MCP integration

Fetches raw file contents and commit diffs without cloning, enumerates repositories and their languages, and confirms the connected identity.

Connect Sourcegraph See all integrations

8actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

List repositories
Lyro lists all repositories available on the Sourcegraph instance. Agents discover codebases and project structure without GitHub navigation.
Get commit details
Lyro retrieves detailed information about a specific commit. Agents trace code changes to root causes in real time.
Get file contents
Lyro fetches file contents from a repository to inspect code. Agents review implementation details without cloning repos.

See all 8 actions

How businesses use Sourcegraph + Lyro

Each card is one request a support team gets, and the Sourcegraph actions Lyro runs to close it.

Read a file without cloning the repository
Lyro fetches the raw text of a file on the default branch and can enumerate the files and directories under a path first, which is faster than going through the code host's own API.
Get File ContentsList Repository Files
Explain what changed between two commits
Lyro compares two commit SHAs in a repository and returns the file diffs, then pulls the detail on a specific commit so the answer includes who made the change and when.
Compare CommitsGet Commit Details
Survey what is actually in the codebase
Lyro pages through the repositories on the instance and lists the languages used in any one of them, which is how you find out whether a service still has Python in it.
List RepositoriesList Repository Languages
Confirm the connection's identity and reach
Before anything else, Lyro checks which authenticated user the connection acts as and whether the API permits site settings edits at all, so a permissions answer is not a guess.
Get Current UserCheck Site Settings Edit Permission

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Sourcegraph actions it has and picks the ones a request needs.

01
Connect Sourcegraph
Authorize the Sourcegraph account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Sourcegraph actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Sourcegraph · Lyro

Everything else about Sourcegraph

Setup, permissions, and the limits of what Lyro can do inside Sourcegraph.

Not with this toolkit. It exposes file and directory listing, file contents, commit details, and diffs, but no search action, so Lyro navigates to a file or a commit rather than querying for a pattern across repositories. A repository name or path is the starting point.

Every action available in Sourcegraph

All 8 actions your agent can call on Sourcegraph, straight from the live MCP connection.

Check site settings edit permission
Check whether site settings can be edited through the API.
Compare commits
Compare two commits in a repository and retrieve their file diffs.
Get commit details
Get detailed information about a specific commit in a repository.
Get current user
Retrieve information about the currently authenticated user.
Get file contents
Fetch the contents of a specified file on the default branch.
List repositories
List repositories on the Sourcegraph instance.
List repository files
List all files and directories in a repository path.
List repository languages
List languages used in a repository.