SkillAgentSearch skills...

logsift

Find out what your app did, from its logs to its threads, and ask AI about it (GitHub Copilot or Claude Code, MCP): multi-GB logs, live tail, filters, request tracing, exceptions, thread dumps, GC logs, heap and crash dumps, JVM profiling, SSH. Windows, macOS, Linux.

Install / Use

claude mcp add bdarwin -- npx -y github:bdarwin/logsift

If the server publishes to npm under a different name, use that package instead β€” check the repo README.

About this skill
πŸ”Œ

MCP Server

Model Context Protocol server

Quality Score

74/100

Category

Marketing

Supported Platforms

Claude Code
Claude Desktop
GitHub Copilot

Our assessment of logsift

logsift scores 74/100 on our quality scale, 618th of 649 Marketing skills we index.

Its MCP Server is 85 KB long, well organised into 47 sections with 5 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
21/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so logsift is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

logsift compared with similar skills

All 4 of these similar skills score higher than logsift; compare them before choosing.

SkillScoreStarsUpdatedFormat
logsift (this skill)by bdarwin743todayMCP Server
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
hyperframesby heygen-com10087.1ktodayCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
headroomby headroomlabs-ai10080.2ktodayCLAUDE.md

Frequently asked questions

How do I install logsift?
Run claude mcp add bdarwin -- npx -y github:bdarwin/logsift. The install tabs above show the steps for each supported agent.
Which AI agents does logsift work with?
It is written for Claude Code, Claude Desktop and GitHub Copilot, as a MCP Server file. Other agents that read the same format can often use it too.
Is logsift safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is logsift still maintained?
The repository was last updated today, so logsift is actively maintained.

Logsift

Latest release Build License: MIT Platforms

Find out what your app did, from its logs to its threads. Logsift opens gigabytes of logs instantly, tails them live and points out errors, bursts and restarts. Follow one request through every log, even inside zips; see exceptions grouped by cause; chart how long things take. Then go deeper: it explains Java and Python thread dumps, and attaches to running JVMs to profile them and look at their heap, on your computer or on a server. Windows, macOS and Linux.

Ask AI about it. GitHub Copilot or Claude Code answers in Logsift's window, reading your logs, thread dumps, GC logs and crash dumps with Logsift's own tools: why did checkout fail at 10:42? It cites lines you can click, asks before it reads anything you haven't opened, and shows what each answer cost. Or ask from your coding agent (Copilot, Claude Code or any agent that supports MCP), and Logsift does the reading on your computer, with secrets masked.

Logsift with four filters combined as (A OR B) AND NOT C, the timeline on top and the highlight bar on the right

The assistant beside a log: the question, the lines Logsift read for it, and the answer with links to them

User guide: what each view shows, what its colours and numbers mean, and what to do about them (also Help β†’ Documentation in the app).

