io.github.zw008/vmware-log-insight
Related Servers
Alternatives to io.github.zw008/vmware-log-insight
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for querying and analyzing logs from VMware Aria Operations for Logs, enabling log search, incident detection, and vROps correlation.64MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.-
- AlicenseAqualityBmaintenanceA read-only MCP server for querying Sumo Logic logs, enabling AI assistants to search and investigate application logs with opinionated tools and secure credential handling.56 npm1MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for exploring and searching OpenSearch clusters, enabling log analysis, index exploration, and query execution.8MIT
- AlicenseNot gradedqualityFmaintenanceA read-only MCP server that exposes Quickwit log search and aggregations to LLM clients, enabling natural language log investigation.Apache 2.0
- AlicenseAqualityBmaintenanceA read-only MCP server that enables AI assistants to search, aggregate, and explore OpenSearch log data through 12 tools for connectivity, index discovery, search, and aggregations.17MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: alert list/get/history handle alert definitions and trigger records, while log_search/log_aggregate/log_fields/log_version handle log exploration and diagnostics. There is no realistic overlap between alert_get and alert_history or between log_search and log_aggregate.
All tool names use lowercase snake_case and follow a consistent noun_verb pattern, with alert_ prefixed for alert operations and log_ prefixed for log operations. This creates a predictable and scannable naming scheme.
Seven tools is a well-scoped size for a focused read-only Log Insight API. Each tool earns its place and there is no redundancy or padding.
The toolset covers the main read workflows: version checking, field discovery, event search, aggregation, and alert definition/history inspection. The only gap is that the alert surface is intentionally read-only, so creating, updating, or deleting alerts requires external tooling.