Enterprise DNA Enterprise DNA
M MCP Servers Developer low

kascada/logmcp

by Various

MCP server — read-only log access for AI assistants. Debug your Linux server with AI, without giving the AI shell access.

MCP

kascada/logmcp

Added 7 June 2026

#claude #debugging #devops #linux #log-viewer #logging #mcp #model-context-protocol

Overview

MCP server that provides read-only access to Linux logs for AI assistants. Written in Go, it enables debugging without granting shell access to the AI.

Best for

Best for
Developers who want AI assistants to securely inspect Linux server logs without giving shell access

Use cases

  • Give an AI assistant read-only access to server logs for debugging
  • Integrate log inspection into AI-powered monitoring workflows via MCP
  • Enable AI tools to analyze logs without compromising security

How to use

Install

go install github.com/kascada/logmcp@latest

Tools exposed

  • list_logs
  • read_log
  • search_log
  • log_info
  • check_environment
  • check_config
  • server_status

Tested with

Claude Code, VS Code, Claude Desktop

Example client config

auth:\n  tokens:\n    - name: claude\n      token: ${LOGMCP_TOKEN}\n      scopes: [read]\nextensions:\n  clitool:\n    - name: switchboard\n      command: /usr/local/bin/switchboard\n      timeout_seconds: 10

Notes

MCP server that provides read-only access to Linux logs for AI assistants. Written in Go, it enables debugging without granting shell access to the AI.

1 stars on GitHub. Last updated 2026-06-04. Licensed MIT.

Use cases

  • Give an AI assistant read-only access to server logs for debugging
  • Integrate log inspection into AI-powered monitoring workflows via MCP
  • Enable AI tools to analyze logs without compromising security

Pros

  • Read-only design ensures the AI cannot modify system files or execute commands
  • Lightweight Go implementation with minimal dependencies
  • Simple MCP integration for existing AI assistant toolchains

Cons

  • Only one star on GitHub indicates very limited community adoption or testing
  • No mention of support for non-Linux systems or custom log formats
  • Read-only access may not cover all debugging scenarios that require interactive shell commands

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Read-only design ensures the AI cannot modify system files or execute commands
  • Lightweight Go implementation with minimal dependencies
  • Simple MCP integration for existing AI assistant toolchains

Cons

  • Only one star on GitHub indicates very limited community adoption or testing
  • No mention of support for non-Linux systems or custom log formats
  • Read-only access may not cover all debugging scenarios that require interactive shell commands
Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

Running a business, not writing the code? See the MCP servers picked for operators, and get your first one wired up with us.

Operator picks