rlg-mcp
The rlg-mcp server exposes RustLogs (rlg) log streams as MCP tools over stdio, enabling LLM agents to read, filter, and analyze structured log files via three tools:
tail_log: Retrieve the last N parseable rlg records from a log file (default: 100), rendered in Logfmt, with newest records last.filter_log: Filter records by minimum severity level (TRACE, DEBUG, VERBOSE, INFO, WARN, ERROR, FATAL, CRITICAL), by component name, and render results in any supported rlg LogFormat (e.g., Logfmt, JSON).summarize_errors: Scan a log file and return a JSON map ofcomponent → error_countfor all ERROR-and-above records, providing a fast error taxonomy for triage.
All tools are read-only, idempotent, and non-destructive, making them safe for use by AI agents such as Claude Desktop, Cursor, or mcp.run agents.
This is the Cargo workspace root. The library lives at
crates/rlg. Ten companion crates ship from this
workspace, all at lockstep version 0.0.11.
The rlg ecosystem
Crate | What it does | Use case |
Near-lock-free structured logging engine. 65k-slot ring buffer, deferred formatting, 14 output formats, native OS sinks ( | Embed structured logging in any Rust binary or library. | |
| Pipe | |
Model Context Protocol server exposing rlg streams as tools to LLM agents. | Claude Desktop, Cursor, mcp.run agents reading your logs. | |
OpenTelemetry network exporter (OTLP/HTTP JSON). | Ship records to Honeycomb, Datadog, Tempo, Jaeger, otelcol. | |
| axum, tonic, hyper, | |
| Structured logging from JS or WASI 0.2 components. | |
PII / secret redaction between | Compliance, GDPR, audit-trail safety. Built-in patterns for cards, JWTs, bearers, emails, IPs, AWS keys. | |
Test utilities — capture rlg records in a | Downstream library tests verifying their structured log output. | |
Log digest / analytics: count by level, top components, top errors, latency percentiles. CLI + library mode. | Operational dashboards, daily error reports, oncall triage. | |
| Automatic host-level context on every record without app code changes. | |
|
| Maintainer automation. |
Install one, install all
[dependencies]
rlg = "0.0.12"
rlg-otlp = "0.0.12" # ship to an OTLP collector
rlg-tower = "0.0.12" # HTTP middleware
rlg-redact = "0.0.12" # PII redaction
[dev-dependencies]
rlg-test = "0.0.12" # assertions in your testsCLI binaries:
cargo install rlg-cli # the `rlg` binary
cargo install rlg-mcp # the `rlg-mcp` MCP server
cargo install rlg-report # the `rlg-report` digest toolRelated MCP server: log-mcp
Tools
The MCP server crate, rlg-mcp, exposes rlg
log streams to LLM agents as three MCP tools over the stdio transport:
tail_log—path, optionaln(default 100) → lastnparseable records, rendered in Logfmt.filter_log—path, optionalmin_level/component/format→ records matching every supplied filter, in the chosenLogFormat.summarize_errors—path→ JSON map ofcomponent → error_countfor ERROR-and-above records.
Workspace layout
.
├── Cargo.toml # workspace manifest (profiles, members)
├── README.md # ← you are here
├── CHANGELOG.md / CONTRIBUTING.md / SECURITY.md
├── LICENSE-{APACHE,MIT}
├── crates/
│ ├── rlg/ # core library
│ ├── rlg-cli/ # `rlg` binary + filter/render lib
│ ├── rlg-mcp/ # MCP server
│ ├── rlg-otlp/ # OTLP/HTTP exporter
│ ├── rlg-tower/ # tower::Layer
│ ├── rlg-wasm/ # wasm-bindgen + WASI 0.2 component
│ ├── rlg-redact/ # PII / secret scrubber (Aho-Corasick)
│ ├── rlg-test/ # test utilities
│ ├── rlg-report/ # log digest binary + lib
│ ├── rlg-ebpf/ # Enricher trait + eBPF (Linux) scaffold
│ └── xtask/ # internal automation (publish = false)
└── .github/
└── workflows/
├── ci.yml # delegates to sebastienrousseau/pipelines
└── release.yml # workspace-aware crates.io publisherQuick links
Core docs:
crates/rlg/README.md· docs.rs/rlgContributing & signing policy:
CONTRIBUTING.mdSecurity policy:
SECURITY.mdRelease notes:
CHANGELOG.md
License
Dual-licensed under Apache 2.0 or MIT, at your option.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceAn MCP server that connects Claude (or any MCP compatible client) to your existing log infrastructure. Query, summarize, and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki, and Elasticsearch without writing filter expressions or leaving your editor.Last updated163MIT
- AlicenseAqualityDmaintenanceMCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.Last updated795MIT
- FlicenseBqualityDmaintenanceA log analysis MCP server that enables tailing, searching, filtering, and summarizing logs from local files and Docker containers.Last updated7
- Alicense-qualityCmaintenanceMCP server for collecting and analyzing CLI/web server error logs. Enables watching log files/directories, parsing common error patterns, and querying/analyzing logs through natural language.Last updated33MIT
Related MCP Connectors
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
MCP server exposing the Backtest360 engine API as tools for AI agents.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/rlg'
If you have feedback or need assistance with the MCP directory API, please join our Discord server