From 9c9cfa82c0d3a301a9b67ada88b1ac729877c1f7 Mon Sep 17 00:00:00 2001 From: Syed Fahad Date: Fri, 6 Nov 2026 19:32:17 +0000 Subject: [PATCH] Rename the hosted MCP page to Graphify MCP Move the page into Get started, after the quickstart, and redirect the old URL. Rewrite it around the endpoint, sign-in, and tools, and correct the capabilities note so review_status reads review results. --- agents/capabilities.mdx | 7 +- agents/headless.mdx | 8 +- agents/overview.mdx | 4 +- agents/recipes.mdx | 2 +- changelog/platform.mdx | 2 +- cookbooks/agent-team-one-graph.mdx | 2 +- cookbooks/cross-repo-dependencies.mdx | 4 +- cookbooks/document-the-why.mdx | 2 +- cookbooks/make-agents-use-the-graph.mdx | 4 +- cookbooks/read-your-graph.mdx | 2 +- cookbooks/reuse-existing-code.mdx | 2 +- docs.json | 8 +- for-agents.mdx | 4 +- index.mdx | 2 +- llms.txt | 6 +- platform/ask.mdx | 2 +- platform/connectors.mdx | 4 +- platform/{hosted-mcp.mdx => graphify-mcp.mdx} | 223 ++++++++---------- platform/graphs.mdx | 2 +- platform/memory.mdx | 6 +- platform/reviews.mdx | 2 +- platform/support/rate-limits.mdx | 2 +- platform/support/troubleshooting.mdx | 6 +- platform/test-impact.mdx | 2 +- platform/verify-connection.mdx | 2 +- platform/workspaces-and-members.mdx | 2 +- scripts/build-llms-txt.py | 4 +- 27 files changed, 145 insertions(+), 171 deletions(-) rename platform/{hosted-mcp.mdx => graphify-mcp.mdx} (61%) diff --git a/agents/capabilities.mdx b/agents/capabilities.mdx index 2f912fd..5a088d2 100644 --- a/agents/capabilities.mdx +++ b/agents/capabilities.mdx @@ -9,7 +9,7 @@ icon: "map" import { PromptBlock } from '/snippets/hero-install.jsx'; -When your coding agent connects to the [hosted MCP server](/platform/hosted-mcp), it gets a set of Graphify tools. This page maps each job you might want done to the tool that does it, with a prompt you can paste. You don't have to name tools in your prompts. Naming them makes it easier to check that the agent used the graph. +When your coding agent connects to [Graphify MCP](/platform/graphify-mcp), it gets a set of Graphify tools. This page maps each job you might want done to the tool that does it, with a prompt you can paste. You don't have to name tools in your prompts. Naming them makes it easier to check that the agent used the graph. ## At a glance @@ -27,6 +27,7 @@ When your coding agent connects to the [hosted MCP server](/platform/hosted-mcp) | Find the tests linked to code | `graphify_tests_for` | | Check that a repository is indexed, and how fresh it is | `graph_stats` | | Read or save what the team remembers | `recall`, `memories_about`, `remember` | +| Read how a pull request review went | `review_status` | | Switch between Graphify workspaces | `list_workspaces`, `set_workspace` | ## Find code @@ -77,7 +78,7 @@ Most tools take a `repository_id`, either an id or a name like `acme/web-app`. ` - They don't edit your code or run your tests. Your agent does that with its own tools. - They answer from the last index of your default branch. Code that isn't merged or indexed yet isn't in the results. -- There's no tool to read pull request reviews. Your agent reads reviews on GitHub. See [Know when a review is ready](/platform/reviews). +- `review_status` does not start a review. It reads status and results. A completed review has `gate` of `pass` or `advisory`, not a `passed` field. See [what review_status returns](/platform/graphify-mcp#what-review_status-returns). ## Related @@ -85,7 +86,7 @@ Most tools take a `repository_id`, either an id or a name like `acme/web-app`. ` Copy-ready prompts for common jobs. - + Client setup and limits. diff --git a/agents/headless.mdx b/agents/headless.mdx index 2ad5744..23b4e3b 100644 --- a/agents/headless.mdx +++ b/agents/headless.mdx @@ -16,7 +16,7 @@ The hosted MCP server at `https://api.graphify.com/mcp` uses OAuth. There is no - Sign-in is a browser flow (authorization code with PKCE). A person has to finish it once in a browser. - Graphify doesn't offer a device-code flow or a client-credentials flow. An agent can't sign itself in. - After the first sign-in, the client keeps working on its own. It asks for `offline_access`, gets a refresh token, and refreshes when the access token expires. -- Each refresh rotates the refresh token. A client that reuses an old one has to sign in again. See [How hosted MCP sign-in works](/platform/hosted-mcp#how-hosted-mcp-sign-in-works). +- Each refresh rotates the refresh token. A client that reuses an old one has to sign in again. See [How sign-in works](/platform/graphify-mcp#how-sign-in-works). If you're an agent and you hit `401`, don't loop. Tell the person which sign-in step to run, then stop. [Agents use Graphify](/agents/overview#while-sign-in-is-pending) lists what to do while you wait. @@ -26,7 +26,7 @@ If you're an agent and you hit `401`, don't loop. Tell the person which sign-in |---|---|---| | Cursor cloud agents | Add `https://api.graphify.com/mcp` as a custom MCP server at [cursor.com/agents](https://cursor.com/agents). Cloud agents don't read a local or committed `mcp.json`. | The person, once, in the cursor.com sign-in prompt. | | ChatGPT Dots and background tasks | Add the [Graphify plugin](/integrations/chatgpt). | The person, when they connect the plugin. While a Dot works in the background, connected apps stay read-only, so `remember` and `set_workspace` wait for approval. | -| Clients without remote OAuth | The [`mcp-remote` bridge](/platform/hosted-mcp#clients-without-remote-oauth) runs the sign-in and stores the credentials on that machine. | The person, once, on that machine. | +| Clients without remote OAuth | The [`mcp-remote` bridge](/platform/graphify-mcp#clients-without-remote-oauth) runs the sign-in and stores the credentials on that machine. | The person, once, on that machine. | Full step-by-step setup for cloud agents: [Connect cloud coding agents](/cookbooks/cloud-coding-agents). @@ -44,7 +44,7 @@ Use open-source Graphify instead. Your own infrastructure holds the graph, and y ## Limits to plan for -- 240 requests a minute per client IP and a 256 KB request body. Back off on `429`. See [Hosted MCP limits](/platform/hosted-mcp#hosted-mcp-limits). +- 240 requests a minute per client IP and a 256 KB request body. Back off on `429`. See [Graphify MCP limits](/platform/graphify-mcp#limits). - `set_workspace` binds a session for 24 hours by default. A bot that runs longer should call `list_workspaces` to check which workspace is active. - The graph reflects the last indexed snapshot of the default branch. See [Keep answers fresh](/agents/overview#keep-answers-fresh). @@ -54,7 +54,7 @@ Use open-source Graphify instead. Your own infrastructure holds the graph, and y Connect, pick the right tool, and handle sign-in. - + Setup, sign-in, workspaces and limits. diff --git a/agents/overview.mdx b/agents/overview.mdx index cd11242..c8c00c1 100644 --- a/agents/overview.mdx +++ b/agents/overview.mdx @@ -61,7 +61,7 @@ Rules for the results: The tools don't edit source files, but two of them change stored state on purpose. Ask the user first: - `remember` saves a note to the workspace's shared [Memory](/platform/memory). Save only what the user asked you to save. -- `set_workspace` changes which workspace, and so which repositories, the session reads. With `make_default`, it also changes the user's default. See [Hosted MCP](/platform/hosted-mcp#workspaces-and-mcp-sessions). +- `set_workspace` changes which workspace, and so which repositories, the session reads. With `make_default`, it also changes the user's default. See [Graphify MCP](/platform/graphify-mcp#workspaces-and-mcp-sessions). In workspaces with trail capture turned on, `search`, `query_graph`, `graphify_find`, `graphify_trace`, `graphify_rank_files` and an unscoped `recall` can also save the question you asked to workspace memory. They never change source code. @@ -96,7 +96,7 @@ If `list_repositories` succeeds but is empty, sign-in worked and no repository i Test prompts and fixes per client. - + Sign-in, workspaces, limits and errors. diff --git a/agents/recipes.mdx b/agents/recipes.mdx index 9759238..183ba49 100644 --- a/agents/recipes.mdx +++ b/agents/recipes.mdx @@ -9,7 +9,7 @@ icon: "list-checks" import { PromptBlock } from '/snippets/hero-install.jsx'; -Paste these prompts into any agent connected to Graphify. Each one names the tool it should trigger, so you can check that the agent used the graph instead of searching files one by one. Not connected yet? Use [Connect to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=graphify&config=eyJ1cmwiOiJodHRwczovL2FwaS5ncmFwaGlmeS5jb20vbWNwIn0%3D), the [Graphify extension for VS Code](https://marketplace.visualstudio.com/items?itemName=graphify-labs.graphify-mcp), the [Graphify plugin for ChatGPT and Codex](https://chatgpt.com/plugins/plugin_asdk_app_6abe89f7f5d88191b9422522bb8562a4), or the [hosted MCP setup](/platform/hosted-mcp). +Paste these prompts into any agent connected to Graphify. Each one names the tool it should trigger, so you can check that the agent used the graph instead of searching files one by one. Not connected yet? Use [Connect to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=graphify&config=eyJ1cmwiOiJodHRwczovL2FwaS5ncmFwaGlmeS5jb20vbWNwIn0%3D), the [Graphify extension for VS Code](https://marketplace.visualstudio.com/items?itemName=graphify-labs.graphify-mcp), the [Graphify plugin for ChatGPT and Codex](https://chatgpt.com/plugins/plugin_asdk_app_6abe89f7f5d88191b9422522bb8562a4), or [Graphify MCP](/platform/graphify-mcp). Hosted Graphify lists 63 grammars. Open-source Graphify supports 40 languages (33 tree-sitter, 7 built-in). diff --git a/changelog/platform.mdx b/changelog/platform.mdx index 8e60ec6..569f32b 100644 --- a/changelog/platform.mdx +++ b/changelog/platform.mdx @@ -12,7 +12,7 @@ icon: "cloud" ## Find Graphify with an MCP server card ### New -- **MCP:** Graphify now publishes an MCP Server Card at `https://api.graphify.com/mcp/server-card`, plus an AI Catalog that lists it. MCP apps and directories that read server cards can find Graphify and set it up before you connect. See [Hosted MCP](/platform/hosted-mcp#let-clients-find-graphify-with-a-server-card). +- **MCP:** Graphify now publishes an MCP Server Card at `https://api.graphify.com/mcp/server-card`, plus an AI Catalog that lists it. MCP apps and directories that read server cards can find Graphify and set it up before you connect. See [Graphify MCP](/platform/graphify-mcp#server-card-vs-the-mcp-connection). diff --git a/cookbooks/agent-team-one-graph.mdx b/cookbooks/agent-team-one-graph.mdx index 8bdc3f9..70e3570 100644 --- a/cookbooks/agent-team-one-graph.mdx +++ b/cookbooks/agent-team-one-graph.mdx @@ -38,7 +38,7 @@ A solo founder runs one product across three repositories: a web app, an API and ## Before you start - Your repositories indexed in one [Graphify](https://app.graphify.com) workspace. -- The agents you use. Setup for each client is in [Hosted MCP](/platform/hosted-mcp). +- The agents you use. Setup for each client is in [Graphify MCP](/platform/graphify-mcp). ## Setup diff --git a/cookbooks/cross-repo-dependencies.mdx b/cookbooks/cross-repo-dependencies.mdx index affc9eb..9f188dc 100644 --- a/cookbooks/cross-repo-dependencies.mdx +++ b/cookbooks/cross-repo-dependencies.mdx @@ -106,7 +106,7 @@ Every agent on the team reads the same combined graph through one server. For Cl claude mcp add --transport http --scope user graphify https://api.graphify.com/mcp ``` -Start Claude Code, run `/mcp`, select **graphify**, and choose **Authenticate**. For Codex, Cursor, VS Code and other clients, see [Hosted MCP](/platform/hosted-mcp). If the `claude` command isn't available, as in the Claude desktop app, see [Claude Code](/integrations/claude-code). +Start Claude Code, run `/mcp`, select **graphify**, and choose **Authenticate**. For Codex, Cursor, VS Code and other clients, see [Graphify MCP](/platform/graphify-mcp). If the `claude` command isn't available, as in the Claude desktop app, see [Claude Code](/integrations/claude-code). Check the agent can see the combined graph: @@ -291,7 +291,7 @@ Your repositories now share one graph. Any agent on the team can ask what a chan Combined graph limits, states and the impact view. - + Connect Codex, Cursor, VS Code and other agents. diff --git a/cookbooks/document-the-why.mdx b/cookbooks/document-the-why.mdx index 8f9b326..827ac7f 100644 --- a/cookbooks/document-the-why.mdx +++ b/cookbooks/document-the-why.mdx @@ -31,7 +31,7 @@ import TryCloudCard from '/snippets/try-cloud-card.mdx'; ## Before you start -- A repository indexed in [Graphify](https://app.graphify.com), with your coding agent connected to the [hosted MCP server](/platform/hosted-mcp). The open-source [Graphify CLI](/open-source/overview) works too. +- A repository indexed in [Graphify](https://app.graphify.com), with your coding agent connected to the [hosted MCP server](/platform/graphify-mcp). The open-source [Graphify CLI](/open-source/overview) works too. - Access to your git history and issue tracker. ## Why AI coding agents "fix" code that isn't broken diff --git a/cookbooks/make-agents-use-the-graph.mdx b/cookbooks/make-agents-use-the-graph.mdx index b88ee52..21b63de 100644 --- a/cookbooks/make-agents-use-the-graph.mdx +++ b/cookbooks/make-agents-use-the-graph.mdx @@ -109,7 +109,7 @@ Agents follow the instruction file they read at the start of every session: `CLA session isn't in it yet, so read your own edits from disk. ``` - To save the agent a lookup, you can set a default repository on the server URL instead, such as `https://api.graphify.com/mcp?repo=acme/web-app`. See [Hosted MCP](/platform/hosted-mcp). + To save the agent a lookup, you can set a default repository on the server URL instead, such as `https://api.graphify.com/mcp?repo=acme/web-app`. See [Graphify MCP](/platform/graphify-mcp). Let Graphify write the block for you. In the repository root: @@ -327,7 +327,7 @@ Your agent now has a specific rule for when to call Graphify, a reminder at the Combine repositories and ask what a change breaks. - + Every hosted tool, limits and client setup. diff --git a/cookbooks/read-your-graph.mdx b/cookbooks/read-your-graph.mdx index 9ad51ae..beb9590 100644 --- a/cookbooks/read-your-graph.mdx +++ b/cookbooks/read-your-graph.mdx @@ -113,7 +113,7 @@ Open a finding and select **Copy task for my agent**. Use **Preview or edit the The copied task tells your agent not to delete code, apply a change, open a pull request, or merge anything without your separate instruction. It asks the agent to return its investigation and a proposed next step first. Paste it into your agent, read what it finds, and only then approve the change. -For your agent to check callers against the graph while it works, connect it to the [hosted MCP server](/platform/hosted-mcp) and follow [Make your agent use the graph](/cookbooks/make-agents-use-the-graph). +For your agent to check callers against the graph while it works, connect it to the [hosted MCP server](/platform/graphify-mcp) and follow [Make your agent use the graph](/cookbooks/make-agents-use-the-graph). ## When it goes wrong diff --git a/cookbooks/reuse-existing-code.mdx b/cookbooks/reuse-existing-code.mdx index 6b1798a..08b1e20 100644 --- a/cookbooks/reuse-existing-code.mdx +++ b/cookbooks/reuse-existing-code.mdx @@ -112,7 +112,7 @@ Ask the agent at the end of the session which Graphify tools it called and what Get agents to query Graphify before they grep. - + Every hosted tool and client setup. diff --git a/docs.json b/docs.json index 1380c69..597ecfb 100644 --- a/docs.json +++ b/docs.json @@ -26,6 +26,7 @@ "platform/overview", "platform/how-it-works", "platform/quickstart", + "platform/graphify-mcp", "platform/verify-connection", "concepts/index-a-repository", "platform/keep-the-graph-fresh", @@ -65,8 +66,7 @@ "platform/wiki", "platform/memory", "platform/learning", - "platform/connectors", - "platform/hosted-mcp" + "platform/connectors" ] }, { @@ -671,6 +671,10 @@ { "source": "/platform/google-drive", "destination": "/integrations/google-drive" + }, + { + "source": "/platform/hosted-mcp", + "destination": "/platform/graphify-mcp" } ] } diff --git a/for-agents.mdx b/for-agents.mdx index bec322b..636de9e 100644 --- a/for-agents.mdx +++ b/for-agents.mdx @@ -25,7 +25,7 @@ This page holds the full rules. Every page's Markdown, [llms.txt](https://docs.g ## Which surface - **Graphify CLI** is the open-source `graphifyy` package on the machine: the skill, the CLI, and the ten-tool MCP server. Its pages are the Graphify CLI tab (`/open-source/`) and the skill setup tabs in Integrations. -- **Graphify** is the hosted workspace and `https://api.graphify.com/mcp` (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (`/platform/`, `/concepts/`) and the Hosted MCP and CI groups in Integrations. +- **Graphify** is the hosted workspace and `https://api.graphify.com/mcp` (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (`/platform/`, `/concepts/`), including [Graphify MCP](/platform/graphify-mcp), and the coding-agent and CI pages in Integrations. - Everything else, including Cookbooks (`/cookbooks/`), `/mcp/docs-search`, and `/platform/graphify-vs-local`, applies to both. - Each page's source frontmatter records its surface as `surface: local`, `cloud`, or `both`. - In llms.txt, tell the surface from the path: `/platform/` and `/concepts/` are Graphify, `/open-source/` is Graphify CLI. Most `/integrations/` pages cover both, with a Graphify tab and a Graphify CLI tab. @@ -97,7 +97,7 @@ Default to Graphify, the hosted product. It needs no local build: the user signs A new server loads only when a session starts. Tell the user to start a new Claude Code session, run `/mcp`, select **graphify**, and finish the sign-in in the browser. Run step 3 in that new session. - Other MCP clients: add a remote (Streamable HTTP) server at `https://api.graphify.com/mcp` and complete the browser sign-in. No API key is needed. See [Integrations](/integrations/overview) for every agent. + Other MCP clients: add a remote (Streamable HTTP) server at `https://api.graphify.com/mcp` and complete the browser sign-in. No API key is needed. See [Graphify MCP](/platform/graphify-mcp) for the endpoint, auth, and client setup, and [Integrations](/integrations/overview) for every agent. 3. Check the connection with this prompt: diff --git a/index.mdx b/index.mdx index 725b84f..01a543e 100644 --- a/index.mdx +++ b/index.mdx @@ -46,7 +46,7 @@ import { HeroInstall, PromptBlock } from '/snippets/hero-install.jsx';

