elog-mcp
Related Servers
Alternatives to elog-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.-
- FlicenseNot gradedqualityCmaintenanceEnables read-only querying of a local Grafana Loki instance, providing log search, service listing, and health check capabilities.-

hepdata-mcpofficial
AlicenseAqualityBmaintenanceEnables discovery of HEPData records, tables, and data access with read-only operations and export links.9GPL 2.0- FlicenseAqualityBmaintenanceProvides read-only search and retrieval of archived emails, archive statistics, health, and ingestion sources, with an optional administrative toolset for user, role, reindexing, and queue management.6-
- AlicenseAqualityDmaintenanceRead-only MCP server for exploring and searching OpenSearch clusters, enabling log analysis, index exploration, and query execution.8MIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server that converts Elasticsearch logs into citable evidence for AI agents, offering deterministic log summarization and search tools.-
TDQS
Scored across 5 tools
Each tool maps to a distinct operation (listing logbooks, searching, reading a single entry, browsing recent entries, fetching attachments), so confusion is unlikely. However, elog_get_recent_entries overlaps with elog_search's last_days and reverse options, making the boundary between them slightly less sharp.
The elog_ prefix and verb-first style are consistent, and most tools follow a verb_noun pattern such as elog_list_logbooks, elog_get_entry, and elog_get_attachment. elog_search is the one outlier because it omits an explicit object, which is a minor deviation from the otherwise predictable pattern.
Five tools is a well-scoped size for a read-only logbook client. Each tool covers one essential need—discovering logbooks, searching entries, reading full entries, browsing recent entries, and downloading attachments—without unnecessary redundancy or bloat.
The read-oriented surface is complete for searching, reading, and retrieving attachments from ELOG entries. The only notable gap is the absence of write or lifecycle tools such as creating, replying to, or editing entries, though this appears to be an intentional read-only scope.