Skip to main content
Ask your agent who calls a function, what it calls, or how one symbol reaches another. Graphify answers from the call edges in the graph of your indexed repository, so your agent follows real links instead of searching for names. Use this when you already know a symbol and want to see what is around it. If you don’t know where to start, ask a question about your code first.

Before you start

  • An account at app.graphify.com. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.
  • A repository with the status Indexed. See Repositories and builds.
  • Your agent connected to the hosted MCP server at https://api.graphify.com/mcp. See Code with an agent.

Follow callers and callees

Your agent uses these hosted tools: An empty result from graphify_callers means no call edge was indexed. It does not prove that nothing calls the symbol, for example when code is called dynamically or the index is out of date. If the name matches more than one definition, the tool refuses and lists the candidate ids. Pass an id to pick one.

Trace a path between two symbols

Local path command

The local graphify path command takes these options:

Read the result

A lookup can return a semantic suggestion when a name has no exact match. Check the labels and the resolved field (exact or semantic) before you trust it. Each edge also carries a confidence tag (EXTRACTED, INFERRED, or AMBIGUOUS). Edges and provenance explains each tag.

If something fails

Next steps

Try it in Graphify

We build and host the graph for you, and review your pull requests with it. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Check the impact of a change

See what a change reaches before you make it.

graphify path

Every option for the local command.