Ermöglicht es einem AI-Client, entschlüsselte Logs zu durchsuchen, Anwendungen aufzulisten und in Echtzeit auf neue Fehler oder fatale Ereignisse zu überwachen.
Auch bekannt als infinitetoken/Lumber-CLI, lumber-cli, @infinitetoken/lumber-cli
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- 1.878
- Neueste Version
- 0.5.0
- Letzter Commit
- 14. Nov. 2026
- Lizenz
- MIT
Was ist Lumber MCP?
Lumber ist ein MCP server. Ermöglicht es einem AI-Client, entschlüsselte Logs zu durchsuchen, Anwendungen aufzulisten und in Echtzeit auf neue Fehler oder fatale Ereignisse zu überwachen.
Zusammenfassung generiert aus dem README des Projekts
Über Lumber MCP server
Lumber bietet Entwicklern eine Möglichkeit, AI Agents über das Model Context Protocol mit ihren verschlüsselten Application Logs zu verbinden. Dieser MCP server läuft lokal auf macOS, Windows oder Linux und nutzt deine vorhandenen Lumber-Account-Credentials, um Daten direkt auf deiner eigenen Maschine zu entschlüsseln. Da die Entschlüsselung lokal mit deinem Account-Key erfolgt, haben die Lumber-Server niemals Zugriff auf den Klartext deiner Logs.
Nutzer können den Server einrichten, indem sie den Befehl lumber mcp ausführen und ihn ihrer Client-Config hinzufügen, wie zum Beispiel Claude Desktop oder Claude Code. Der Server stellt spezifische Tools bereit, darunter list_apps, um verfügbare Anwendungen anzuzeigen, search_logs, um gezielt Einträge mittels Textmustern und Zeiträumen zu finden, sowie list_notes, um Kommentare von anderen Teammitgliedern einzusehen. Zudem gibt es ein wait_for_logs Tool, mit dem ein Agent in Echtzeit auf neue Fehler oder fatale Ereignisse warten kann, was es zu einem nützlichen Tool für automatisiertes Debugging und Systemmonitoring macht.
Was du damit machen kannst
- 1Echtzeit-Überwachung von Application ErrorsEin AI Agent kann auf neue Error- oder Fatal-Events warten und versuchen, die Ursache direkt in deinem Codebase zu finden.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Lumber MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenLumber MCP in Claude Code installieren
$ claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliLumber MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Lumber MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"lumber-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Lumber MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"lumber-cli","type":"stdio","command":"npx","args":["-y","@infinitetoken/lumber-cli"]}'Lumber MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Lumber MCP in Codex installieren
$ codex mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliLumber MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.lumber-cli] command = "npx" args = ["-y", "@infinitetoken/lumber-cli"]
Lumber MCP in Gemini CLI installieren
$ gemini mcp add -s user lumber-cli npx -- -y @infinitetoken/lumber-cliLumber MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarinfinitetoken/lumber-cli is public and reachablegithub.com/infinitetoken/lumber-cli ↗Bestanden
- Paket nennt dieses Repository als Quelle@infinitetoken/lumber-cli names infinitetoken/lumber-cli as sourcenpmjs.com/package/@infinitetoken/lumber-cli ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for @infinitetoken/lumber-clinpmjs.com/package/@infinitetoken/lumber-cli/v/0.5.0#provenan ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-14github.com/infinitetoken/lumber-cli ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @infinitetoken/lumber-cliBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeitenthe package checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeNicht geprüft
README
Auf GitHub ansehen@infinitetoken/lumber-cli
Read your Lumber logs from the terminal, and let an AI agent read them over MCP. Logs are decrypted on your computer with your own account key, so Lumber's servers still can't read them.
Runs on macOS, Windows and Linux. It reads; it never changes anything in Lumber.
Installation
npm install -g @infinitetoken/lumber-cli
The package is scoped: the unscoped lumber and lumber-cli on npm are someone else's.
Or with Homebrew, on macOS or Linux. This repo is the tap:
brew tap infinitetoken/lumber https://github.com/infinitetoken/Lumber-CLI
brew install infinitetoken/lumber/lumber
Naming it in full the first time is what has Homebrew trust the formula. Update with brew upgrade lumber.
On Windows with Scoop, which needs no Node: this repo is also the bucket.
scoop bucket add lumber https://github.com/infinitetoken/Lumber-CLI
scoop install lumber/lumber
Update with scoop update lumber.
Or download lumber itself, with Node built in, for Windows, macOS or Linux (x64 or arm64) from the latest release, unpack it and put it on your PATH. Check a download against the release's SHA256SUMS, or where it was built with gh attestation verify <file> --repo infinitetoken/Lumber-CLI. On a Mac the download isn't notarized yet, so one a browser saved runs only after xattr -d com.apple.quarantine lumber: Homebrew is the easier way there.
Signing in
lumber login
Signs in with your Lumber email and password, then links this computer the way a new phone links: open Lumber on a phone or Mac that already has your account key (your phone gets a notification, and the Mac app asks when you switch to it, or open Account > Link another device), tap Show Code, and type the 7-digit code at the Code prompt. That device checks the code and sends your account key. The request lasts 10 minutes, and a wrong code ends it. The other device needs an up-to-date Lumber app.
The session and your account key are kept in your system's own credential store, never in a file:
- macOS: your login keychain, the "Lumber CLI" item.
- Windows: Credential Manager, the generic credential
session.Lumber CLI. - Linux: the Secret Service, which GNOME Keyring and KWallet provide, the "Lumber CLI" item. A desktop session has one; on a server or over SSH with none running,
lumbersays so and stops.
The session renews itself each day you use it, so it only ends after 30 days without running lumber; signing in again then, as the same person, needs no new link. lumber logout removes both.
Commands
lumber status # who's signed in, which apps this computer can read
lumber apps # your apps
lumber logs # the newest 100 logs from every app, oldest at the bottom
lumber logs Lumber-Test -l error -s 2h # one app's errors and fatals from the last two hours
lumber logs -g "payment" -n 20 # the newest 20 logs mentioning "payment"
lumber tail Lumber-Test -l warn # follow new warnings and worse as they arrive
lumber help # everything, and `lumber logs help` for one command
- Apps are names (in any case) or ids. Naming none means every app.
-l, --leveltakes one level for that level and above (warnis warn, error and fatal), or a list for exactly those (info,warn).-s, --sinceand-u, --untiltake an age (15m,2h,3d), a day (2026-10-29,today,yesterday) or an ISO time.-g, --grepmatches the message, request and trace ids, context and metadata, ignoring case. The server only holds ciphertext, so the search runs here, reading back through at most 20,000 logs.-v, --verboseshows each log's id, ids, context and metadata under it.--jsonprints one JSON object per log, for scripts and agents.tailfollows over Lumber's live connection for apps on Dev and Pro plans, and checks every 5 seconds for the rest. In a terminal its connection state stays on a line under the logs;-qhides it.helpanywhere on the command line shows help, solumber logs -g helpprints help rather than searching. Search for-g Helpinstead: the match ignores case.- When a newer version is on npm, a command run at a terminal says so after its output, at most once a day, with the command to update. It asks npm at most once a day, while the command runs, so it never slows one down.
tail,mcp, piped output and CI never check;LUMBER_NO_UPDATE_CHECK=1turns it off.
The output takes the apps' colors: spinners, help and prompts in your accent (the one you picked in Lumber's Account screen), levels in their colors, and a square in each app's color before its name. Piped or with --json, it's plain text.
AI agents (MCP)
lumber mcp serves the same reads as MCP tools over stdio, using the session lumber login saved.
Claude Code:
claude mcp add lumber -- lumber mcp
On Windows, npm installs lumber as a .cmd file, which an agent can only start through cmd (installed with Scoop or downloaded, lumber is an .exe, and the line above works as it is):
claude mcp add lumber -- cmd /c lumber mcp
Claude Desktop, in its claude_desktop_config.json (on macOS and Linux, use the full path which lumber prints, since the app doesn't read your shell's PATH):
{
"mcpServers": {
"lumber": { "command": "/opt/homebrew/bin/lumber", "args": ["mcp"] }
}
}
On Windows, with npm's lumber:
{
"mcpServers": {
"lumber": { "command": "cmd", "args": ["/c", "lumber", "mcp"] }
}
}
With Scoop's or the downloaded lumber.exe, "command": "lumber" works there too.
Tools:
list_apps: your apps, and whether this computer can read each one.search_logs: the newest logs matching apps, a level, a time range and text.wait_for_logs: waits for new logs (errors and fatals unless told otherwise) and returns them grouped by message, with anext_afterto pass back, so an agent can watch in a loop without missing or repeating any.list_notes: what people wrote about an app's logs, with who wrote it.
Letting an agent watch for errors
Nothing watches unless you start it. In Claude Code, ask something like:
Watch Lumber-Test for errors with wait_for_logs. When one comes in, find the cause in this repo and fix it, leaving the change for me to review.
Or have it follow lumber tail Lumber-Test -l error --json -q, which prints one line per error.
Log messages, context and metadata are written by your app and the people using it: a form field, a URL or a crafted request can end up in a log. Every tool says so to the agent, but an agent that can edit your code is reading text anyone could have written. Keep its changes for review rather than letting it deploy.
How it stays private
Each app's logs are encrypted with its own key before they leave your servers (AES-256-GCM). The server keeps a copy of each app key wrapped to each person's account key, which it can't unwrap. Linking hands this computer your account key, wrapped by the approving device to a key this computer made for the link. The code you type ties that key to the link, and the account key comes back tagged with a secret only the code gives, so the server can neither choose where your account key goes nor hand this computer a key of its own. Then each command fetches the ciphertext and decrypts it here.
Requirements
- macOS, Windows, or Linux with a Secret Service (GNOME Keyring or KWallet).
- Node 20 or later, when installed with npm or Homebrew. Scoop's and the downloaded
lumbercarry their own. - A Lumber account, and a phone or Mac where Lumber already has your account key, to show the code that links this computer.
Publishing
Tag a release to trigger the publish workflow:
npm run release:patch # or release:minor / release:major: verifies, tags and pushes
License
MIT
Lumber MCP Fragen
Wie füge ich Lumber MCP zu Claude Code hinzu?
Führe claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cli in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Lumber MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie stellt Lumber den Datenschutz der Logs sicher?
Logs werden mit AES-256-GCM verschlüsselt, bevor sie den Server verlassen, und die Entschlüsselung erfolgt lokal auf deinem Computer unter Verwendung deines Account-Keys.
Welche Betriebssysteme werden unterstützt?
Lumber läuft auf macOS, Windows und Linux.