MCP for monitoring local application logs with real-time tailing, error tracking, and log search capabilities.
Local Logs MCP server exists for a simple reason — assistants are far more useful when they can act on Local Logs directly instead of describing what you should do. MCP for monitoring local application logs with real-time tailing, error tracking, and log search capabilities.
Once Local Logs is connected, these are the calls the assistant has available:
get_log_files — List available log files with metadatatail_log — Get last N lines from a log fileget_errors — Get recent error log entriesget_server_status — Server status summary from logswatch_log — Monitor log file for changessearch_logs — Search for text in log filesYou will need 2 environment variables: LOGS_DIR, LOG_EXTENSIONS. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Usage on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Local Logs's toolset — get_log_files, tail_log, get_errors and 3 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_log_files | List available log files with metadata |
| tail_log | Get last N lines from a log file |
| get_errors | Get recent error log entries |
| get_server_status | Server status summary from logs |
| watch_log | Monitor log file for changes |
| search_logs | Search for text in log files |
{
"mcpServers": {
"local-logs": {
"command": "npx",
"args": ["-y", "local-logs-mcp-server"],
"env": {
"LOGS_DIR": "./logs"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOGS_DIR | Filesystem location the server is allowed to use. | Optional |
| LOG_EXTENSIONS | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.