jarvis-intelligence/jarvis-index 预览 preview

jarvis-intelligence/jarvis-index

Public distribution surface for jarvis — local-first code intelligence MCP server (SCIP navigation + Zoekt search). Installer, Claude Code / Codex / Cursor plugins, and prebuilt binaries.

项目介绍Project Overview

jarvis-index 是面向编码代理的本地优先代码检索插件。它通过 SCIP 与 Zoekt 在本机为仓库建立索引,并暴露九款 MCP 工具与三项代理技能,让代理可直接查询定义、引用、调用与类型层级、跨仓库搜索及受变更影响范围,取代盲目的 grep。适用于需要结构化代码理解、离线隐私的开发者。注意:Windows 不受支持,多语言仓库仅索引主体语言,Java/Kotlin 的 Android/Gradle 项目在偏离固定 Kotlin 版本时仅为可搜索。

jarvis-index is a local-first code intelligence plugin for coding agents. It builds an on-disk index of a repository with SCIP and Zoekt, then exposes nine MCP tools and three agent skills so agents answer structural questions, such as definitions, references, call and type hierarchies, cross-repo search, and blast radius, instead of guessing from grep. Use it when structural code understanding and offline privacy matter. Caveats: Windows is unsupported, polyglot repos index only the plurality language, and Java/Kotlin Android or Gradle projects off the pinned Kotlin version are search-only.

或使用命令行安装(适合开发者)Or use CLI install (for developers)

命令行安装CLI Install

dsh plugin --profile web add github:jarvis-intelligence/jarvis-index

jarvis-intelligence/jarvis-index 加入你的 DSH 配置(web profile)即可启用。

READMEREADME

Index once. Nothing leaves the room. Your repository stays where it is, jarvis index turns it into a local index on your disk, and your agent queries that index directly — all on your machine.

Local-first code intelligence for coding agents. Index your own repositories with SCIP and Zoekt, then let the agent ask structural questions — who calls this?, where is this defined? — instead of guessing from grep.

PyPI License Platform

Everything runs on your machine. No code leaves it, no telemetry, no account.

This repo is the public distribution surface: the installer, the plugins, the binary release assets, and the issue tracker. It holds no source — see Why this repo exists.


What you get

Nine MCP tools, exposed to any MCP client:

Tool Answers
Navigate goToDefinition Where is X defined?
findReferences Everywhere X is used
callHierarchy What calls X, and what X calls
typeHierarchy Super/subtypes of X
documentSymbols Every symbol in a file
Search searchCode Lexical search across indexed repos (Zoekt)
semanticSearch Natural-language search — needs the [semantic] extra
Scope blastRadius Which other indexed repos depend on this package
getIndexStatus Is this repo indexed, and is the index stale?

Plus three agent skills that ship with the plugin: jarvis-setup (onboarding), jarvis-use (steers the agent toward structural queries over grep), and jarvis-issues (files well-formed bug reports).

Full signatures and return shapes: plugin/skills/jarvis-use/references/tool-roster.md.

Quick start

# 1. External binaries (scip, zoekt, language indexers) → ~/.jarvis/bin
curl -fsSL https://raw.githubusercontent.com/jarvis-intelligence/jarvis-index/main/setup.sh | sh

# 2. The CLI + MCP server
uv tool install jarvis-mcp

# 3. Index a repo (slug defaults to the directory name)
jarvis index /path/to/your/repo

# 4. Verify
jarvis status <slug>          # expect: indexed

Then register the MCP server — or skip that entirely by installing the plugin below, which registers it for you.

setup.sh is idempotent; re-running skips what is already present. Options: --only <name>, --force, --help.

Install as a plugin

The plugin bundles the MCP registration and all three skills, so there is no manual mcp add.

Client How
Claude Code /plugin marketplace add jarvis-intelligence/jarvis-index
/plugin install jarvis@jarvis
Codex CLI codex plugin marketplace add https://github.com/jarvis-intelligence/jarvis-index --ref main
codex plugin add jarvis
Cursor Dashboard → Plugins → Add Marketplace → Import from Repo (Teams/Enterprise)
or clone and ln -s "$PWD/jarvis-index/plugin" ~/.cursor/plugins/local/jarvis
Other MCP clients Point them at the stdio command jarvis-server

Still run setup.sh + jarvis index afterwards — the plugin ships the wiring, not the binaries.

Details, the optional [semantic] extra, and privacy notes: plugin/README.md.

Requirements

  • macOS or Linux. Windows is not supported.
  • uv on PATH.
  • java on PATH only if you index Java/Kotlin repos.

Language support

One language per index — a polyglot repo indexes only its plurality language.

Language Indexer Notes
TypeScript / JavaScript scip-typescript
Python scip-python
Swift scip-swift macOS arm64 only; pass --scheme if the Xcode project has several
Java / Kotlin scip-java Android/Gradle projects and repos off the pinned Kotlin version are published search-only — lexical and semantic search work, navigation does not

Why this repo exists

jarvis's development repo is private, and GitHub serves raw files and release assets only to viewers of the owning repo. An unauthenticated curl against a private repo's setup.sh 404s — which is every real user. So every user-facing install path lives here, in public:

  • setup.sh, fetchable by anyone
  • the Claude Code / Codex / Cursor plugins
  • the scip and zoekt binaries, as GitHub release assets
  • the issue tracker

The Python package itself is on PyPI as jarvis-mcp.

Repo layout

setup.sh              Dependency bootstrapper — SYNCED from the dev repo, do not edit here
plugin/               The plugin: skills, MCP config, assets — source of truth, edit directly
.claude-plugin/       Claude Code marketplace manifest
.codex-plugin/        Codex CLI plugin manifest
.cursor-plugin/       Cursor marketplace manifest
docs/                 Maintainer documentation for this repo

Editing this repo

Path Rule
setup.sh Never edit here. Published automatically from the development repo and overwritten on the next release. Fix it upstream.
everything else Source of truth is here — edit directly.

Any change under plugin/ must bump the version in all three plugin manifests, to the same value, or it reaches nobody: plugin/.claude-plugin/plugin.json, plugin/.cursor-plugin/plugin.json, .codex-plugin/plugin.json. The plugin versions independently of the jarvis-mcp package on PyPI.

Full conventions: docs/code-standards.md.

Docs

overview · architecture · codebase summary · standards · publishing · roadmap

Links

上一个 Prev dsh-plugin-knowledge-graph 下一个 Next dsh-web-search-searxng