Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerJVM AST-level code indexer (Java/Kotlin/Scala) with SQLite storage, exposed as an MCP server for AI coding assistants.
中文 | English
AI coding assistants exploring unfamiliar JVM projects today:
Supports 30+ annotations across major frameworks:
Requires Java 21+ (JRE or JDK). Docker and Native Image options bundle the runtime.
Option 1: Download from GitHub Releases (recommended)
# Fat JAR (all platforms)
curl -LO https://github.com/Lincoln-cn/JCodeIndexer/releases/latest/download/java-code-indexer-VERSION.jar
# Native Image (Linux)
curl -LO https://github.com/Lincoln-cn/JCodeIndexer/releases/latest/download/java-code-indexer-VERSION-linux-amd64.tar.gz
# Native Image (macOS)
curl -LO https://github.com/Lincoln-cn/JCodeIndexer/releases/latest/download/java-code-indexer-VERSION-darwin-arm64.tar.gz
# Native Image (Windows)
curl -LO https://github.com/Lincoln-cn/JCodeIndexer/releases/latest/download/java-code-indexer-VERSION-windows-amd64.zip
Option 2: Build from source (requires Java 21+ and Maven 3.8+)
git clone https://github.com/Lincoln-cn/JCodeIndexer.git
cd java-code-indexer
mvn package -q -DskipTests
# output: target/java-code-indexer-*-shaded.jar
Option 3: Docker
docker pull sodlinken/jcodeindexer:latest
# 1. Index your JVM project (Java/Kotlin/Scala)
java -jar java-code-indexer-VERSION.jar --project-root /path/to/your/project --index
# 2. Start the MCP server (stdio, for Claude Code / Qwen Code / Cursor)
java -jar java-code-indexer-VERSION.jar --project-root /path/to/your/project
That's it. Your AI assistant can now query your codebase structure instead of reading files.
java -jar java-code-indexer-VERSION.jar [options]
Options:
--project-root <path> JVM project root directory (default: current dir)
--data-dir <path> Index data directory (default: .jindexer)
--init Initialize database schema only
--index Run indexer (extract symbols/references/calls)
--status Show index statistics
--search <query> Search directly (no MCP server needed)
--export <file> Export index data to JSON file
--version Show version number
--help, -h Show help
No flags → start MCP server over stdio.
When running as an MCP server, Java Code Indexer exposes these tools:
{
"method_name": "com.example.Service.save",
"direction": "both", // "callers" | "callees" | "both"
"filter": "project", // "all" | "project" | "jdk"
"limit": 50 // max results per direction
}
For method calls that cannot be resolved, the system automatically infers the type and returns a type field:
Create .jindexer/config.yaml in your project root (optional):
# === Project Paths ===
# Project root (CLI --project-root overrides this)
project_root: /path/to/project
# Data directory (stores index.db)
data_dir: .jindexer
# === Indexing ===
# Number of indexing threads
indexing_threads: 4
# Max file size to index (KB)
max_file_size_kb: 512
# Extract Javadoc comments
extract_javadoc: false
# Follow symbolic links
follow_symlinks: false
# Include patterns (files to index)
include_patterns:
- "**/*.java"
- "**/*.yml"
- "**/*.yaml"
- "**/*.properties"
- "**/*.env"
- "**/pom.xml"
- "**/build.gradle"
- "**/build.gradle.kts"
# Exclude patterns (files to skip)
exclude_patterns:
- "**/target/**"
- "**/build/**"
- "**/.git/**"
- "**/node_modules/**"
# === Storage ===
# Database filename
db_name: index.db
# === Logging ===
# Log level: DEBUG, INFO, WARN, ERROR
log_level: INFO
# Enable verbose logging
verbose: false
# === File Watcher ===
# Enable automatic re-indexing on file changes
watch_enabled: true
# Watch mode: event (NIO WatchService) or polling (SHA-1 check)
watch_mode: event
# Watch interval in seconds (polling mode)
watch_interval_seconds: 5
# Debounce interval in ms (event mode)
watch_debounce_ms: 500
# Directories to exclude from watching
watch_exclude:
- "**/target/**"
- "**/build/**"
- "**/.git/**"
- "**/node_modules/**"
# === Multi-project Mode ===
# Define multiple projects to index together
projects:
- name: backend
root: /path/to/backend
- name: frontend
root: /path/to/frontend
# === Auto Discover ===
# Auto-discover Maven/Gradle sub-modules
auto_discover: true
CLI flags → environment variables → config file → defaults.
Add to your MCP configuration:
{
"mcpServers": {
"java-code-indexer": {
"command": "java",
"args": ["-jar", "/path/to/java-code-indexer-VERSION.jar", "--project-root", "/path/to/project"]
}
}
}
{
"mcpServers": {
"java-code-indexer": {
"command": "docker",
"args": ["run", "--rm", "-i", "-v", "/path/to/project:/project", "sodlinken/jcodeindexer:latest", "--project-root", "/project"]
}
}
}
┌──────────────┐ MCP (stdio) ┌──────────────────────────────────────┐
│ AI Assistant │ ◄─────────────────► │ Java Code Indexer │
│ (Qwen/Claude)│ JSON-RPC │ │
└──────────────┘ │ Phase A: Parallel Parse (no lock) │
│ ┌────────────────┐ │
│ │ Virtual Threads│──► Parsers: │
│ │ (concurrent) │ JavaParser │
│ │ │ KotlinParser │
│ │ │ ScalaParser │
│ └───────┬────────┘ │
│ ▼ │
│ Phase B: Batch Write (transactional) │
│ ┌────────────────┐ │
│ │ SQLite (WAL) │ │
│ │ symbols │ │
│ │ references │ │
│ │ call_graphs │ │
│ │ annotations │ │
│ │ configs │ │
│ │ dependencies │ │
│ └────────────────┘ │
└──────────────────────────────────────┘
executeBatch(), stale files deleted via IN clauses, stats merged into a single SQL query.Thirteen core tables:
symbols — classes, methods, fields with location and signaturesreferences — symbol usage locations across the codebasecalls — method call relationships (caller → callee)annotations — symbol annotations with attributeschunks — code slices at class/method granularityfile_meta — SHA-1 hashes for incremental indexingconfig_entries — YAML/Properties/.env key-value pairsdependencies — Maven/Gradle dependency declarationsapi_routes — Spring Boot API route mappings (URL → Controller)bean_dependencies — Spring Bean injection relationshipstest_mappings — Test class to source class associationsindex_metadata — Index metadata (key-value store)code_metrics — Code metrics (LOC, method/field counts, complexity)Plus FTS5 full-text search tables (symbols_fts, chunks_fts) with auto-sync triggers.
The database uses automatic migration to handle schema upgrades:
ALTER TABLE ADD COLUMN which preserves existing dataWhen upgrading from an older version, the database schema is automatically updated without deleting data files. If the database is corrupted, it will be automatically rebuilt.
src/main/java/com/sodlinken/jindexer/
├── cli/ # CLI entry point
├── mcp/ # MCP server (JSON-RPC over stdio)
├── config/ # YAML config loader
├── storage/ # SQLite schema & StorageService (including FTS5)
├── indexer/ # Two-phase incremental indexing engine (parallel parse + batch write)
├── parser/ # Java, Kotlin, Scala, POM, Gradle, Config parsers
├── chunker/ # Code chunking (class/method slices)
├── search/ # Structured search (FTS5 full-text)
├── model/ # Data models (Symbol, Call, Chunk, Annotation, etc.)
└── util/ # SHA-1 hashing utility
Release workflow is automated via GitHub Actions:
# Clone and build
git clone https://github.com/Lincoln-cn/JCodeIndexer.git
cd JCodeIndexer
mvn package -q -DskipTests
# Run tests
mvn test
# Index this project itself
java -jar target/java-code-indexer-*-shaded.jar --project-root . --index
# Start MCP server
java -jar target/java-code-indexer-*-shaded.jar --project-root .
GitHub Actions automated release process:
v* tag or manual trigger# Create release tag (replace VERSION with actual version)
git tag vVERSION
git push origin vVERSION
# Run all tests (384+ tests)
mvn test
# Run specific test class
mvn test -Dtest=JavaParserAdapterTest
# Run performance benchmarks
mvn test -Dtest=PerformanceBenchmarkTest
Java / Kotlin / Scala AST-level code indexer with SQLite storage, exposed as an MCP server; provides multiple analysis tools including symbol & reference search, call-graph analysis and annotation-awa
Vue d'ensemble
Java / Kotlin / Scala AST-level code indexer with SQLite storage, exposed as an MCP server; provides multiple analysis tools including symbol & reference search, call-graph analysis and annotation-aware indexing to help AI assistants understand codebases
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
JCodeIndexer s'exécute en local via stdio.
Dernière vérification : 2026-10-28. Java / Kotlin / Scala AST-level code indexer with SQLite storage, exposed as an MCP server; provides multiple analysis tools including symbol & reference search, call-graph analysis and annotation-aware indexing to help AI assistants understand codebases