Choose your coding assistant - Graphify
Skip to main content
Graphify Cloud answers from repositories you have already indexed. The Cloud path uses the hosted MCP server at https://api.graphify.com/mcp. A local skill builds a graph on your machine.

Graphify Cloud

These installs talk to https://api.graphify.com/mcp. Sign in at app.graphify.com and wait until the repository status is Indexed. The graph stays in Graphify Cloud. The same list is the Graphify Cloud page in the sidebar.

Local skill

The package is graphifyy. The command is graphify. graphify install writes the skill into the assistant you name.

The common workflow

Replace cursor with the installer platform for your assistant. Restart or refresh the assistant if it does not discover the new skill immediately, then ask it to map the current repository with Graphify. Skill invocation differs by client. Slash commands are common; Codex also exposes skills through the $ picker. If a client does not show slash commands, explicitly ask it to use the installed Graphify skill.

Project or personal installation

The default registration is personal. Add --project for repository-local registration where supported. This makes the instructions reviewable in version control and lets a team share the setup. The installer adds platform-specific files and may install hooks or instructions that suggest querying the graph before reading source. It does not grant your assistant new permissions.

Local MCP server

Connect the graph MCP server for ten tools on a graph that already exists on your machine. You can use those tools with the skill, or on their own. Codex and OpenClaw each have a local skill and a Cloud install. Graphify with Codex is the local skill, and so is graphify install --platform claw on Other coding assistants. ChatGPT, Codex, and Dots and Graphify MCP for OpenClaw are the Cloud install. Other coding agents is the hosted server for every other MCP client.