https://api.graphify.com/mcp. Open-source Graphify is the graphifyy 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
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 CLI
The project exists only on your machine, or you want to build and keep the graph yourself with no account.
Side by side
Only in Graphify
- Pull request reviews analyze the full pull request, from where it branched to its latest commit. They use the indexed graph to understand how the changes affect the surrounding code.
- Learning from
@graphify wrong,good, andsuppressreplies on reviews. - Formal verification of changed functions against their earlier implementation.
- Agent memory shared by every assistant and teammate in the workspace.
graphify_tests_for, andgraphify_impactwithinclude_risk, which list the tests linked to a symbol and rank hotspot files by linked-test coverage.- Contributors, when it is available in your workspace.
Does hosted Graphify have a search hook?
No. The open-source CLI installs Claude Code hooks that add graph context right before each grep, and strict mode can require a graph query first. The hosted MCP server athttps://api.graphify.com/mcp has no hook. On hosted, an instruction block in your assistant’s rules file does that job. Follow Step 2 of Make agents use the graph and keep the block short and specific.