Graphify for agents

How agents use Graphify →
    -
  • Hosted MCP serverAdd https://api.graphify.com/mcp to any MCP client. Sign in with OAuth, no API key.Hosted MCP →
    • +
  • Graphify MCPAdd https://api.graphify.com/mcp to any MCP client. Sign in with OAuth, no API key.Graphify MCP →
  • Plugins and one-click installsInstall in Cursor, the VS Code extension, or the Graphify plugin for ChatGPT and Codex.Integrations →
  • Graphify CLIRun open-source Graphify on your machine and keep the graph in your own files.CLI quickstart →
diff --git a/llms.txt b/llms.txt index 55f78e9..67e476d 100644 --- a/llms.txt +++ b/llms.txt @@ -19,11 +19,12 @@ Start here for an overview of Graphify. ## Graphify: Get started -Use when setting up hosted Graphify: sign in, index a repository, and connect an agent. +Use when setting up hosted Graphify: sign in, index a repository, and connect an agent through Graphify MCP. - [Graphify overview: hosted code knowledge graph](https://docs.graphify.com/platform/overview.md): Explore graphs, Wiki, pull request reviews, formal verification, Learning and shared agent memory in your hosted Graphify workspace. - [How Graphify works](https://docs.graphify.com/platform/how-it-works.md): What happens between connecting a repository and your agent asking the graph a question: indexing, updates, and the hosted MCP server. - [Graphify in 5 minutes](https://docs.graphify.com/platform/quickstart.md): Get started with hosted Graphify in 5 minutes: sign in, index a GitHub repository, and ask your coding agent about it through the hosted MCP server. +- [Graphify MCP: connect your coding agent](https://docs.graphify.com/platform/graphify-mcp.md): Connect Claude Code, Cursor, Codex, or VS Code to Graphify over MCP with OAuth. Endpoint, tools, workspaces, limits, and fixes. - [Check your agent is using Graphify](https://docs.graphify.com/platform/verify-connection.md): Confirm Cursor, Claude Code, Codex or VS Code is connected to Graphify, run three test prompts, and fix common setup problems. - [Index your first repository in Graphify](https://docs.graphify.com/concepts/index-a-repository.md): Connect a GitHub or GitLab repository to Graphify, switch on indexing, and confirm the build finished so your agent can query the graph. - [How Graphify keeps your graph fresh](https://docs.graphify.com/platform/keep-the-graph-fresh.md): Graphify rebuilds your code graph on every push to the default branch, re-processing only the files that changed. See what triggers a build and when. @@ -46,7 +47,7 @@ Use when explaining how the graph answers questions about code, and how to read ## Graphify: Features -Use when the user asks about a hosted feature: Ask, graphs, reviews, verification, Wiki, Memory, connectors or the hosted MCP server. +Use when the user asks about a hosted feature: Ask, graphs, reviews, verification, Wiki, Memory, or connectors. - [Ask your codebase: answers with citations](https://docs.graphify.com/platform/ask.md): Ask your codebase plain-language questions. Graphify answers with cited graph nodes and paths, handles PR questions, and abstains without a path. - [Code knowledge graph: explore and query repos](https://docs.graphify.com/platform/graphs.md): Explore and query Graphify's code knowledge graph, see what a change affects, and combine up to 100 repositories into one cross-repo workspace graph. @@ -62,7 +63,6 @@ Use when the user asks about a hosted feature: Ask, graphs, reviews, verificatio - [Agent memory for coding agents](https://docs.graphify.com/platform/memory.md): Explore the facts your coding agents remember about a repository, organized by code entity, with provenance and graph anchors behind every fact. - [Learning: tune AI code review findings](https://docs.graphify.com/platform/learning.md): Teach Graphify which review findings matter with @graphify wrong, good, and suppress. Learning reduces noise and never changes verification results. - [Connectors: agents, code hosts and tools](https://docs.graphify.com/platform/connectors.md): Connect coding agents over MCP and connect source providers, docs, issue trackers, and CI to Graphify from the Connectors page in the Console. -- [Hosted MCP server for code graphs, with OAuth](https://docs.graphify.com/platform/hosted-mcp.md): Connect Claude Code, Cursor, Codex, or VS Code to Graphify's hosted MCP server with OAuth sign-in. Tools, workspaces, 240/min limit, errors. ## Graphify: Workspace diff --git a/platform/ask.mdx b/platform/ask.mdx index 150eea1..2447314 100644 --- a/platform/ask.mdx +++ b/platform/ask.mdx @@ -129,7 +129,7 @@ When the box is empty, Ask may show up to four questions under **Suggested from No. Both modes only read the graph. **Plan a change** produces a plan with links, not edits. - Yes. Connect it to the [hosted MCP](/platform/hosted-mcp) and it queries the same graph. + Yes. Connect it to the [hosted MCP](/platform/graphify-mcp) and it queries the same graph. Ask doesn't carry hidden assumptions between questions. Name the symbol or module again in a follow-up so the graph search starts from the right place. diff --git a/platform/connectors.mdx b/platform/connectors.mdx index a696c5a..2208b38 100644 --- a/platform/connectors.mdx +++ b/platform/connectors.mdx @@ -22,7 +22,7 @@ import HostedMcpCard from '/snippets/hosted-mcp-card.mdx'; ## The MCP tab -Pick your coding agent and follow its setup. The tab fills in your endpoint and shows the config file to edit. See [Hosted MCP](/platform/hosted-mcp) for each client. +Pick your coding agent and follow its setup. The tab fills in your endpoint and shows the config file to edit. See [Graphify MCP](/platform/graphify-mcp) for each client. ## The Integrations tab @@ -164,7 +164,7 @@ Tiles that aren't available for your workspace show **Coming soon**. ## What's next - + Connect a coding agent. diff --git a/platform/hosted-mcp.mdx b/platform/graphify-mcp.mdx similarity index 61% rename from platform/hosted-mcp.mdx rename to platform/graphify-mcp.mdx index 690b502..1526d20 100644 --- a/platform/hosted-mcp.mdx +++ b/platform/graphify-mcp.mdx @@ -1,36 +1,35 @@ --- -title: "Hosted MCP server for code graphs, with OAuth" -sidebarTitle: "Hosted MCP" -description: "Connect Claude Code, Cursor, Codex, or VS Code to Graphify's hosted MCP server with OAuth sign-in. Tools, workspaces, 240/min limit, errors." -keywords: ["graphify mcp", "hosted mcp server", "mcp oauth", "code graph mcp", "claude code mcp", "cursor mcp", "codex mcp", "remote mcp server", "mcp server card", "mcp registry"] +title: "Graphify MCP: connect your coding agent" +sidebarTitle: "Graphify MCP" +description: "Connect Claude Code, Cursor, Codex, or VS Code to Graphify over MCP with OAuth. Endpoint, tools, workspaces, limits, and fixes." +keywords: ["graphify mcp", "mcp server", "remote mcp server", "mcp oauth", "code graph mcp", "claude code mcp", "cursor mcp", "hosted mcp", "mcp server card"] surface: "cloud" -icon: "cloud" +icon: "plug" --- import TryCloudCard from '/snippets/try-cloud-card.mdx'; -The **hosted MCP** server gives your coding agent the same graph you see in the Graphify app. Instead of grepping through files, your agent asks Graphify for the entities, relationships, and paths it needs, and gets grounded answers for a fraction of the tokens. +Graphify MCP is the hosted Model Context Protocol server for your indexed repositories. Your coding agent queries the same code graph you see in the console: find symbols, follow callers, check impact, recall team memory, and read review status. Nothing runs on your machine. Sign in with OAuth. There is no API key to paste. ```text https://api.graphify.com/mcp ``` -You sign in with OAuth from your client. There's no API key to paste. +| | | +| --- | --- | +| **Transport** | Streamable HTTP | +| **Auth** | OAuth (browser sign-in, PKCE). No API key in the URL or config. | +| **Scope** | `graphify:query` | +| **When to use it** | This server. Use the [local MCP server](/open-source/mcp-server) for an offline or on-machine graph. | + +Main setup lives in the console under **Connectors → MCP**. That page fills in the endpoint, shows **Agent connection status**, and offers starter tasks under **Try it on your repository** once a repository is indexed. -**Use the hosted MCP when** your repositories are indexed in Graphify and you want every agent on your team to use the same graph. To run a server on your own graph, see the [local MCP server](/open-source/mcp-server). +You need a Graphify account at [app.graphify.com](https://app.graphify.com), at least one indexed repository, and an MCP client that supports remote HTTP servers. Hosted Graphify lists 63 grammars. -## Before you start - -- A Graphify account at [app.graphify.com](https://app.graphify.com). -- At least one indexed repository. Hosted Graphify lists 63 grammars. -- An MCP client that supports remote HTTP servers. - ## Connect your client -The **MCP** tab under **Connectors** in Graphify shows the setup for your client, with your endpoint filled in. - One-click installs: [Connect to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=graphify&config=eyJ1cmwiOiJodHRwczovL2FwaS5ncmFwaGlmeS5jb20vbWNwIn0%3D), the [Graphify extension for VS Code](https://marketplace.visualstudio.com/items?itemName=graphify-labs.graphify-mcp), or the [Graphify plugin for ChatGPT and Codex](https://chatgpt.com/plugins/plugin_asdk_app_6abe89f7f5d88191b9422522bb8562a4). @@ -112,7 +111,7 @@ One-click installs: [Connect to Cursor](cursor://anysphere.cursor-deeplink/mcp/i -Graphify also has setup for VS Code, Windsurf, Cline, Continue, JetBrains, Zed, Goose, Kiro, and other clients, including one-click install links where a client supports them. +Graphify also has setup for Windsurf, Cline, Continue, JetBrains, Zed, Goose, Kiro, and other clients, including one-click install links where a client supports them. See [Integrations](/integrations/overview). ### Clients without remote OAuth @@ -131,7 +130,7 @@ For a client that only runs local (stdio) servers, use the pinned `mcp-remote` b Use your client's native remote connection when it supports Graphify's sign-in. The bridge is a third-party package. -## Scope it to one repository +## Target a repository or group Add `?repo=` with the repository's full name to set a default: @@ -139,15 +138,29 @@ Add `?repo=` with the repository's full name to set a default: https://api.graphify.com/mcp?repo=acme/payments ``` +### 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 the console, 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 console. + ## What your agent can do -Your client builds its tool list from the server's `tools/list` response, so the client's tool panel always shows the current set. The repository tools, such as `list_repositories`, come from the indexed graph. Graphify also adds these tools to every session: +Your client builds its tool list from the server's `tools/list` response, so the client's tool panel always shows the current set. Repository tools such as `list_repositories`, `query_graph`, `graphify_find`, callers, impact, and memory come from the indexed graph. For the job-to-tool map and pasteable prompts, see [What your agent can do](/agents/capabilities) and [Use Graphify from your agent](/agents/recipes). -| Tool | Arguments | Behavior | -| --- | --- | --- | -| `list_workspaces` | None | Lists the workspaces you belong to and marks the active one. Read-only. | -| `set_workspace` | `handle` (string, required), `make_default` (boolean, optional) | Switches the session to that workspace. With `make_default`, the choice persists. Marked as a state-changing tool, so most clients ask before running it. | -| `review_status` | `repository` (string, optional), `pr_number` (integer, optional) | Read-only. Returns how Graphify's review of a pull request went. Pass `pr_number` for one PR. Omit it to list the 10 most recent reviews. Does not start or re-run a review. | +Graphify also adds these workspace and review tools to every session: + +| Tool | What it does | +| --- | --- | +| `list_workspaces` | Lists the workspaces you belong to and marks the active one. No arguments. Read-only. | +| `set_workspace` | `handle` (required) switches the session to that workspace. `make_default` (optional) also saves it as your default. State-changing, so most clients ask before running it. | +| `review_status` | `repository` and `pr_number` are optional. Pass `pr_number` for one PR, or omit it for the 10 most recent reviews. Read-only. Does not start or re-run a review. | Changing workspace changes which repositories the session can see. It doesn't change your code or the graph. @@ -157,25 +170,15 @@ For one PR, the tool returns a `review` object (or `null` with a message if Grap Each review includes the repository, PR number and title, status (`queued`, `running`, `completed`, `failed`, or `cancelled`), and whether a newer push superseded it. A completed review also includes: -- **`gate`:** `pass` or `advisory` +- **`gate`:** `pass` or `advisory` (not a `passed` field) - **Finding counts:** `blocking_count`, `advisory_count`, and `findings_total` - **`top_findings`:** up to five findings, worst severity first -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. +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 about 20 to 30 minutes instead of polling continuously. See [Pull request reviews](/platform/reviews). -See [Graph explorer](/platform/graphs) for how to build and open a combined graph in the UI. + -## How hosted MCP sign-in works +## How sign-in works You don't paste a key. Your client discovers the sign-in flow from the server: @@ -186,50 +189,50 @@ You don't paste a key. Your client discovers the sign-in flow from the server: If a token doesn't verify, you get the same discovery `401`, and your client starts the sign-in again. -## Let clients find Graphify with a server card + -**Your client can find Graphify on its own.** Graphify publishes an [MCP server card](https://modelcontextprotocol.io/seps/2127-mcp-server-cards): a small public JSON file that says what the server is and where to connect. A client can read it before it connects or signs in, so you don't have to type the server URL. +## Server card vs the MCP connection - - - `https://api.graphify.com/mcp/server-card`. Who the server is and where to reach it. - - - `https://api.graphify.com/.well-known/ai-catalog.json`. Lists the server card, so a client that only knows the domain can find it. - - +**Your client can find Graphify on its own.** Graphify publishes an [MCP server card](https://modelcontextprotocol.io/seps/2127-mcp-server-cards): a small public JSON file that says what the server is and where to connect. A client can read it before it connects or signs in, so you don't have to type the server URL. -### When a client uses it +The server card is discovery only. It is not the MCP connection, and it does not list your tools. After connect and OAuth, your client gets tools from `tools/list`. Clients that don't read server cards keep working with the setup steps above. - - - A client or registry reads the AI catalog at `api.graphify.com`, or goes straight to the server card. - - - It reads the name, icon and remote URL from the card and adds Graphify for you. - - - It connects to `https://api.graphify.com/mcp`, runs the [OAuth sign-in](#how-hosted-mcp-sign-in-works), then gets your tools from `tools/list`. - - - -Clients that don't read server cards keep working with the setup steps above. +| Endpoint | What it is | +| --- | --- | +| `https://api.graphify.com/mcp/server-card` | Server card: name, icon, remote URL | +| `https://api.graphify.com/.well-known/ai-catalog.json` | AI catalog entry that points at the card | +| `https://api.graphify.com/mcp` | The actual MCP endpoint your client calls | ### What's in the card -| Field | Value | What it's for | -| --- | --- | --- | -| `name` | `io.github.Graphify-Labs/graphify` | Unique ID. Matches the MCP Registry entry. | -| `title` | `Graphify` | The name a client shows you. | -| `description` | What the server does | Shown next to the name. | -| `version` | Version number, such as `0.1.1` | Which release of the listing this is. | -| `remotes` | `streamable-http` at `https://api.graphify.com/mcp` | Where and how to connect. | -| `icons` | 400×400 PNG logo | The icon a client shows. | -| `websiteUrl` | `https://graphify.com/mcp` | Where to learn more. | -| `repository` | `github.com/Graphify-Labs/graphify-mcp` | Where the server code lives. | +| Field | Value | +| --- | --- | +| `name` | `io.github.Graphify-Labs/graphify`. Unique ID. Matches the MCP Registry entry. | +| `title` | `Graphify`. The name a client shows you. | +| `description` | Search indexed code, trace dependencies, assess change impact, and recall repository memory. | +| `version` | Version number, such as `0.1.1`. Which release of the listing this is. | +| `remotes` | `streamable-http` at `https://api.graphify.com/mcp`. Where and how to connect. | +| `icons` | 400×400 PNG logo. The icon a client shows. | +| `websiteUrl` | `https://graphify.com/mcp`. Where to learn more. | +| `repository` | `github.com/Graphify-Labs/graphify-mcp`. Where the server code lives. | The AI catalog has one entry, `urn:air:graphify.com:mcp:graphify`, of type `application/mcp-server-card+json`, pointing at the server card. +```bash +curl -H "Accept: application/mcp-server-card+json" https://api.graphify.com/mcp/server-card +``` + +### Other discovery endpoints + +These public files tell a client how to sign in. Your client reads them for you. + +| Endpoint | What it describes | +| --- | --- | +| `/.well-known/oauth-protected-resource/mcp` | The MCP server, its sign-in server, and the `graphify:query` scope. | +| `/.well-known/oauth-authorization-server` | Sign-in, token, registration, and revoke URLs, with PKCE (`S256`). Also at `/.well-known/openid-configuration`. | + +All are on `https://api.graphify.com` and are cached for an hour. + Your tools depend on your workspace, so a public file can't list them. Your client gets them from `tools/list` after you sign in. @@ -240,26 +243,8 @@ The AI catalog has one entry, `urn:air:graphify.com:mcp:graphify`, of type `appl Yes. The card and catalog allow any origin (`Access-Control-Allow-Origin: *`), are cached for an hour, and send an `ETag`. Send it back in `If-None-Match` and you get `304 Not Modified` if nothing changed. - - ```bash - curl -H "Accept: application/mcp-server-card+json" https://api.graphify.com/mcp/server-card - ``` - - You get back JSON with the server's name and remote URL. - -### Other discovery endpoints - -These public files tell a client how to sign in. Your client reads them for you. - -| Endpoint | What it describes | -| --- | --- | -| `/.well-known/oauth-protected-resource/mcp` | The MCP server, its sign-in server and the `graphify:query` scope. | -| `/.well-known/oauth-authorization-server` | Sign-in, token, registration and revoke URLs, with PKCE (`S256`). Also at `/.well-known/openid-configuration`. | - -All are on `https://api.graphify.com` and are cached for an hour. - ## Workspaces and MCP sessions Every request runs in one workspace. Graphify picks it in this order: the workspace bound to this MCP session, then your default workspace, then your only workspace if you belong to just one. @@ -282,7 +267,9 @@ Every request runs in one workspace. Graphify picks it in this order: the worksp | `mcp_session_required` | "set_workspace can only run inside an established MCP session." Reconnect the client, then retry. | | `invalid_arguments` | "set_workspace requires a handle." | -## Hosted MCP limits + + +## Limits | Limit | Default | | --- | --- | @@ -313,49 +300,31 @@ The request limit is counted per client IP address for signed-in sessions. Over Seeing the tools doesn't prove repository access. The last step does. For test prompts per client, see [Check your agent is using Graphify](/platform/verify-connection). -### Fix common problems +## Fix common problems - - - Run the client's sign-in step: `/mcp` → Authenticate, or `codex mcp login graphify`. - - - You're signed in, but the account's email isn't verified yet. Open the verification link Graphify emailed you (or use **Resend the verification email**), then connect again from your client. If you signed up with Google or GitHub, choose that option when you connect. - - - You're in a workspace with no indexed repositories. Switch with `set_workspace`. - - - Check in Graphify that it finished indexing, and that you're in the right workspace (`list_workspaces`). - - - Turn the tools on in your client and check that your model can call tools. In Copilot, add `"tools": ["*"]` to its config. - - - Add `https://api.graphify.com/mcp` directly. The MCP Registry listing (`io.github.Graphify-Labs/graphify`) and gallery inclusion are separate. - - - Install Node.js where the client can find it, or use the client's native remote setup. - - - Copilot's coding agent and code review only support static header credentials, not OAuth sign-in, so they can't use this endpoint yet. - - - No. It serves the indexed graph. For uncommitted work, use the [local MCP server](/open-source/mcp-server). - - +| What you see | What to do | +| --- | --- | +| Needs authentication / Needs login | You are connected, not signed in. Claude Code: `/mcp` → **Authenticate**. Codex: `codex mcp login graphify`. Cursor and VS Code: finish the browser sign-in. | +| Verify your email to connect | The account email isn't verified. Open the verification email, or select **Resend the verification email**, then connect again. Google or GitHub sign-up: choose that option when you connect. | +| `list_repositories` is empty | You are in the wrong workspace, or it has no repositories. Switch with `set_workspace`, or index a repository. | +| A repository returns no results | It is not indexed, or you are in the wrong workspace. Wait for **Indexed** on **Repositories**, then confirm the workspace with `list_workspaces`. | +| Tools connect but chat can't run them | Turn Graphify tools on in the client, and check that the model can call tools. In Copilot, add `"tools": ["*"]`. | +| Graphify isn't in my client's MCP gallery | Gallery listing is separate from the registry. Add `https://api.graphify.com/mcp` directly. Registry id: `io.github.Graphify-Labs/graphify`. | +| `npx` or Node.js isn't found | The bridge needs Node. Install Node where the client can find it, or use the client's native remote setup. | +| Copilot on github.com can't connect | No OAuth support there yet. Copilot's coding agent and code review only support static header credentials, so they can't use this endpoint yet. | +| Does Graphify MCP see my local changes? | No. It serves the indexed graph. For uncommitted work, use the [local MCP server](/open-source/mcp-server). | ## What's next - - The same graph, in the Graphify app. + + Three prompts that prove the agent used Graphify. - - What your agents remember. + + Job-to-tool map and pasteable prompts. - - Run only the tests a change affects. + + The same graph, in the console. Setup for each agent. diff --git a/platform/graphs.mdx b/platform/graphs.mdx index e8f831b..a74b11c 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 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). +The console, Ask, and your [hosted MCP](/platform/graphify-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/graphify-mcp#query-a-repository-group). | Code | Status | Fix | | --- | --- | --- | diff --git a/platform/memory.mdx b/platform/memory.mdx index 2d1fbca..7f688fb 100644 --- a/platform/memory.mdx +++ b/platform/memory.mdx @@ -19,7 +19,7 @@ import HostedMcpCard from '/snippets/hosted-mcp-card.mdx'; - A Graphify account at [app.graphify.com](https://app.graphify.com). - An indexed repository. -- A coding agent connected through the [hosted MCP](/platform/hosted-mcp). Memories are written by agents, so a new repository has none. +- A coding agent connected through the [hosted MCP](/platform/graphify-mcp). Memories are written by agents, so a new repository has none. ## How it works @@ -66,7 +66,7 @@ Your agent can keep its own preferences and session notes. Graphify adds shared ## Tell your agent to use memory -Connected agents get three memory tools from the [hosted MCP server](/platform/hosted-mcp): `recall` searches what the workspace remembers, `memories_about` returns what's known about one file or symbol, and `remember` saves one fact. Most agents won't call them unless their instructions say when. Add a block like this to `AGENTS.md` or `CLAUDE.md` in the repository and commit it. Replace `acme/web-app` with the repository's name in Graphify. +Connected agents get three memory tools from the [hosted MCP server](/platform/graphify-mcp): `recall` searches what the workspace remembers, `memories_about` returns what's known about one file or symbol, and `remember` saves one fact. Most agents won't call them unless their instructions say when. Add a block like this to `AGENTS.md` or `CLAUDE.md` in the repository and commit it. Replace `acme/web-app` with the repository's name in Graphify. ```md AGENTS.md ## Graphify memory @@ -159,7 +159,7 @@ Search memory with plain words to find saved decisions, incidents and lessons. T ## What's next - + Connect the agents that write memory. diff --git a/platform/reviews.mdx b/platform/reviews.mdx index 7ff6406..0dfa17f 100644 --- a/platform/reviews.mdx +++ b/platform/reviews.mdx @@ -21,7 +21,7 @@ To review the current head after new commits, a repository owner, member, or col A review shows up in two places on the pull request: a review comment from the Graphify app, and a check run named **Graphify** on the reviewed commit. Formal verification posts its own check run, **Graphify Formal Verification**, and runs on every push. -Graphify doesn't push a message to your coding agent when a review lands. Your agent can ask for the result with the hosted MCP `review_status` tool: pass a PR number for one review, or omit it to get the 10 most recent. See [What your agent can do](/platform/hosted-mcp#what-your-agent-can-do). +Graphify doesn't push a message to your coding agent when a review lands. Your agent can ask for the result with the hosted MCP `review_status` tool: pass a PR number for one review, or omit it to get the 10 most recent. See [what review_status returns](/platform/graphify-mcp#what-review_status-returns). To wait on GitHub itself, point the agent at the **Graphify** check run and the review comments: diff --git a/platform/support/rate-limits.mdx b/platform/support/rate-limits.mdx index d51fd59..65c1091 100644 --- a/platform/support/rate-limits.mdx +++ b/platform/support/rate-limits.mdx @@ -24,7 +24,7 @@ These are the default limits on every plan. They may change as we tune the servi | MCP requests | 240/minute | | Test impact requests | 60/minute | -Ask, query, and test impact limits apply per workspace. The hosted MCP limit applies per client IP address. See [Hosted MCP limits](/platform/hosted-mcp#hosted-mcp-limits) and [Test impact analysis](/platform/test-impact#limits). +Ask, query, and test impact limits apply per workspace. The hosted MCP limit applies per client IP address. See [Graphify MCP limits](/platform/graphify-mcp#limits) and [Test impact analysis](/platform/test-impact#limits). ## Memory limits diff --git a/platform/support/troubleshooting.mdx b/platform/support/troubleshooting.mdx index 03c0570..eb249bd 100644 --- a/platform/support/troubleshooting.mdx +++ b/platform/support/troubleshooting.mdx @@ -28,7 +28,7 @@ Your client hasn't finished the one-time browser sign-in. Graphify answers a req - Codex: run `codex mcp login graphify`. - Cursor: select **Needs login** next to the server. -See [Hosted MCP](/platform/hosted-mcp#how-hosted-mcp-sign-in-works) for how sign-in works. +See [Graphify MCP](/platform/graphify-mcp#how-sign-in-works) for how sign-in works. ### "Verify your email to connect" @@ -44,7 +44,7 @@ The stored login is no longer valid. Sign out of the server in your client, then ### invalid_client_metadata: "Only public clients (auth method 'none') are supported." -Your client tried to register with a client secret. Graphify supports public OAuth clients only. Use the client's standard remote MCP setup, or the [`mcp-remote` bridge](/platform/hosted-mcp#clients-without-remote-oauth). +Your client tried to register with a client secret. Graphify supports public OAuth clients only. Use the client's standard remote MCP setup, or the [`mcp-remote` bridge](/platform/graphify-mcp#clients-without-remote-oauth). ### 429 on sign-in @@ -173,7 +173,7 @@ See [Graphify vs Graphify CLI](/platform/graphify-vs-local). Common questions. - + Setup and verification. diff --git a/platform/test-impact.mdx b/platform/test-impact.mdx index 1df38c3..aea4db0 100644 --- a/platform/test-impact.mdx +++ b/platform/test-impact.mdx @@ -108,7 +108,7 @@ Treat any `429` or `5xx` as "run everything". The [Buildkite script](/integratio How Graphify traces what a change touches. - + The same graph, for your coding agent. diff --git a/platform/verify-connection.mdx b/platform/verify-connection.mdx index 1eb6a41..14b1051 100644 --- a/platform/verify-connection.mdx +++ b/platform/verify-connection.mdx @@ -67,7 +67,7 @@ Then ask a code question without naming Graphify, such as `What calls | A Cursor cloud agent can't see Graphify | Cloud agents don't read your local `mcp.json`, and they keep their own sign-in. Add and sign in to Graphify for cloud agents at [cursor.com/agents](https://cursor.com/agents). | | Answers miss today's changes | Graphify serves the indexed default branch. Uncommitted work isn't in it. | -More fixes are in [Hosted MCP](/platform/hosted-mcp#fix-common-problems) and [Troubleshooting](/platform/support/troubleshooting). +More fixes are in [Graphify MCP](/platform/graphify-mcp#fix-common-problems) and [Troubleshooting](/platform/support/troubleshooting). ## Prove it after a session diff --git a/platform/workspaces-and-members.mdx b/platform/workspaces-and-members.mdx index 0813535..35a15f1 100644 --- a/platform/workspaces-and-members.mdx +++ b/platform/workspaces-and-members.mdx @@ -58,7 +58,7 @@ If a teammate already installed Graphify on your GitHub organization, connecting ## Switch workspaces -When you belong to more than one workspace, the sidebar workspace switcher lists every workspace you can open. Pick one to move there. Agents keep their own workspace selection over MCP with `list_workspaces` and `set_workspace`. See [Hosted MCP server](/platform/hosted-mcp). +When you belong to more than one workspace, the sidebar workspace switcher lists every workspace you can open. Pick one to move there. Agents keep their own workspace selection over MCP with `list_workspaces` and `set_workspace`. See [Graphify MCP](/platform/graphify-mcp). ## Last active on Members diff --git a/scripts/build-llms-txt.py b/scripts/build-llms-txt.py index 58a2dda..9cf25f0 100644 --- a/scripts/build-llms-txt.py +++ b/scripts/build-llms-txt.py @@ -26,9 +26,9 @@ WHEN_TO_USE = { ("Get Started", None): "Start here for an overview of Graphify.", - ("Graphify", "Get started"): "Use when setting up hosted Graphify: sign in, index a repository, and connect an agent.", + ("Graphify", "Get started"): "Use when setting up hosted Graphify: sign in, index a repository, and connect an agent through Graphify MCP.", ("Graphify", "Core concepts"): "Use when explaining how the graph answers questions about code, and how to read its edges.", - ("Graphify", "Features"): "Use when the user asks about a hosted feature: Ask, graphs, reviews, verification, Wiki, Memory, connectors or the hosted MCP server.", + ("Graphify", "Features"): "Use when the user asks about a hosted feature: Ask, graphs, reviews, verification, Wiki, Memory, or connectors.", ("Graphify", "Workspace"): "Use for repository indexing and sync, connected agents, contributors and profiles.", ("Graphify", "Support"): "Use for errors, rate limits, pricing, security, or moving from Graphify CLI to hosted Graphify.", ("Open Source", "Get started"): "Use only when the user wants open-source Graphify on their machine: install graphifyy, build a graph, or serve it over MCP.",