@nxuss/lemma weekly downloads statistics
By nxuss · npm · Claude Code
Local MCP server that gives coding agents a verifiable project memory, trims what enters their context, and masks secrets — with honest accounting of what it saves and costs.
@nxuss/lemma has 2,615 recorded weekly downloads on npm, a decrease of 0.3% over the past 30 days, ranking #1275 of 2,322 tracked listings.
About @nxuss/lemma
🧠 Lemma
A memory your AI agent can verify, and a context window that only holds what matters.
Coding agents forget everything between sessions, re-read the same files, and dump whole test logs into their context. Lemma is a local MCP server (plus an optional proxy) that gives them a project memory checked against your actual code, trims what enters the context, and keeps the receipts — including what Lemma itself costs.
npm install -g @nxuss/lemma
lemma init # wires Claude Code, Cursor, Codex, Windsurf, Kiro, OpenCode, Muse
That's it: your agent now has Lemma's tools. The dashboard opens at http://localhost:8081/dashboard/.
Why Lemma
🧠 A memory that knows when it's out of date. The Brain stores fixes, decisions and context in a local index (BM25, no embeddings service, no cloud). Every memory is tied to the files and symbols it's about, so when the code changes it comes back stale instead of confidently wrong — and a memory with no evidence is labelled as such, never sold as a verified answer.
✍️ It fills itself. A test, build or lint command that goes red → green is saved as
fix: <the error> with the diff that fixed it. Commits become memories. Next time the same
error shows up, the agent is pointed at the fix — through hooks in Claude Code, Codex, Cursor
and OpenCode, for zero model tokens.
👥 Shared through git. brain_team push writes verified memories into the repo, one
reviewable JSON file each. Teammates pull them on merge/checkout, re-verified against their
checkout.
✂️ Less noise in the context. Large search results are capped, failing test/tsc/lint
output is distilled to the failures that matter (the full log stays retrievable), and a command
that prints the same thing twice comes back as IDENTICAL or a diff. Only the tools your
project needs are advertised; the rest are one lemma_toolbox call away.
🔒 Private by default. API keys, credentials and PII are masked in file reads, searches and
command output before they reach the model. Commands run with a minimal environment and
workspace-bound paths, or in an opt-in Docker sandbox. Everything binds to 127.0.0.1.
📊 Numbers you can check. Lemma records what it saves and what it spends — its own
prompt, tool schemas and every result it adds to the context — and the dashboard shows the net
balance next to the gross. A cache hit says it's a cache hit; token_receipt shows how each
answer was produced.
🧰 Static intelligence without tokens. Dependency graphs, coupling/risk scores and AST
symbol lookups computed locally with the TypeScript compiler, plus surgical AST edits instead of
full-file rewrites. C# gets the parts that are real; the rest says fallback instead of
pretending (capability_matrix).
Free vs Pro
61 of the 111 tools are free, including all memory, upkeep and export tools and the 22
infrastructure tools (Jenkins, OKD/OpenShift, Terraform). Pro adds writing and patching,
search_workspace, run_workspace_command, static analysis, PR review and auto-heal.
| Free | Pro | |
|---|---|---|
| Memory | search_memory, store_memory, get_memory, update_memory, verify_memory, brain_team, brain_upkeep, brain_export… | get_telepathic_hints, semantic_dedup_guard, local_semantic_autofix |
| Context | read_workspace_file, scrub_privacy, token_budget, token_receipt, auto_context_bundle | get_ast_hologram, smart_file_slice, get_symbol_surgical_context |
| Workspace | — | apply_workspace_patch, write_workspace_file, run_workspace_command, validate_patch_sandbox, surgical_ast_insert |
| Analysis & review | type_coverage_report, git_blame_heat | depgraph, entropy_score, refactor, review_diff, review_pr, test_oracle |
| Infrastructure | all 22 infra_*, jenkins_*, okd_*, terraform_* | — |
Without a license, Pro tools aren't advertised to the model at all. Full list:
lemma_toolbox { "action": "list" }. Get Pro: lemma activate <key> →
lemma.nxus.studio/upgrade.
Setup
| Client | How |
|---|---|
| Claude Code, Cursor, Codex, OpenCode, Windsurf, Kiro | lemma init in the project |
| Muse | Installed on npm i -g; lemma call <tool> '<json>' works from any shell |
| Claude Desktop / any MCP client | { "command": "npx", "args": ["-y", "@nxuss/lemma", "mcp"] } |
lemma init also installs the hooks that feed the Brain (git post-commit / post-merge /
post-checkout, and post-tool hooks for Claude Code, Codex, Cursor and OpenCode). Existing hooks
are kept; --no-hooks skips them. Health check: lemma doctor.
CLI
| Command | What it does |
|---|---|
lemma init | Configure MCP and hooks for this project |
lemma start / stop / status | Proxy + dashboard on localhost:8081 (an MCP server starts it on its own when none is running) |
lemma stats | Net token and cost report |
lemma mcp | Run the MCP server on stdio |
lemma call <tool> [json] | Call one tool from a shell, for CLIs without MCP |
lemma doctor | Check the installation |
lemma activate <key> | Activate Pro |
Configuration…
Description from the npm listing.
- semantic-cache
- privacy-firewall
- ai-security
- cost-optimization
- intelligent-proxy
- ai-agents
- orchestration
- ide-sync
- llm-gateway
- openai-proxy
- anthropic-proxy
- vector-database
- muse
- muse-code
- muse-spark
- claude-code
- cursor
- codex
- mcp
- mcp-server
README badge
Show your rank in a README or on your website. The badge updates automatically.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Ranking history
Listing placement
Listing placement
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Recent observations
Full history (122)Similar npm Claude Code plugins
All 20 @nxuss/lemma alternativesData source
Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.
Listing: https://www.npmjs.com/package/@nxuss/lemma. First seen Oct 16, 2026; last successful collection Oct 20, 2026. See the methodology.