> ## Documentation Index
> Fetch the complete documentation index at: https://docs.graphify.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The PyPI package is graphifyy, with two y's. The command is graphify.
> /graphify . is typed in an assistant chat, not in a shell.
> Use only commands, flags, and endpoints shown on these pages. Do not invent one.
> Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. 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 Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> The official site is https://graphify.com. These docs are https://docs.graphify.com.
> The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server.
> Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough.

# Graphify vs Graphify Local

> Compare Graphify, the hosted product, with Graphify Local, the open-source graphifyy package. See how each builds, updates, and serves the graph, and which features need the hosted product.

Graphify is the hosted product. It indexes your repositories on GitHub or GitLab and serves the graph through `https://api.graphify.com/mcp`. Graphify Local is the open-source [`graphifyy`](https://github.com/Graphify-Labs) package. It builds the graph on your machine and writes it to `graphify-out/`.

Both give your assistant the same kind of code graph. They differ in where the graph is built, how it stays current, and what your team can do with it.

## Which one fits

> **[Choose Graphify](https://docs.graphify.com/platform/quickstart.md)**
>
> Your code is on GitHub or GitLab, and you want the graph kept current on every push, shared with your team, and used for pull request reviews.

> **[Choose Graphify Local](https://docs.graphify.com/open-source/quickstart.md)**
>
> The project exists only on your machine, or you want to build and keep the graph yourself with no account.

## Side by side

| Area | Graphify Local | Graphify |
| - | - | - |
| **Graph build** | `/graphify .` or `graphify extract` on your machine | Indexed from the default branch on GitHub or GitLab |
| **Updates** | `graphify update .`, `graphify watch .`, or git hooks | Each push to the default branch |
| **Connection** | `graphify-mcp` over stdio, with a path to `graph.json` | `https://api.graphify.com/mcp` over Streamable HTTP |
| **Sign-in** | None | OAuth in the browser, or an API token for CI |
| **Repository** | One `graph.json` for each entry, or `project_path` | `repository_id` on each call |
| **Tool names** | `get_node`, `get_neighbors`, and `shortest_path` with `source` and `target` | `graphify_node`, `graphify_callers`, and `shortest_path` with `src` and `tgt` |
| **Pull requests** | `list_prs`, `get_pr_impact`, and `triage_prs` through `gh` | Automatic reviews in **Reviews** |
| **Saved lessons** | `graphify-out/reflections/LESSONS.md` | **Memory** for each repository, shared with the workspace |
| **Change impact** | `graphify affected "<node>"` | `graphify_impact` and `impact_and_risk` |
| **Wiki** | `graphify export wiki` writes Markdown files | **Wiki** for each indexed repository, with search and questions |
| **Several repositories** | `graphify merge-graphs` or `graphify global add` | **Cross-Repository** in **Graphs** |
| **Team** | Each clone installs the skill and the hooks | **Members** in the user menu |

## Only in Graphify

* [Pull request reviews](https://docs.graphify.com/platform/reviews.md) against the indexed graph and the diff.
* [Learning](https://docs.graphify.com/platform/learning.md) from `@graphify wrong`, `good`, and `suppress` replies on reviews.
* [Formal verification](https://docs.graphify.com/platform/verification.md) of changed functions against their earlier implementation.
* [Agent memory](https://docs.graphify.com/platform/memory.md) shared by every assistant and teammate in the workspace.
* `graphify_tests_for` and `impact_and_risk`, which list the tests linked to a symbol and rank the files a change reaches.
* [Contributors](https://docs.graphify.com/platform/contributors.md), when it is available in your workspace.

## Switch later

You can start with Graphify Local and move a repository to Graphify at any time. It is a configuration change: your application code stays as it is, and the local graph keeps working until you switch each assistant. Follow [Move from Graphify Local](https://docs.graphify.com/platform/support/move-from-local.md).

[PreviousConsole tour](https://docs.graphify.com/platform/console.md)
[NextTrace who calls this](https://docs.graphify.com/platform/trace.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.