Permet à un client IA de rechercher dans des logs déchiffrés, de lister les applications et de surveiller en temps réel l'apparition de nouvelles erreurs ou d'événements fatals.
Aussi connu sous infinitetoken/Lumber-CLI, lumber-cli, @infinitetoken/lumber-cli
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- 1 878
- Dernière version
- 0.5.0
- Dernier commit
- 14 nov. 2026
- Licence
- MIT
Qu'est-ce que Lumber MCP ?
Permet à un client IA de rechercher dans des logs déchiffrés, de lister les applications et de surveiller en temps réel l'apparition de nouvelles erreurs ou d'événements fatals.
Résumé généré à partir du README du projet
À propos du MCP server Lumber
Lumber offre aux développeurs un moyen de connecter des agents IA à leurs logs d'applications chiffrés via le Model Context Protocol. Ce MCP server s'exécute localement sur macOS, Windows ou Linux et utilise vos identifiants de compte Lumber existants pour déchiffrer les données sur votre propre machine. Comme le déchiffrement s'effectue localement avec votre clé de compte, les serveurs Lumber n'ont jamais accès au texte brut de vos logs.
Les utilisateurs peuvent configurer le serveur en exécutant la commande lumber mcp et en l'ajoutant à la configuration de leur client, comme Claude Desktop ou Claude Code. Le serveur propose des outils spécifiques, notamment list_apps pour visualiser les applications accessibles, search_logs pour trouver des entrées précises via des motifs textuels et des plages horaires, et list_notes pour consulter les commentaires laissés par d'autres membres de l'équipe. Il inclut également un outil wait_for_logs qui permet à un agent de surveiller en temps réel l'apparition de nouvelles erreurs ou d'événements fatals, ce qui en fait un utilitaire précieux pour le débogage automatisé et la surveillance système.
Ce que vous pouvez faire avec
- 1Surveiller les erreurs d'application en temps réelUn agent IA peut guetter l'apparition de nouvelles erreurs ou d'événements fatals et tenter d'en identifier la cause dans votre base de code.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Lumber MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Lumber MCP dans Claude Code
$ claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliInstaller Lumber MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Installer Lumber MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"lumber-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Installer Lumber MCP dans VS Code CLI
$ code --add-mcp '{"name":"lumber-cli","type":"stdio","command":"npx","args":["-y","@infinitetoken/lumber-cli"]}'Installer Lumber MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Installer Lumber MCP dans Codex
$ codex mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliInstaller Lumber MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.lumber-cli] command = "npx" args = ["-y", "@infinitetoken/lumber-cli"]
Installer Lumber MCP dans Gemini CLI
$ gemini mcp add -s user lumber-cli npx -- -y @infinitetoken/lumber-cliInstaller Lumber MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleinfinitetoken/lumber-cli is public and reachablegithub.com/infinitetoken/lumber-cli ↗Réussi
- Le nom du package correspond au dépôt source@infinitetoken/lumber-cli names infinitetoken/lumber-cli as sourcenpmjs.com/package/@infinitetoken/lumber-cli ↗Réussi
- Provenance du build (attestation Sigstore)Sigstore attestation for @infinitetoken/lumber-clinpmjs.com/package/@infinitetoken/lumber-cli/v/0.5.0#provenan ↗Réussi
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-14github.com/infinitetoken/lumber-cli ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from @infinitetoken/lumber-cliRéussi
- Aucun avis critique dans le package ou ses dépendancesthe package checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHub@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
Questions sur Lumber MCP
Comment ajouter Lumber MCP à Claude Code ?
Exécutez claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cli dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Lumber MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Comment Lumber garantit-il la confidentialité des logs ?
Les logs sont chiffrés avec AES-256-GCM avant de quitter le serveur, et le déchiffrement s'effectue localement sur votre ordinateur à l'aide de votre clé de compte.
Quels systèmes d'exploitation sont pris en charge ?
Lumber fonctionne sur macOS, Windows et Linux.