Skip to main content

​
Prerequisites

The standalone CLI works without an assistant. Code-only extraction does not require an API key.

​
Install the package

On Windows, a virtual environment’s executable is .venv\Scripts\python.exe. uv and pipx manage the environment for you.
The official PyPI package is graphifyy. Other similarly named packages are not the Graphify Labs package.

​
Register the skill

The first command detects an assistant; the second targets one explicitly. Run the specific command for each assistant you use. Use --project when you want the registration committed with a repository:
Read the installer’s list of files before committing them. Project and user registrations live in different locations.

​
Optional capabilities

Install only the extras your workflow needs. Quote bracketed names in zsh. Combine extras, for example uv tool install "graphifyy[mcp,watch]". If uv reports an existing installation, use its --reinstall option to replace that tool environment with the requested extras.

​
Upgrade

Re-run registration for the assistants you use so their skill files match the package. If you installed git hooks, run graphify hook install again after moving or reinstalling the Python environment.

​
Command not found

Then open a new terminal. With pipx, run pipx ensurepath. If an MCP client cannot find Graphify, use an absolute executable path in its configuration.

​
Remove a registration

graphify uninstall removes user registrations across platforms. The optional --purge flag also deletes graphify-out/; omit it to preserve your graph.