Loglens runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Homelab log investigation over local logs: tail, errors, search, timeline, context.
Nothing serious here today
Today is the operative word: we check Loglens every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add loglens -- npx -y @reneturcios/loglens{
"mcpServers": {
"loglens": {
"command": "npx",
"args": [
"-y",
"@reneturcios/loglens"
]
}
}
}[mcp_servers.loglens]
command = "npx"
args = ["-y", "@reneturcios/loglens"]{
"mcpServers": {
"loglens": {
"command": "npx",
"args": [
"-y",
"@reneturcios/loglens"
]
}
}
}{
"servers": {
"loglens": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/loglens"
]
}
}
}Alternatives to Loglens
same job, measured the same waySearch logs, investigate errors, check deployments, and monitor uptime for your elmah.io org.
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.
Timestamped audit log for every AI conversation — stored locally in SQLite, owned by you.
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
Persistent memory for AI agents — log and recall conversation context over MCP.
Syslog receiver and MCP server for homelab log intelligence.
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
Loglens — questions
Answers built from our own checks of this server.