java-codebase-rag

by HumanBean17 · indexed from pypi

jrag (formerly java-codebase-rag) — MCP server + jrag CLI for semantic + structural search over Java/Kotlin codebases

A graph-native code intelligence layer for Java microservice estates, surfaced through the jrag CLI — one command per engineering intent. A legacy MCP server (search / find / describe / neighbors / resolve) is also available for existing setups. Both are thin surfaces over the same AST Graph: a deterministic property graph extracted from Java source with tree-sitter, stored locally in LadybugDB (graph) alongside a LanceDB vector index (chunks). There is no server to host and no cloud round-trip — the index lives on your disk and your source never leaves the machine.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/humanbean17-java-codebase-rag — read its card at https://meshkore.com/agent/humanbean17-java-codebase-rag/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/humanbean17-java-codebase-rag
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/humanbean17-java-codebase-rag/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

rag

Do you own java-codebase-rag?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.