> ## Documentation Index
> Fetch the complete documentation index at: https://docs.graphify.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The PyPI package is graphifyy, with two y's. The command is graphify.
> /graphify . is typed in an assistant chat, not in a shell.
> Use only commands, flags, and endpoints shown on these pages. Do not invent one.
> Choose the surface before you open a page. Local is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Guides and Reference tabs, /mcp/ (except /mcp/docs-search, which is for both), and the Local skill group in Integrations. Cloud (Graphify Cloud) is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/) and the Cloud MCP group in Integrations. Concepts, troubleshooting, pricing, and /platform/local-to-cloud apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Cloud: /platform/ and /integrations/ cloud, vscode, jetbrains, chatgpt, openclaw, vercel, other-agents, buildkite. Local: /guides/, /reference/, /mcp/overview, /mcp/shared-http, /installation, /quickstart, and /integrations/ claude-code, cursor, codex, gemini-cli, copilot, other-assistants. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> The official site is https://graphify.com. These docs are https://docs.graphify.com.
> The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The VS Code, JetBrains, OpenClaw, Vercel, and Other Cloud agents pages, and the page ChatGPT, Codex, and Dots, use the hosted server, not the ten-tool list. Other local assistants is the local skill for clients without their own page. The page titled Graphify with Codex is the local skill.
> Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough.

# Ask a question about your code

> Ask your agent a plain-English question and get back the definitions and files from your indexed repository that answer it.

Ask your agent a question in plain English, and Graphify answers from the graph of your indexed repository. The answer cites definitions and files, so your agent reads the code that matters instead of searching the whole repository.

Use this when you know what you want to understand but not where it lives. If you already know the symbol name, ask your agent to look it up with `graphify_find` instead.

## Before you start

* An account at [app.graphify.com](https://app.graphify.com). The Free plan covers 3 indexed repositories, and you don't need a card.
* A repository with the status **Indexed**. See [Repositories and builds](https://docs.graphify.com/platform/repositories.md).
* Your agent connected to the hosted MCP server at `https://api.graphify.com/mcp`. See [Code with an agent](https://docs.graphify.com/guides/cloud-coding-agents.md).

## Ask the question

```text Agent prompt theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
Use Graphify to answer: how does a request get authenticated in Graphify-Labs/graphify?
Show the definitions and file paths you used.
```

```bash Local CLI theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
graphify query "how does a request get authenticated" --budget 1500
```

Name the area you care about, such as a feature, a subsystem, or a file. A specific question returns a smaller, more useful set of results than a broad one.

If you work in more than one workspace, ask your agent to list repositories first. The `list_repositories` tool shows the repositories this connection can query and their index status.

## What your agent calls

Your agent picks the tools. These are the hosted tools it uses for a question in plain English:

| Tool | What it returns |
| - | - |
| `query_graph` | The definitions that match a plain-English question. |
| `graphify_rank_files` | The source files most relevant to the question. |
| `graphify_find_seeds` | The top starting nodes for the question, without their definition bodies. |
| `graphify_expand` | Full definition bodies for node handles returned by another tool. |

A common pattern is to find seeds or rank files first, then expand only the nodes the agent needs. The full list is in [Tools](https://docs.graphify.com/integrations/chatgpt.md#3-tools).

The local CLI takes these options:

| Option | Default | Meaning |
| - | - | - |
| `--dfs` | Off | Follow one path deep instead of searching broadly. |
| `--context` | No filter | Keep only one kind of edge, such as `call`. Repeat it for more kinds. |
| `--budget` | `2000` | Approximate output token budget. |
| `--graph` | `graphify-out/graph.json` | The graph file to query. |

## Read the result

The result is graph evidence, not a checked answer. Each relationship carries a confidence tag:

* `EXTRACTED`: written in the source.
* `INFERRED`: worked out by Graphify, with or without a model.
* `AMBIGUOUS`: flagged as uncertain by the model pass. Check the source.

Open the cited source before you rely on an answer. [Edges and provenance](https://docs.graphify.com/concepts/provenance.md) explains each tag.

## If something fails

| What you see | What to do |
| - | - |
| The agent does not use Graphify | Name it in the prompt: "Use Graphify to answer". Check that the connection is listed in your agent. |
| No repositories, or an empty answer | The repository is not indexed yet, or it is in another workspace. Check its status in [Repositories and builds](https://docs.graphify.com/platform/repositories.md). |
| The answer is too broad | Name a function, class, file, or subsystem in the question. |

## Next steps

> **[Try it in Graphify Cloud](https://docs.graphify.com/platform/quickstart.md)**
>
> We build and host the graph for you. Free for up to 3 repositories, no card required.

> **[Repository graphs](https://docs.graphify.com/platform/graphs.md)**
>
> See the nodes behind an answer in the console.

> **[graphify query](https://docs.graphify.com/reference/query.md)**
>
> Every option for the local command.

[PreviousHow Graphify works](https://docs.graphify.com/concepts/architecture.md)
[NextFollow calls and trace a path](https://docs.graphify.com/concepts/follow-calls.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.