logpiper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_new_logsC | Get new logs since a specific cursor position (streaming) |
| list_sessionsB | List all logging sessions with metadata |
| search_logsC | Search through logs with a query string |
| get_logs_paginatedC | Get logs with cursor-based pagination and automatic chunking |
| cleanup_sessionsC | Cleanup sessions: intelligent cleanup based on criteria or complete reset of all data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Sessions | List of currently active logging sessions |
| Sessions Overview | Overview statistics of all sessions |
TDQS
Scored across 5 tools
Most tools have clearly distinct roles, but get_new_logs and get_logs_paginated both retrieve logs and could be confused by an agent skimming descriptions. The streaming vs. pagination distinction is present but requires careful reading.
All tool names follow a consistent verb_noun pattern (get_, list_, search_, cleanup_), with no mixed conventions or vague verbs. The naming is predictable and easy to extrapolate.
Five tools is a well-scoped size for a log management server, covering retrieval, search, session listing, and cleanup without unnecessary bloat or feeling thin.
The read and lifecycle side is reasonably covered with search, pagination, streaming, and cleanup, but there is no ingestion or write capability for logs/sessions. This is a notable gap if the server is meant to manage logs end-to-end.