CodeNib MCP Server

Quickstart

Requires Python 3.10+, Git, a clean repository, and Claude Code or Codex.

python -m pip install "codenib[graph,mcp]"
codenib codegraph init /path/to/your/repo

Then ask your agent: “Use CodeNib's explore_context to find where request retry behavior is implemented. Cite the files and lines.”

This shipping path builds local search and a typed symbol graph, then connects installed agent clients. It needs no model, API key, or GPU for CodeNib; your agent uses its own model. It is separate from the grep/Jev experiment above. Language toolchain and project prerequisites vary.

Setup and troubleshooting · Source exclusions · All MCP tools · Local Wiki

Related MCP server: scplus-mcp

Why CodeNib

• Inspect the evidence. Retrieve bounded code context with file and line references, then navigate definitions and static references. Read the source at each reference before describing a call path.

• Use the same tools across languages. The registry tracks 14 language entries, including 12 with graph backends. Check capability and setup differences in the language matrix.

• Compare methods on the same source. Pinned agent contracts, datasets, and scorer checks make the reproduction surface inspectable.

• Share what you found. Export a Wiki with source citations to your own GitHub Pages, or browse the public examples.

How it compares

What an agent can ask each tool. Peer interfaces were checked against upstream docs on 2026-09-28. This compares capabilities, not benchmark scores.

CodeNib's indexed references can include calls, fields, type uses and function values. Inspect the source to establish which references invoke a function; external and dynamic relationships may be missing. For a known string or file, your agent's native search and reads remain useful. Include indexing and rebuild costs when assessing graph navigation on your own tasks.

None of these repository tools needs its own model or API key; your agent uses its own model. Detailed comparison, sources and boundaries. CodeNib 0.2.4 also includes an optional grep → Jev route using OpenRouter for planning and reranking; selected code goes to remote models. Authorization previews remain opt-in. The historical research result above is separate from the product evaluation and the model-free CodeGraph row.

Languages

Graph backends: Python, Go, Rust, C/C++, C#, Java, Ruby, PHP, Kotlin, Scala, JavaScript, and TypeScript. Swift and Lua support chunking/retrieval. Provider prerequisites and coverage differ by language.

The generated language matrix separates chunking, graph backends, incremental-backend support, and decoder parity. The product currently reuses or rebuilds views; file-level delta repair is not enabled.

Results and reproductions

Documentation and community

Documentation · Architecture · Contributing · CI and testing · Changelog · Discord

CodeNib is in beta; public interfaces may change before a stable release. Historical research artifacts retain their published dataset identifiers.

Citation

If you use CodeNib in your research, please cite our arXiv paper:

@misc{yu2026codenibmultiviewdataserving,
      title={CodeNib: A Multi-View Data System for Serving Repository Context to Coding Agents},
      author={Zhongming Yu and Hengjia Yu and Boqin Yuan and Shuting Zhao and Yizhao Chen and Aryan Dokania and Mihir Jagtap and Jiayu Chang and Yitong Ma and Yash Jayswal and Wentao Ni and Hejia Zhang and Zhaoling Chen and Gangda Deng and Jishen Zhao},
      year={2026},
      eprint={2607.25431},
      archivePrefix={arXiv},
      primaryClass={cs.SE},
      url={https://arxiv.org/abs/2607.25431},
}

CodeNib is licensed under Apache 2.0.