Skip to main content
Quick answers to the questions people ask most about Graphify, the hosted product. For the open-source CLI, see Troubleshooting.

Getting started

Graphify is hosted: it indexes your GitHub or GitLab repositories, rebuilds on each push to the default branch, reviews pull requests, and serves every repository through one MCP connection. Graphify Local is the free, open-source graphifyy package. It builds a graph on your machine, with no account. See Move from Graphify Local to switch.
GitHub and GitLab. Connect them from Repositories. GitHub Enterprise is part of Enterprise. A project that is only on your machine needs Graphify Local.
No. Every new account starts on a 14-day Pro trial. When the trial ends, the account moves to Free, which indexes up to 3 repositories and needs no card. See Plans and pricing.
The default branch. A push to another branch, or a pull request, does not change the repository graph. Pull requests get their own review against that graph.

Indexing and builds

Open Repositories and read the status.See Repositories and builds.
Open Builds, filter to the repository, and choose Retry on the latest failed build. On Repositories, a failed repository’s Options also offer Retry indexing. Both index the current head of the default branch, not the commit that failed.
Graphify indexes the default branch. Push the code there and wait for Indexed. Uncommitted work and other branches are not in the graph.

Plans and limits

A limit message does not mean the repository is empty. Compare plans on Plans and pricing.
It sent too many Ask, query, or MCP requests in a short time. Wait a few seconds and retry with exponential backoff. See Rate limits and plan limits.
No. Workspace allowances are shared across the workspace and do not multiply by seat count. Talk to Graphify before planning a larger rollout.

Reviews

When it is opened, reopened, or marked ready for review. To review the latest commits, a repository owner, member, or collaborator comments @graphify review on the pull request. See Pull request reviews.
Reply on the pull request with @graphify wrong <finding>, @graphify good <finding>, or @graphify suppress <rule>. That feedback tunes later reviews. See Learning.

Assistants and MCP

Add the hosted MCP server, https://api.graphify.com/mcp, and sign in with OAuth in the browser. Each integration page has the exact steps; start at Hosted MCP.
A local graphify entry is still active and wins over the hosted one. Remove it, then restart the assistant. See Move from Graphify Local.
Use an API token from the MCP tab of Connectors. Store it as a CI secret, never in the repository.
The workspace has more than one repository, so the call needs repository_id. Pass one of the names in the error, such as your-org/your-repo, or run list_repositories.

Data and security

No. Code goes to Graphify’s LLM subprocessors only to produce results, under terms that prohibit training. See Security and data handling.
Contact the Graphify team to request deletion or export. Content is kept until you delete it or close your account, then removed from active systems within 30 days.
Yes, with Enterprise, which is self-hosted and in early access. Graphify Local also runs entirely on your machine.

Still stuck

Ask in Discord. Teams and Enterprise workspaces also have a dedicated Slack support channel. For the open-source engine, open a GitHub issue. Include what you ran, the exact error, and the correlationId from an API error if there is one.

Next steps

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.

Repositories and builds

Index and rebuild repositories.

Troubleshooting Graphify Local

Fixes for the open-source package.