lilbee
● Activeio.github.tobocop2/lilbee
Local AI stack: search your files, notes, code and sites with cited answers.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"lilbee": {
"command": "npx",
"args": [
"-y",
"lilbee@0.6.90-beta.693",
"mcp"
]
}
}
}claude mcp add lilbee -- npx -y lilbee@0.6.90-beta.693 mcpcodex mcp add lilbee -- npx -y lilbee@0.6.90-beta.693 mcpcode --add-mcp '{"name":"lilbee","type":"stdio","command":"npx","args":["-y","lilbee@0.6.90-beta.693","mcp"]}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Developer Tools
- Version
- 0.6.90-beta.693
- Registry
- active
- Published
- 11/18/2026
Is it safe? Is it maintained?
Serverdex check: Nov 19, 2026Looks healthy: lilbee is maintained, open source.
- Maintained
- Active
- Last commit 3 days ago (Nov 18, 2026), 46 open issues.
- Official registry
- Active
- Published as io.github.tobocop2/lilbee in the official MCP registry, version 0.6.90-beta.693.
- Source
- Open source, MIT
- Public repository under the MIT licence, 71 stars, 9 forks.
- Runs
- On your machine
- A local npm package started by your client; it can reach whatever your user account can.
- Credentials
- None declared
- The registry entry declares no required environment variables.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.
On GitHub
read Nov 18, 2026- Stars
- 71
- Forks
- 9
- Last push
- Nov 18, 2026
- License
- MIT
Pythonai-search-enginechat-with-documentsggufllama-cpplm-studiolocal-ailocal-firstlocal-llmlocal-ragmcp-servermodel-managermulti-gpunotebooklm-alternativeollamaprivacyprivate-airagself-hostedsemantic-searchtui
From the README
The whole local AI stack in one executable: it runs and manages the models, and searches everything you own with them. Project site · Tutorial reels · PyPI · Obsidian plugin · REST API · Chat (#lilbee) lilbee runs your models and puts them to work as a search engine you can talk to. It searches your files, notes, code and saved web pages, and every answer cites its source, down to the line or page. It also crawls websites into your library, launches your coding agents on local models, and gives any MCP-aware agent cited answers. Ask in plain English. It is private. Your files, the index and your questions stay on your machine. No telemetry, no account. lilbee contacts a cloud provider only when you set its API key. Prefer a GUI? The Obsidian plugin puts lilbee's model manager and search inside your vault, with no terminal needed. Tutorial reel: every demo on this page and more, with long-form captions, at lilbee.sh/tutorial. Beta software. lilbee is in active beta. Every PyPI release is a pre-release, so pip needs --pre and uv needs --prerelease=allow. Commands and on-disk formats can change between betas. Bug reports are very welcome; that's the whole point of the beta. Latest pre-release: lilbee on PyPI. Why lilbee A small local model is fun, but limited on its own. Give it properly processed documents and a search engine over them, and it becomes genuinely powerful.…
Read the full README on GitHub →Alternatives to lilbee
All lilbee alternatives →Best Developer Tools servers →The most-starred Developer Tools servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| REA | 466,935 | Nov 2026 | Local / not checked |
| GitHub | 34,658 | Nov 2026 | Needs sign-in |
| Repomix | 29,280 | Nov 2026 | Local / not checked |
| Compiler Explorer | 19,201 | Nov 2026 | Working |
| XERJ | 19,135 | Nov 2026 | Local / not checked |
lilbee: questions people ask
- Is lilbee a remote or a local MCP server?
- According to its entry in the official MCP registry, lilbee ships as a local package (npm) that your client starts on your machine.
- Is lilbee safe to use?
- Looks healthy: lilbee is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 19, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is lilbee still maintained?
- Active: the repository's last commit 3 days ago. Last push Nov 18, 2026, 71 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
- How do I add lilbee to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Developer Tools servers
Browse all Developer Tools →ToGO
togo-framework
ToGO docs and plugins for agents: a full-stack Go + React framework, plus plugin submission.
Research Repo Doctor
Tom409114
Deterministic Artifact Evaluation preflight and run-path grader for research repositories.
MONS
tomis3
Build and adjust your clients' MONS training plans: programs, templates, exercises, sets, reps.
Archprint
Tommkruix
Mine the architecture rules your TypeScript repo already enforces, with the evidence attached.
OmniGet
tonhowtf
Desktop toolbox for coding agents: downloads, files, pages, ports, chats and cleanup, in OmniGet
Contraptify
torsviklabs
Design redstone machines with your AI and test them tick by tick with Java Edition 26.3 rules.
Add the badge to your site
Show visitors that lilbee is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-tobocop2-lilbee?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="lilbee — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-tobocop2-lilbee?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-tobocop2-lilbee) [](https://serverdex.io/install/vscode/io-github-tobocop2-lilbee) [](https://serverdex.io/install/claude-code/io-github-tobocop2-lilbee)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-tobocop2-lilbee"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-tobocop2-lilbee"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-tobocop2-lilbee"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).