AI 클라이언트가 암호화된 로그를 검색하고, 애플리케이션 목록을 확인하며, 새로운 오류나 치명적인 이벤트를 실시간으로 모니터링할 수 있게 합니다.
다른 이름 infinitetoken/Lumber-CLI, lumber-cli, @infinitetoken/lumber-cli
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- 1,878
- 최신 버전
- 0.5.0
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
Lumber MCP란?
Lumber은(는) MCP server입니다. AI 클라이언트가 암호화된 로그를 검색하고, 애플리케이션 목록을 확인하며, 새로운 오류나 치명적인 이벤트를 실시간으로 모니터링할 수 있게 합니다.
프로젝트 README에서 생성된 요약
Lumber MCP server 정보
Lumber는 개발자가 Model Context Protocol을 통해 AI 에이전트를 암호화된 애플리케이션 로그에 연결할 수 있는 방법을 제공합니다. 이 MCP server는 macOS, Windows 또는 Linux에서 로컬로 실행되며, 기존 Lumber 계정 자격 증명을 사용하여 사용자의 기기에서 데이터를 복호화합니다. 계정 키를 사용하여 로컬에서 복호화가 진행되므로, Lumber 서버는 사용자의 로그 평문에 절대 접근할 수 없습니다.
사용자는 lumber mcp 명령어를 실행하고 Claude Desktop 또는 Claude Code와 같은 클라이언트 설정에 추가하여 서버를 구축할 수 있습니다. 이 서버는 접근 가능한 애플리케이션을 확인하는 list_apps, 텍스트 패턴과 시간 범위를 사용하여 특정 항목을 찾는 search_logs, 그리고 다른 팀원이 남긴 메모를 확인하는 list_notes 등 특정 도구를 제공합니다. 또한 에이전트가 새로운 오류나 치명적인 이벤트를 실시간으로 모니터링할 수 있는 wait_for_logs 도구를 포함하고 있어, 자동 디버깅 및 시스템 모니터링을 위한 유용한 유틸리티로 활용됩니다.
활용 사례
- 1실시간 애플리케이션 오류 모니터링AI 에이전트가 새로운 오류 또는 치명적인 이벤트를 감시하고 코드베이스에서 원인을 찾으려고 시도할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Lumber MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Lumber MCP 설치
$ claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliCursor에 Lumber MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}VS Code에 Lumber MCP 설치
.vscode/mcp.json
{
"servers": {
"lumber-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}VS Code CLI에 Lumber MCP 설치
$ code --add-mcp '{"name":"lumber-cli","type":"stdio","command":"npx","args":["-y","@infinitetoken/lumber-cli"]}'Claude Desktop에 Lumber MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}Codex에 Lumber MCP 설치
$ codex mcp add lumber-cli -- npx -y @infinitetoken/lumber-cliCodex config.toml에 Lumber MCP 설치
~/.codex/config.toml
[mcp_servers.lumber-cli] command = "npx" args = ["-y", "@infinitetoken/lumber-cli"]
Gemini CLI에 Lumber MCP 설치
$ gemini mcp add -s user lumber-cli npx -- -y @infinitetoken/lumber-cliGemini settings.json에 Lumber MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"lumber-cli": {
"command": "npx",
"args": [
"-y",
"@infinitetoken/lumber-cli"
]
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능infinitetoken/lumber-cli is public and reachablegithub.com/infinitetoken/lumber-cli ↗통과
- 패키지가 이 저장소를 소스로 명시@infinitetoken/lumber-cli names infinitetoken/lumber-cli as sourcenpmjs.com/package/@infinitetoken/lumber-cli ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @infinitetoken/lumber-clinpmjs.com/package/@infinitetoken/lumber-cli/v/0.5.0#provenan ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-14github.com/infinitetoken/lumber-cli ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @infinitetoken/lumber-cli통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음the package checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
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
Lumber MCP 질문
Lumber MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add lumber-cli -- npx -y @infinitetoken/lumber-cli를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Lumber MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Lumber는 로그 프라이버시를 어떻게 보장하나요?
로그는 서버를 떠나기 전 AES-256-GCM으로 암호화되며, 사용자의 계정 키를 사용하여 로컬 컴퓨터에서 복호화가 이루어집니다.
지원되는 운영 체제는 무엇인가요?
Lumber는 macOS, Windows, Linux에서 실행됩니다.