Skip to main content
ClaudeWave

Local codebase memory for Codex, Claude Code, and other MCP coding agents

MCP ServersOfficial Registry0 stars0 forks● PythonUpdated today
ClaudeWave Trust Score
70/100
· OK
Passed
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Topics declared
  • ✓Documented (README)
Flags
  • !No standard license detected
Last scanned: 10/13/2026
Install in Claude Code / Claude Desktop
Method: pip / Python · lybrary
Claude Code CLI
claude mcp add lybrary -- python -m lybrary
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "lybrary": {
      "command": "python",
      "args": ["-m", "lybrary"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Install first: pip install lybrary
Use cases

MCP Servers overview

# Lybrary — local codebase memory for coding agents

Lybrary indexes a repository by code structure and gives Codex, Claude Code, and other MCP clients a searchable map of its functions, classes, and files. It runs locally, watches for changes, and lets an agent find relevant source lines before opening whole files.

<!-- mcp-name: io.github.vibhu-dixit/lybrary -->

[PyPI](https://pypi.org/project/lybrary/) · [Documentation](https://vibhu-dixit.github.io/lybrary/) · [Source](https://github.com/vibhu-dixit/lybrary) · [Issues](https://github.com/vibhu-dixit/lybrary/issues)

## Start in any repository

Install once, then run `lybrary start` in each folder you want indexed:

```bash
pip install lybrary
cd /path/to/your/repo
lybrary start
lybrary status
```

`start` creates `.lybrary/` if needed, builds the index, and runs a file-watching daemon in the background. It keeps running after the terminal closes. Run `lybrary stop` in that repository to stop it. The first indexing run may download the local embedding model; later runs use the cache.

Each repository has its own index and `.lybrary/config.toml`. The index stays on your machine; no API key or hosted database is required.

## Connect an agent

Register the MCP server once on your machine. Start your agent in an indexed repository, then ask it to call `memory_status` to confirm the root and chunk count.

### Codex

```bash
codex mcp add lybrary -- lybrary mcp
codex mcp list
```

Add this to that repository's `AGENTS.md` if you want Codex to use the memory consistently:

```markdown
When .lybrary/index.db exists, use Lybrary memory_query before broad code searches or reading multiple files. Inspect the returned source paths and lines before editing. If the index is absent or the tool fails, use normal search.
```

### Claude Code

```bash
claude mcp add --scope user --transport stdio lybrary -- lybrary mcp
claude mcp list
```

In Claude Code, `/mcp` shows connection status. Put the same instruction in the repository's `CLAUDE.md`. Registration makes the tool available; the instruction helps the agent choose it when useful.

For another stdio MCP client, configure command `lybrary` with argument `mcp`. See the [setup guides](https://vibhu-dixit.github.io/lybrary/).

## What the agent gets

`memory_query` blends exact symbol, SQLite text, and vector search. Its default response gives ranked paths, symbols, line ranges, and compact numbered excerpts. The agent can then inspect the relevant source lines. Set `include_content=true` when a full chunk is needed.

`memory_status` reports the active repository and index health. `memory_update` triggers incremental, full, or path-scoped re-indexing.

This can avoid repeated broad searches and large file reads, especially when the agent needs to locate a feature across sessions. Actual token use depends on the task, the agent's tool choices, and how much source it still needs to inspect. The [benchmark guide](https://vibhu-dixit.github.io/lybrary/token-usage.html) explains how to compare complete runs rather than infer savings from the size of one response.

## Make it fit your repo

Edit `.lybrary/config.toml` to choose the embedding model and device, chunk sizes, indexed languages, excluded paths, and file-watcher debounce. Add Git-style ignore patterns to `.lybrary/ignore`. Re-run `lybrary index --full` after changing settings that affect stored chunks or embeddings.

Supported parsers: Python, JavaScript, TypeScript, TSX, Go, Rust, Java, C, and C++. The indexer uses tree-sitter boundaries and refreshes changed files while the daemon is running.

## CLI

| Command | Purpose |
| --- | --- |
| `lybrary start` | Initialize, index, and watch the current repository |
| `lybrary stop` | Stop its background daemon |
| `lybrary status` | Show daemon and index status |
| `lybrary query "authentication flow"` | Search from the terminal |
| `lybrary index --full` | Rebuild the index |
| `lybrary logs` | Show daemon logs |
| `lybrary mcp` | Run the stdio MCP server |

If an agent starts above the indexed repository, pass that repository's absolute path as `repo_root` to the MCP tool, or start the agent inside it.

## Measure the effect

From a source checkout, compare the same read-only question with and without Lybrary:

```bash
python benchmark.py /path/to/indexed/repo "Trace how interview invitations are sent"
```

The script records both answers, tool calls, and total, cached, and uncached input tokens under `.lybrary/benchmarks/`. Check answer correctness first; one question does not establish typical savings.

## Contribute

Issues and pull requests are welcome. For a local checkout:

```bash
pip install -e ".[dev]"
pytest
```

Lybrary is MIT licensed. See the [changelog](CHANGELOG.md) for releases.
claude-codecode-searchcodebase-memorycodexdeveloper-toolsmcpmcp-serverpython

What people ask about lybrary

What is vibhu-dixit/lybrary?

+

vibhu-dixit/lybrary is mcp servers for the Claude AI ecosystem. Local codebase memory for Codex, Claude Code, and other MCP coding agents It has 0 GitHub stars and its last recorded update is dated 2026-10-13.

How do I install lybrary?

+

You can install lybrary by cloning the repository (https://github.com/vibhu-dixit/lybrary) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is vibhu-dixit/lybrary safe to use?

+

Our security agent has analyzed vibhu-dixit/lybrary and assigned a Trust Score of 70/100 (tier: OK). See the full breakdown of passed checks and flags on this page.

Who maintains vibhu-dixit/lybrary?

+

vibhu-dixit/lybrary is maintained by vibhu-dixit. The last recorded GitHub activity is dated 2026-10-13, with 0 open issues.

Are there alternatives to lybrary?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy lybrary to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: vibhu-dixit/lybrary
[![Featured on ClaudeWave](https://claudewave.com/api/badge/vibhu-dixit-lybrary)](https://claudewave.com/repo/vibhu-dixit-lybrary)
<a href="https://claudewave.com/repo/vibhu-dixit-lybrary"><img src="https://claudewave.com/api/badge/vibhu-dixit-lybrary" alt="Featured on ClaudeWave: vibhu-dixit/lybrary" width="320" height="64" /></a>

More MCP Servers

lybrary alternatives