Features

  • Huge files, instantly. A 1 GB log shows its first lines in 0.12 s and is fully indexed in 0.26 s. Scrolling and jumping to any line stay smooth at any size.
  • Live tail. Follow a growing log, including through rotation and truncation. You choose whether changes load automatically or only when you click Reload.
  • Find All. Run several searches at once (text, whole word, regex, any case), each in its own color, and search within the results.
  • Filters. Show, hide or mark lines and combine filters with AND, OR and NOT. Filter by log level and time range, keep stack traces with their line, and add context lines.
  • Timeline and highlight bar. See error bursts at a glance and drag over a time range to zoom in.
  • Columns. Time, level, thread, logger and message are parsed automatically. JSON logs and CSV files work too, with a pretty-printed details view.
  • Your own log formats. Drop a log file and Logsift works out its layout, or paste your log4j, logback, java.util.logging or Python logging setup (even a whole logback.xml or log4j2.xml: each layout in it becomes a format). A live preview shows how lines split into columns.
  • Exceptions by root cause. Java stack traces, .NET exceptions (with their inner ones) and Python tracebacks grouped by what went wrong and where in your own code: "60 Γ— NullPointerException at PriceCalculator.discount", with the stack, what wrapped it, and each time it happened.
  • Metrics from the messages and columns. How long things that start and end took ("Started job sync-7" … "Finished job sync-7"), the ones that never ended, the numbers messages report (placed in 345 ms, queue size=42) and columns of numbers (duration_ms in a CSV) as charts over time, with the slowest lines a click away.
  • Follow a request. Right-click a line with a trace or request ID (or select any text) β†’ Follow: the request's lines in order, across threads, open logs or a whole folder (zips too), with the time between them and the longest wait marked.
  • Tree of loggers. Loggers (or threads, components, hosts) as a package tree beside the log, with line counts. Uncheck a branch to hide its lines, double-click one to see only it.
  • Zips, .gz files and the web. Drop a .zip and it opens as a tab with its folders and files (zips inside it too); open any of them as a log, with everything a log has, merge them by time, or search them all. A .gz opens directly. Open logs from web addresses, or download several and search them together.
  • Folder search. Search a whole folder in parallel, including inside .gz and .zip files, and zips inside zips.
  • Remote logs over SSH/SFTP. Browse the server, pick a file, and it stays up to date as the remote log grows.
  • Analyze. See the top messages by count, compare a bad run with a good one, and merge several logs by time.
  • Query with SQL. A Query tab asks a log or a CSV anything SQL can (errors per minute, the slowest requests, percentiles, joins with another file) in milliseconds over millions of lines, read-only; double-click a result to see its line. Coding agents can ask it too.
  • Pivot tables and charts. Group a CSV file's rows, sum, count or average its values, split them across columns and chart them, as in a spreadsheet; double-click a cell to see its rows.
  • Compare CSV files by key. Two exports of the same table, in any row order: pick the key columns (one is suggested), choosing the files in a browser on each side, inside zips too, and see what was added, removed and changed, value by value (old β†’ new), with changes per column, numbers within a tolerance, and an export of the differences. A million rows compare in seconds.
  • Compare text and folders, merge with git. Two folders (or zips) file by file; two text files or logs side by side, with the changed words marked and times, numbers or IDs masked so two runs line up; a three-way merge for conflicts; Logsift can be git's difftool and mergetool.
  • Java threads (and Python's). Open thread dumps (jstack, jcmd, or kill -3 output inside a log; py-spy dump and faulthandler for Python), or attach to a running JVM on your computer, on a server over SSH, or through its JMX port. Logsift points out deadlocks, threads queueing for a lock, stuck and busy threads and full thread pools, and shows each thread over time.
  • Safe around production. Every action that reaches a running JVM says what it costs the service before it runs (a stop, a full GC, CPU, disk, network), and Logsift never removes files on a server. See What Logsift does to a running service.
  • A log knows its JVM. Open a log and Logsift names the JVM writing it, with its threads, profile and heap a click away. Right-click a line to see its thread's stack; from a thread, show only its lines.
  • Heap dumps, explained. Open a .hprof file and Logsift says what fills the memory in plain sentences ("one HashMap in static SessionCache.CACHE holds 1.2 GB: mostly 20,000 sessions"), and for any object, the chain of references that keeps it alive. Dumps of tens of GB open with the app's usual 2 GB of memory: a 12 GB dump with 223 million objects in about 2Β½ minutes.
  • GC logs, explained. Open a Java GC log (Java 8 to 25; G1, Parallel, Serial, CMS, ZGC, Shenandoah) and Logsift says how much of the time the program stood still, what the longest pauses were and why, whether the memory left after GC keeps growing, and what went wrong (full collections, evacuation failures, allocation stalls, System.gc() calls), each with what to try; with charts of the heap, pauses, allocation and time in GC.
  • Crash dumps, explained. Open a Windows dump (.dmp, .mdmp, full or mini, of any program) or a Java hs_err_pid file, and Logsift says what happened in plain words ("Access violation: reading address 0x18, a null pointer, in OrdersService!Order::total"), the code to blame, what to try, and every thread's stack, with threads that share a stack together. Stacks are rebuilt from the dump itself, with names from your PDB files and, if you let it, Windows' own from Microsoft. For a JVM crash it explains how it happened (native library, JNI, Unsafe, the garbage collector, the JIT compiler, out of memory) and which other threads and libraries may have caused it.
  • Ask the assistant about your logs (beta). A chat with GitHub Copilot or Claude Code, in its own tab, beside the log or in a window of its own (Ctrl+I): it reads the open logs and your services' logs with Logsift's tools, knows where they are and what time it is (what went wrong in login this morning?), cites lines you click to see, draws GC charts, and asks before taking a thread dump or reading a file you haven't opened. Each answer shows its model and cost; every chat is kept and searchable. Rate answers πŸ‘/πŸ‘Ž, and View β†’ Assistant Audit shows which questions went wrong or cost the most, and why. Settings β†’ Assistant shows what it's told. See the Assistant.
  • Ask from your coding agent. GitHub Copilot, Claude Code and other agents that support MCP (or skills, where MCP is blocked) can call Logsift: ask in the chat why a log is full of timeouts, and Logsift reads it on your computer and answers with the findings and line numbers; crash dumps too. Read-only, with secrets masked. See Coding agents.
  • Profiling and memory. Flame graphs of a JVM's CPU, wall-clock time, allocations, live objects (memory leaks), locks, native memory and native leaks, calls of a method and slow calls, or hardware events, with async-profiler or the JVM's own Flight Recorder. Compare runs, see who calls a method, and find which classes fill the heap and keep growing.
  • Also: bookmarks, alerts on new matching lines, export, sessions and recent files, many text encodings (UTF-8, UTF-16, Windows code pages, Shift_JIS, GB18030 and more), and light and dark mode.

Download

Get the latest version from the Releases page:

| System | File | |---|---| | Windows (x64, ARM64) | Logsift-<version>-windows-x64.msi / -windows-arm64.msi: installer, no admin rights needed. Or the .zip: unzip, run Logsift\Logsift.exe | | macOS (Apple Silicon, Intel) | Logsift-<version>-macos-arm64.dmg / -macos-x64.dmg | | Debian / Ubuntu | Logsift-<version>-linux-x64.deb | | Other Linux (x64, ARM64) | Logsift-<version>-linux-x64.tar.gz / -linux-arm64.tar.gz: unpack, run Logsift/bin/Logsift | | Any OS with Java 21+ | Logsift-<version>-any-java21.zip: run bin/logsift |

The native downloads include their own Java runtime, so nothing else needs to be installed. They are not code-signed yet:

  • macOS: if it says the app is damaged or can't be opened, run xattr -dr com.apple.quarantine /Applications/Logsift.app.
  • Windows: if SmartScreen warns, choose More info β†’ Run anyway.

Builds of the latest code are on the snapshot release. What changed in each version is in the CHANGELOG.

Opening logs

  • Files: File β†’ Open, or drag files onto the window. On Windows, right-click files or a folder β†’ Logsift β†’ Analyze (a GC log straight to the GC view, a thread dump to Threads, a heap or crash dump to theirs), Open, Compare (two selected) or Search (a folder); Logsift is also in the Open with list of .log, .txt and .out files, without taking over what double-click does. On macOS, use Open With or drop files on the Dock icon. If Logsift is already running, files open in the same window.
  • Folders: File β†’ Open Folder… (or drop a folder on the window) shows a folder's files in a tab, as a tree with sizes, like a zip's: filter them by name, open files as logs, Merge by Time, and Find in all files (Ctrl+F in that tab) searches the folder. Refresh lists the files again; a very big folder shows it

Truncated for display β€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategoryMarketing
Updated13h ago
Forks0

Languages

Java

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

1 low
logsift β€” MCP Server: Install & Safety Check | SkillAgent