本体索引

Third-party Prerequisites

OntoIndex runs on Node.js and uses native parser packages for some languages. Install the following before installing OntoIndex.

Linux example:

node --version
npm --version
git --version
python3 --version
make --version
g++ --version

Windows PowerShell example:

node --version
npm --version
git --version
python --version
npm config get msvs_version

Installation

Install the Latest GitHub Release

Linux and macOS:

wget -qO- https://raw.githubusercontent.com/ontograph/ontoindex/master/scripts/install-ontoindex-latest.sh | bash
ontoindex --version

If wget is unavailable, curl -fsSL https://raw.githubusercontent.com/ontograph/ontoindex/master/scripts/install-ontoindex-latest.sh | bash works as a fallback.

Windows PowerShell:

iwr -useb https://raw.githubusercontent.com/ontograph/ontoindex/master/scripts/install-ontoindex-latest.ps1 | iex
ontoindex --version

Windows note:

- OntoIndex no longer supports Node.js 20 in the current release line because commander@15 requires Node.js 22.12.0 or newer. - Node.js 24 and 25 use OntoIndex's vendored tree-sitter runtime source, patched to compile native bindings with C++20 when prebuilds are unavailable. - With Node.js 22 LTS, use npm 11.6.0 or newer on Windows. - Older npm releases can bundle node-gyp builds that fail to detect Visual Studio 2026 Build Tools. - Upgrade with npm.cmd install -g npm@11.6.3 before retrying the installer.

From a local checkout:

The installers fetch the latest GitHub release, locate the ontoindex-*.tgz asset, and install it with npm install -g. If ONTOINDEX_LOCAL_ASSET points to a tarball, or an ontoindex-*.tgz file already exists in the current directory or beside the script, the Linux/macOS installer uses that local tarball first instead of going back to GitHub. If a global install is not writable, the installers fall back to a user npm prefix.

The default installer is not an offline bundle of every third-party package. It ships OntoIndex sources and vendored parser sources, then lets npm resolve runtime dependencies such as LadybugDB, ONNX Runtime, and image/vector helpers for the current platform. A non-fatal npm deprecation warning from a transitive package can appear while upstream packages catch up. For air-gapped hosts, use an internal npm registry mirror or a prepared npm cache.

On Linux x64, the installer also prefetches LadybugDB fts and vector extension binaries from the OntoIndex GitHub extension-cache release. On Windows x64, the PowerShell installer prefetches the same binaries from the LadybugDB extension host into the local cache. At runtime, OntoIndex tries that cache before asking LadybugDB to download extensions during INSTALL fts / INSTALL VECTOR.

If a Windows install previously failed partway through and left a broken ontoindex.cmd shim, repair the global install state before retrying:

npm.cmd uninstall -g ontoindex
if (Test-Path "$env:APPDATA\npm\node_modules\ontoindex") { Remove-Item "$env:APPDATA\npm\node_modules\ontoindex" -Recurse -Force }
if (Test-Path "$env:APPDATA\npm\ontoindex.cmd") { Remove-Item "$env:APPDATA\npm\ontoindex.cmd" -Force }
if (Test-Path "$env:APPDATA\npm\ontoindex.ps1") { Remove-Item "$env:APPDATA\npm\ontoindex.ps1" -Force }

Installer configuration:

Install with npm

Use this path when npm publication is available in your environment.

Install from a Release Tarball URL

Use this when you want an immutable GitHub release asset.

MCP Setup

ontoindex setup configures supported MCP clients automatically. Manual examples are useful for debugging or for clients that do not support automatic setup.

Cursor example:

{
  "mcpServers": {
    "ontoindex": {
      "command": "ontoindex",
      "args": ["mcp"]
    }
  }
}

OpenCode example:

{
  "mcp": {
    "ontoindex": {
      "type": "local",
      "command": ["ontoindex", "mcp"]
    }
  }
}

Docker

Images:

Optional Web UI

The hosted UI is optional and can connect to a local backend at http://localhost:4747.

To run the web UI from source:

The browser-only mode can inspect uploaded ZIPs in memory. For larger repositories, start ontoindex serve and let the UI use the local index.

Common Agent Workflows

Core MCP surfaces include:

Indexing Pipeline

The graph build is a typed phase DAG:

scan -> structure -> [markdown, cobol] -> parse -> [routes, tools, orm]
  -> crossFile -> mro -> communities -> processes

Key steps:

1. Scan files with repository ignore rules.
2. Parse supported languages with Tree-sitter providers.
3. Resolve imports, calls, receivers, constructors, type hints, inheritance, and method-resolution-order edges.
4. Enrich the graph with routes, MCP/RPC tools, ORM queries, markdown sections, communities, and execution flows.
5. Persist nodes and relations into LadybugDB under .ontoindex/.
6. Expose the same graph through CLI, MCP, HTTP, web UI, generated wiki pages, and generated skills.

Supported language depth varies, but the shared model covers TypeScript, JavaScript, Python, Java, Kotlin, C#, Go, Rust, PHP, Ruby, Swift, C, C++, Dart, and protobuf-related parser support.

Comparison With Related Tools

This table compares functional scope, not benchmark speed.

Practical guidance:

• Choose OntoIndex when an agent must edit or release from local evidence: impact, diff review, docs drift, audit workflows, and target-repository safeguards.
• Choose Graphify when the main deliverable is a broad human-readable project knowledge graph across mixed artifacts.
• Choose CodeGPT Deep Graph MCP when your graph already lives in CodeGPT/DeepGraph.
• Choose smaller code-graph MCP servers when you only need AST/call/dependency lookup without a broader audit lifecycle.
• Choose Serena for language-server style symbolic edits.
• Choose Graphiti MCP for temporal memory over facts and events; it complements OntoIndex rather than replacing a source-code index.