get_log_filesLABSCO 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 && local-logs-setup
USE CASES
01
Finding out what just broke
Pull the recent error entries, then tail the file around them for the lines that led up to it.
02
Working out which log to look in
List the log files with their metadata, rather than remembering which service writes where.
03
Chasing a specific request or ID
Search for the string across every log, or narrow it to one file when you already know where it happened.
04
Watching while you reproduce a bug
Monitor the file for changes as you trigger the problem, instead of re-tailing after each attempt.
05
Getting the state of things at a glance
Read the summary derived from the logs before deciding which file to open.
6 tools
Listed in project docs. Your client may show a different list.
tail_logget_errorsget_server_statuswatch_logsearch_logsBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g https://github.com/mariosss/local-logs-mcp-server
local-logs-setupMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"local-logs": {
"command": "local-logs-mcp",
"env": {
"LOGS_DIR": "./logs"
}
}
}
}
