Skip to content

document querying a repository group over mcp #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SyedFahad7 merged 1 commit into from
Nov 5, 2026
Merged

document querying a repository group over mcp #211

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion platform/graphs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ A combined graph moves through `not_started`, `queued`, `running`, then `ready`

## Query the graph

The console, Ask, and your [hosted MCP](/platform/hosted-mcp) agent all query the same graph. Each query targets one repository, by ID, full name such as `acme/api`, or short name such as `api`. A combined graph is targeted by its name.
The console, Ask, and your [hosted MCP](/platform/hosted-mcp) agent all query the same graph. Each query targets one repository, by ID, full name such as `acme/api`, or short name such as `api`. A combined graph is targeted by its name in the UI, or by its group id over MCP: `list_repositories` returns it with `kind: "workspace"`, and query tools take that id in the `repository_id` slot. See [Query a repository group](/platform/hosted-mcp#query-a-repository-group).

| Code | Status | Fix |
| --- | --- | --- |
Expand Down
12 changes: 12 additions & 0 deletions platform/hosted-mcp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,18 @@ Each review includes the repository, PR number and title, status (`queued`, `run

If the review is still queued or running, the response includes how many minutes it has been in flight and a hint to check again in a few minutes instead of polling continuously. See [Pull request reviews](/platform/reviews).

## Query a repository group

A [combined graph](/platform/graphs#combine-repositories) is a query target for your agent, the same way a single repository is.

1. In Graphify, open **Graphs**, choose **Combine graphs**, and pick the repositories. Wait until the combined graph is ready.
2. Ask your agent to run `list_repositories`. Combined graphs appear in that list with `kind: "workspace"`. Their `repositoryId` is the group id, and `fullName` is the name you gave the group.
3. Pass that `repositoryId` to the usual query tools (find, callers, impact, and the rest). Graphify serves the group's promoted merged graph.

A group is queryable only when its current merge is promoted. If `queryable` is false, the merge is still building, failed, or was not promoted. Combined graphs have no pull requests, so review tools do not apply to them.

See [Graph explorer](/platform/graphs) for how to build and open a combined graph in the UI.

## How hosted MCP sign-in works

You don't paste a key. Your client discovers the sign-in flow from the server:
Expand Down
Loading