Logmcp
Read-only MCP server giving AI assistants access to Linux server logs without shell access
- Pricing
- Open source
- Platforms
- CLI, Linux, API
- Version
- 0.7.7
- Listing updated
- today
Similar MCP servers
About Logmcp
Logmcp is an open-source MCP server for developer tools. It is available on CLI, Linux, API, self-hosted and vscode.
The README says LogMCP lets an AI assistant read log files on a remote Linux server while never giving it SSH or shell access. The server exposes whitelisted log files and systemd journal sources over HTTPS, with bearer-token authentication and access auditing through syslog, so the assistant can help diagnose problems without being able to change or execute anything on the machine.
Setup is handled by a quickstart command for trying it without root, or a permanent install with an interactive wizard that configures TLS (self-signed, custom certificate, or behind Caddy), tokens and a systemd service. Whitelist and blacklist glob patterns control which logs are visible, and per-client tokens can be added or revoked. Extensions can also expose external CLI tools or Redis-based workers as additional MCP tools.
The project is aimed at sysadmins and developers who want AI-assisted debugging of production, customer or hardened machines where least-privilege access matters more than convenience.
Tools this server provides (7)
Taken from the project documentation; the running server may differ.
- list_logs
- List all log files the server has been configured to expose
- read_log
- Read lines from a log file by head, tail, offset, or time window
- search_log
- Search a log file by regexp with optional context lines and time filter
- log_info
- File metadata: size, line count, last modified
- check_environment
- Server-side health checks for config, TLS, whitelist, syslog and databases
- check_config
- Show current server configuration and optional parameters at their defaults
- server_status
- Runtime status of the MCP layer and registered extensions
What it does
- Read-only log access
- Assistants can read and search configured log files but cannot modify, delete or execute anything.
- Whitelist and blacklist paths
- Glob patterns restrict which log files and paths the AI can see.
- systemd journal source
- Journald logs are available through a journald:// virtual source alongside regular files.
- Per-client bearer tokens
- Multiple tokens can be issued to different clients and revoked individually.
- Syslog audit trail
- Each access is recorded in syslog without logging the log content itself.
- Extensions and macros
- External CLI tools or Redis RPC workers can be added as MCP tools, and composite tools can be defined in YAML.
Good for
- Letting an AI assistant diagnose errors on a production server without SSH access
- Debugging customer or hardened machines under a least-privilege access policy
- Searching system and application logs from Claude Code or VS Code during an incident
- Sharing read-only log visibility with a remote CI or support agent
Pricing
Open source
Open source under the MIT License.
Logmcp FAQ
Does the AI get shell access?
No. The README states the AI cannot execute anything or read beyond the whitelisted log paths, and no SSH is required.
Which AI clients are supported?
The README names Claude Code, VS Code and Claude Desktop, and the CLI can print client configuration for each.
Can I use it over SSH instead of a public endpoint?
Yes. The README describes forwarding the port over an SSH tunnel, with a bearer token still required.
Is Logmcp free?
Yes. Logmcp is open source, so you can use and self-host it for free.
What are the best alternatives to Logmcp?
The closest alternatives to Logmcp are Linux MCP daemon (mcpd), ClosedMCP, VPS MCP & Digital Secretary, MCP Server Filesystem and Super Log.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.