Jarvis

io.github.jarvis-intelligencePublished by GitHub account jarvis-intelligencev0.8.0Updated Oct 11, 2026

Local-first SCIP code navigation and Zoekt search over your own indexed repositories

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local-first code intelligence server that gives an assistant precise symbol navigation and lexical search over repositories you have indexed on your machine.

What you can do
Resolve symbols to their defining file and range, and list every reference to a symbol across an indexed repo, including call and type hierarchies and per-file symbol outlines. Run lexical or regex code search, optionally limited to one repository. Check which other indexed repos depend on a package, up to two hops. Report index status such as published commit, freshness and staleness against the working tree. Build an index for a git repository at a given path.
When to use it
Useful when a coding agent keeps burning context on grep and file re-reads to find where a symbol is defined or used. Suited to developers working on one or more local git repositories who want exact reference and call-path answers instead of noisy text matches.
Requirements
Runs as a local stdio process on macOS arm64/x86_64 or Linux arm64/x86_64; Windows is not supported. Install the standalone Homebrew binary, which embeds its runtime and search tools, then index each repository with the CLI before querying. Optional per-language indexers need their own toolchains (Node.js/npm, JDK, Xcode). Indexes live in ~/.jarvis unless JARVIS_DATA_DIR overrides it.
Before you install
Indexing is explicit and must be run before queries; one language is detected per repository. Semantic search is unavailable in the standalone distribution and returns an error. The server never edits code, and query paths read published snapshots read-only, but the indexing CLI writes to the local data directory. Code and indexes stay on the machine.

Installation

In SourceWeft

  1. Open Jarvis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

jarvis

[CI] [Platforms] [License: MIT] [MCP]

Your coding agent should not spend its context window on grep.

When your agent asks "where is AuthService used?", grep returns comments, markdown, test fixtures, and similarly named symbols in one noisy pile. The agent burns context re-reading files to filter signal from noise — and still misses call sites.

jarvis precomputes a local code-intelligence layer so your agent calls findReferences for exact occurrences, goToDefinition for the defining range, callHierarchy for call paths, and searchCode for precise lexical search — ten MCP tools for Claude Code, Cursor, or any MCP client. Your code and indexes never leave your machine.

Without jarvisGrep → comments, tests, imports mixed with real hits → opens files to filter → guesses at call sites → burns context on search instead of reasoning
With jarvisfindReferences("AuthService") → exact file-and-range occurrences → callHierarchy for the graph → searchCode("token refresh") → answers without opening every match

[grep returns noisy results vs jarvis findReferences returning 10 exact file:line:col occurrences]

Quick start · MCP tools · Dashboard · Limits · Details · Docs

Quick start

1. Install the standalone binary:

bash
brew install jarvis-intelligence/jarvis/jarvis

Linux users need Homebrew/Linuxbrew installed first. The formula supports macOS arm64/x86_64 and Linux arm64/x86_64, installs both jarvis and jarvis-server, and embeds Python 3.12, dashboard assets, tree-sitter libraries, watch, scip, zoekt-git-index, and zoekt-webserver. Homebrew supplies universal-ctags. No Python, uv, pip, or PyPI installation is required.

Upgrade with brew upgrade jarvis; recover a damaged installation with brew reinstall jarvis.

2. Index a repo (slug defaults to the directory name):

bash
jarvis index /path/to/your/repo

3. Register the MCP server:

bash
claude mcp add jarvis --scope user -- jarvis-server

Ask your agent "find all references to AuthService" — it calls findReferences instead of grepping.

Other MCP clients (Cursor, Claude Desktop, any stdio client)
json
{  "mcpServers": {    "jarvis": {      "command": "jarvis-server"    }  }}

If your client can't find jarvis-server on PATH (GUI apps often don't inherit your shell's), use the absolute path from which jarvis-server.

Claude Code plugin (registers MCP + ships agent skills)

Install the Homebrew binary first. The plugin adds jarvis skills and can register the already-installed jarvis-server.

/plugin marketplace add jarvis-intelligence/jarvis-index/plugin install jarvis@jarvis
Optional language indexers

The standalone package includes the SCIP converter and both Zoekt binaries. The Homebrew formula does not install setup.sh; from a jarvis source checkout, install the optional per-language indexer for your repo:

LanguageInstallerToolchain
TypeScript/TSXsh setup.sh --only scip-typescriptNode.js/npm
Pythonsh setup.sh --only scip-pythonNode.js/npm
Java/Kotlinsh setup.sh --only scip-javaJDK; Kotlin repos require Kotlin 2.2.0 exactly
Swiftsh setup.sh --only scip-swiftXcode on macOS arm64

