From 0c39ed962d8e5cbd04826e3773402b8420159fbf Mon Sep 17 00:00:00 2001 From: Syed Fahad Date: Thu, 5 Nov 2026 23:12:21 +0530 Subject: [PATCH] Document querying a repository group over MCP Combined graphs already show up in list_repositories as kind "workspace". This adds the steps to find the group id and pass it to query tools, plus a pointer from the graph explorer page. --- platform/graphs.mdx | 2 +- platform/hosted-mcp.mdx | 12 ++++++++++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/platform/graphs.mdx b/platform/graphs.mdx index cfaec72..e8f831b 100644 --- a/platform/graphs.mdx +++ b/platform/graphs.mdx @@ -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 | | --- | --- | --- | diff --git a/platform/hosted-mcp.mdx b/platform/hosted-mcp.mdx index ee7cdab..690b502 100644 --- a/platform/hosted-mcp.mdx +++ b/platform/hosted-mcp.mdx @@ -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: