> ## 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 (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search 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. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. 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 JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server.
> 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.

# Export and reuse your graph

> Export a Graphify graph as an interactive map, a wiki, graph files, or database import scripts you can reuse in other tools.

Build a graph first, then export the same saved relationships into the format you need.

| Command | Output |
| - | - |
| `graphify export html` | Interactive graph visualization. |
| `graphify export callflow-html` | Architecture and call-flow HTML. |
| `graphify export wiki` | Markdown wiki organized around graph communities. |
| `graphify export obsidian` | Obsidian-compatible notes and links. |
| `graphify export svg` | Static SVG graph; requires the `svg` extra. |
| `graphify export graphml` | GraphML for tools such as Gephi or yEd. |
| `graphify export neo4j` | Cypher for Neo4j. |
| `graphify export falkordb` | Cypher for FalkorDB. |

## Generate a call-flow view

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
graphify export callflow-html --max-sections 8
graphify export callflow-html --output docs/architecture.html
```

The exporter reads the graph and associated report/labels. Explicit output paths make it easier to include the result in an internal documentation workflow.

## Export another graph

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
graphify export graphml --graph ./shared/graph.json
```

## Write to an existing Obsidian vault

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
graphify export obsidian --dir /absolute/path/to/vault
```

Review generated content before syncing it to a shared vault. The exporter is designed to preserve your own notes and `.obsidian` configuration.

## Push to a graph database

Neo4j and FalkorDB exports support optional push connections. Install the matching extra, use the appropriate connection URL, and supply passwords through `NEO4J_PASSWORD` or `FALKORDB_PASSWORD` rather than putting secrets on the command line.

## Run every export on a real repository

These examples come from a code-only graph of the open-source [httpx](https://github.com/encode/httpx) repository, built with Graphify Local 0.9.97. Your counts will differ.

```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
$ graphify export html
graph.html written - open in any browser, no server needed
$ graphify export wiki
Wiki: 199 articles written to graphify-out/wiki/
  graphify-out/wiki/index.md  ->  agent entry point
$ graphify export obsidian
Obsidian vault: 2530 notes in graphify-out/obsidian/
Canvas: graphify-out/obsidian/graph.canvas
$ graphify export graphml
graph.graphml written - open in Gephi, yEd, or any GraphML tool
$ graphify export neo4j
cypher.txt written - import with: cypher-shell < graphify-out/cypher.txt
$ graphify export callflow-html
Call-flow HTML written: graphify-out/httpx-callflow.html
  Sections: 17  |  Mermaid diagrams: 16  |  Call tables: 15
$ graphify tree
wrote graphify-out/GRAPH_TREE.html (157.3 KB)
```

## Outputs

| Command | Writes | Needs |
| - | - | - |
| `export html` | `graph.html` | Nothing extra. `--node-limit` defaults to 5000. |
| `export callflow-html` | `<name>-callflow.html` | Nothing extra. |
| `export wiki` | `wiki/` with `index.md` | Nothing extra. |
| `export obsidian` | `obsidian/` vault and `graph.canvas` | Nothing extra. |
| `export svg` | `graph.svg` | The `svg` extra. |
| `export graphml` | `graph.graphml` | Nothing extra. |
| `export neo4j` / `falkordb` | `cypher.txt`, or a push with `--push URI` | The `neo4j` / `falkordb` extra to push. |
| `tree` | `GRAPH_TREE.html` | Nothing extra. |

To push to a database, set `NEO4J_PASSWORD` or `FALKORDB_PASSWORD` instead of passing `--password`, so the secret stays out of your shell history.

## Troubleshooting

**`ImportError: matplotlib not installed. Run: pip install matplotlib`.** SVG export needs the `svg` extra:

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
pip install "graphifyy[svg]"
```

**`warning: graphify-out/.graphify_analysis.json is stale (1883 node(s) recorded vs 2341 in graph.json)`.** The graph changed after the last clustering. The export still runs, rebuilding communities from `graph.json`. To refresh community data, run:

```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
graphify cluster-only .
```

## Flags

| Command | Flags |
| - | - |
| `export html` | `--graph PATH`, `--labels PATH`, `--node-limit N` (default 5000), `--no-viz` |
| `export callflow-html` | `--graph PATH`, `--labels PATH`, `--report PATH`, `--sections PATH`, `--output HTML`, `--lang auto\|zh-CN\|en`, `--max-sections N`, `--diagram-scale N` |
| `export obsidian` | `--graph PATH`, `--labels PATH`, `--dir PATH` |
| `export wiki` / `svg` | `--graph PATH`, `--labels PATH` |
| `export graphml` | `--graph PATH` |
| `export neo4j` / `falkordb` | `--graph PATH`, `--push URI`, `--user U`, `--password P` |
| `tree` | `--graph PATH`, `--output HTML`, `--root PATH`, `--max-children N` (default 200), `--top-k-edges N` (default 0, off), `--label NAME` |

## FAQ

**Do exports call an LLM?** No. They read `graph.json` and the label files.

**Which export should an agent read?** `wiki/index.md` is marked as the agent entry point.

## Next steps

> **[Try it in Graphify](https://docs.graphify.com/platform/quickstart.md)**
>
> We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.

> **[Share context with your team](https://docs.graphify.com/cookbooks/shared-team-graph.md)**
>
> Keep one graph for everyone.

> **[Graph files and outputs](https://docs.graphify.com/concepts/outputs.md)**
>
> What each output file contains.

[PreviousRecord useful findings](https://docs.graphify.com/open-source/features/work-memory.md)
[NextShare context with your team](https://docs.graphify.com/cookbooks/shared-team-graph.md)


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