For Maven-built Java repositories on macOS, also install a modern Bash with brew install bash, then run sh setup.sh --only bash-shim from that same source checkout. Reindex after adding an indexer. Without the matching indexer, documentSymbols and goToDefinition still work via Tree-sitter where coverage exists; findReferences, callHierarchy, and typeHierarchy return recovery guidance.

Not included

semanticSearch is registered for MCP compatibility but is excluded from the standalone distribution. It returns a Homebrew-specific unavailability error that points to the source-build steps below; lexical search and symbol search remain available.

Source-build semantic search

The standalone Homebrew package excludes semantic dependencies. In a source checkout, install them with:

bash
uv run jarvis install-semantic

Then index explicitly:

bash
uv run jarvis index /path/to/repo --semantic

install-semantic also pre-downloads the embedding model (BAAI/bge-m3, ~4.3 GB, one time) into the shared Hugging Face cache (~/.cache/huggingface/); every indexed repo reuses it. If the download is interrupted, the next jarvis index retries it automatically.

MCP tools

ToolWhat it does
goToDefinitionResolve a symbol to its defining file and range
findReferencesEvery occurrence of a symbol across the indexed repo
callHierarchyIncoming/outgoing calls for a symbol
typeHierarchySupertypes/subtypes
documentSymbolsOutline of every symbol defined in one file
searchCodeZoekt lexical/regex search, optionally filtered to one repo
semanticSearchReturns the Homebrew distribution's semantic-unavailability error
blastRadiusWhich other indexed repos depend on a package, up to 2 hops
getIndexStatusPublished commit, freshness, staleness vs. working tree
indexRepoBuild an index for a git repo at path

Dashboard

bash
jarvis dashboard          # serves http://127.0.0.1:6080 and opens a browser

A localhost web console over the same ~/.jarvis data the CLI and MCP server read:

[Repositories view]   [Tool playground]

Requirements and limits

  • macOS arm64/x86_64 and Linux arm64/x86_64 only. Windows is not supported.
  • Semantic search is unavailable in the Homebrew distribution.
  • One language per repo — detected by extension plurality across git-tracked files; override with --language.
  • jarvis never edits code. It is the retrieval half — Serena complements it for renames/refactors.
  • Indexing is explicit — run jarvis index (or jarvis watch) before querying.

Details

How it works

One indexing CLI writes precomputed indexes into ~/.jarvis; one stdio runtime reads them down. The two share no other contract.

[jarvis architecture]

  • Publishing is atomic — a reindex writes a new snapshot, then flips the current pointer via os.replace. A query reading the old snapshot keeps working; no downtime window.
  • The runtime path never writes — every query opens the published snapshot read-only (mode=ro&immutable=1).
  • The package graph is rebuilt, not accumulated — each reindex clears that repo's outgoing edges before recomputing.

Full detail: docs/system-architecture.md

Indexing CLI reference
bash
jarvis index /path/to/your/repo            # slug defaults to the directory namejarvis index /path/to/your/repo --slug foo # or pick one explicitlyjarvis index /path/to/your/repo --scheme MyScheme # Swift repo with an ambiguous Xcode schemejarvis index /path/to/your/repo --language python # force the language instead of detecting itjarvis index /path/to/your/repo --no-scip   # skip optional SCIP enrichment; syntax baseline + Zoekt still publishjarvis index /path/to/your/repo --scip      # re-enable SCIP enrichment (both flags persist per repo)jarvis listjarvis status foojarvis reindex foojarvis forget foojarvis watch /path/to/your/repo [--debounce 5.0]  # debounced auto-reindex on file changes (foreground)
Known upstream limitations
  • scip-java can't index Android/Gradle repos — its Gradle plugin keys off standard source sets that AGP replaces (scip-java#177). Detected automatically; degrades to search-only.
  • Kotlin indexing requires an exact Kotlin version match — scip-kotlinc is compiled against one pinned release (currently 2.2.0). Detected automatically.
  • Maven-built Java repos need bash ≥ 4.4 on macOS — brew install bash fixes it.
  • Swift indexing requires scip >= v0.9.0 — older converters silently drop occurrence ranges. jarvis index refuses an older scip rather than publishing a broken index.
Configuration
VariablePurpose
JARVIS_DATA_DIROverride default ~/.jarvis for all indexes and registry

The source-development semantic path has additional model-prefix overrides; they have no effect in the standalone distribution.

Documentation

License

MIT

Source: README.md at commit 4cf9176

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts