Labsco
MCP SERVER

Local Logs MCP Server

by mariosss

Point the assistant at your app's log directory and let it read, tail and search it.

Runtime Debugging & Crash Analysis
Summary
The log file in the conversation, not in another terminal.

Debugging a local app usually means one window running it and another tailing its log. Handing the tail, the error filter and the search to the assistant puts the stack trace and the code in front of the same reader at the same time.

What it is

A local MCP server for application log files. It discovers the log files in a configured directory, tails the last N lines, pulls recent errors, searches for text across logs, watches a file for changes, and summarizes server status from what the logs say.

What you get
  • Available log files discovered and listed with their metadata
  • The last N lines of a named file
  • Recent error entries, without having to name the file
  • A server status summary derived from log analysis
  • A log file monitored for changes
  • Text searched across the logs, or scoped to one file
  • Custom log directories and file extensions
Requirements

A recent Node.js, plus read access to the directory the logs are written to. The README's npm name, local-logs-mcp-server, is not on the registry; the install script sets the server up and writes the Cursor configuration for you.

Setup effort

One command — npm install -g https://github.com/mariosss/local-logs-mcp-server