log-mcp

Read-only Model Context Protocol (MCP) server for log analysis. A host runs the log-mcp binary; the process speaks MCP over stdio (JSON-RPC on stdin/stdout) and exposes tools to inspect log data without mutating underlying sources.

Detailed, maintained documentation is in [`docs/`](docs/). The sections below are a compact overview; for environment variables, the full tool catalog, security limits, parsing behavior, and CI, follow the links.

| Resource | Purpose | |----------|---------| | **docs/README.md** | Documentation index and update guidance. | | **docs/architecture.md** | System design: MCP stdio, sources, security limits, parsing, normalization, pipeline. | | **docs/tools.md** | Tool reference: parameters and JSON results for every MCP tool. | | **docs/client-contract.md** | Stdio/MCP expectations and how errors surface. | | **docs/usage.md** | Build, env vars, host configuration, workflows. | | **docs/development.md** | Contributor workflow and doc ownership. | | **docs/testing-and-ci.md** | Tests, fixtures, govulncheck, go mod tidy gate, CI workflows. | | **docs/releases.md** | Tags, release builds, versioning. | | **CHANGELOG.md** | Version history (Keep a Changelog). | | **docs/troubleshooting.md** | Common failures and fixes. | | CONTRIBUTING.md | Branches, build/test commands, PR checklist. | | SECURITY.md | Reporting vulnerabilities. | | CODE_OF_CONDUCT.md | Community expectations. | | LICENSE | Apache License 2.0. |

Active development on the develop branch. The MCP tool surface and JSON shapes may still evolve; pin releases or digests for production hosts if you need s