エージェントを強化
公開元からインストールします。PlugMCP のエンドポイントではありません。
リモート URL か、手元のマシンのコマンドか 2 つのインストール方法の違い
PlugMCP で実行
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
起動公開元より
MCP server — read-only log access for AI assistants. Debug your Linux server with AI, without giving the AI shell access.
No SSH. No write permissions. The AI reads your logs over HTTPS and helps you diagnose problems, while your server stays fully under your control.
MCP server — read-only log access for AI assistants. Debug your Linux server with AI, without giving the AI shell access.
LogMCP is an open-source MCP server that exposes log files on a remote Linux server to AI assistants (Claude Code, VS Code, Claude Desktop). Access is read-only, token-authenticated, and fully audited via syslog.
Try LogMCP in under a minute — no config file, no root, no systemd:
logmcp quickstart
The command checks your group memberships (adm, systemd-journal), generates a bearer token and a self-signed TLS certificate, starts the server, and prints a ready-to-paste claude mcp add command.
Running as root? Pass --user <name> and LogMCP will add the user to the required groups and re-launch as that user — root is not needed for future starts.
Note: Token and certificate are ephemeral. The token changes on every start. For a permanent setup use Option B.
logmcp quickstart --port 7789 --token mytoken # optional flags
After testing, remove the server from Claude Code:
claude mcp remove logmcp-quickstart
1. Install
go install github.com/kascada/logmcp@latest
Or install the pre-built .deb (replace x.y.z with the latest version):
curl -LO https://github.com/kascada/logmcp/releases/download/vx.y.z/logmcp_x.y.z_amd64.deb
sudo dpkg -i logmcp_x.y.z_amd64.deb
2. Run the setup wizard
sudo logmcp setup
Guides you through TLS mode, bearer token, and systemd service — then prints a ready-to-paste client config snippet.
3. Add to your AI client
logmcp client-config claude-code # or: vscode | claude-desktop
Paste the output into your MCP client config. Done — your AI can now read the server's logs.
You give the AI a read-only window into your logs. That's it.
This makes LogMCP ideal for situations where you need AI-assisted debugging but cannot or do not want to grant shell access: production servers, customer machines, hardened environments, or any setup where least-privilege matters.
SSH is also supported. If your AI client is Claude Code running locally with an SSH key, you can use LogMCP over an SSH tunnel instead of a public HTTPS endpoint. See SSH Tunnel Setup below.
journald://) as a virtual log sourceThe wizard (sudo logmcp setup) covers:
Whitelist/blacklist and journald are configured directly in /etc/logmcp/config.yaml after setup.
Any value in config.yaml can reference environment variables using ${VAR} or $VAR syntax. The substitution happens before the file is parsed, so it works everywhere — tokens, paths, DSNs, etc.
auth:
tokens:
- name: claude
token: ${LOGMCP_TOKEN}
scopes: [read]
extensions:
clitool:
- name: switchboard
command: /usr/local/bin/switchboard
timeout_seconds: 10
Unset variables expand to an empty string. To keep a literal $ in a value, use $$.
After setup, start the server:
sudo systemctl start logmcp
These are the tools LogMCP exposes to AI assistants:
Extensions may add further tools — their names are prefixed with the extension name (e.g. myapp_status for an extension named myapp).
LogMCP can expose any external program or service as additional MCP tools — no custom MCP server required. The AI sees them alongside the built-in log tools.
Any program that implements the clitool interface (list / call subcommands) can be registered. LogMCP calls <command> list at startup to discover tools, and forwards each tool call to <command> call <tool> --token-stdin.
extensions:
clitool:
- name: myapp
command: /usr/local/bin/myapp-ctl
timeout_seconds: 10
This spawns a subprocess per call — suitable for any program on the same or a remote host.
For programs running on the same host, the RPC variant avoids the per-call process-startup overhead (relevant for Python programs where interpreter startup and imports add noticeable latency). Instead of spawning a subprocess, LogMCP pushes a request onto a Redis list and waits for the worker's reply.
extensions:
clitool:
- name: myapp
command: /usr/local/bin/myapp-ctl # still used for `list` at startup
mode: rpc
redis_addr: "127.0.0.1:6379"
timeout_seconds: 5
The worker reads requests from a Redis list and pushes its reply to a per-request reply key. See docs/RPC.md for the full protocol.
The bearer token from each incoming MCP request is forwarded to the extension — either via stdin (CLI mode) or as caller metadata in the RPC envelope. The extension can verify it or trust the pre-resolved identity.
Real-world scenarios where LogMCP makes the difference — see docs/case-studies.md:
If you are using Claude Code locally and already have SSH access to the server, you can run LogMCP without a public HTTPS endpoint:
# Forward remote port 7788 to localhost
ssh -L 7788:127.0.0.1:7788 user@yourserver
# Then point your MCP client at https://localhost:7788
LogMCP still requires a bearer token over the tunnel — the SSH layer adds transport security, the token controls which client can connect.
MIT License — see LICENSE.
MCP server — read-only log access for AI assistants. Debug your Linux server with AI, without giving the AI shell access.
ツール
ツール一覧はまだありません。リモートサーバーは、最初のヘルスチェック後に取得されます。
よくある質問
このページで Cursor、Claude Desktop、Claude Code、VS Code 用の stdio 設定をコピーできます。PlugMCP のプロキシではなく、公開元のインストール方法を使います。
このレコードに必須の環境変数は記載されていません。
Logmcp は stdio 経由でローカル実行されます。
最終チェックは 2026-10-28 です。 MCP server — read-only log access for AI assistants. Debug your Linux server with AI, without giving the AI shell access.
