vmware-aria-logs
Provides tools for querying and analyzing logs from VMware Aria Operations for Logs, including log search, incident detection, dashboard listing, and optional correlation with VMware Aria Operations resources and alerts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vmware-aria-logs Show me the latest error events from the past 2 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VMware Aria Operations for Logs — MCP Server
MCP server for querying and analyzing logs from VMware Aria Operations for Logs (formerly vRealize Log Insight). Provides log search, mass incident detection, and optional VMware Aria Operations (vROps) correlation.
Built for use with Claude Code, Claude Desktop, LobeChat, and any MCP-compatible client.
Features
Log Search — Query events with time range, text filters, and field constraints via Log Insight API v2
Incident Detection — Signature-based clustering to identify mass log incidents (Stormbreaker engine)
API Surface Probe — Detect appliance version and available API endpoints
Dashboard Listing — Enumerate saved dashboards (legacy vRLIC API, deprecated on 8.18+)
vROps Correlation — Cross-reference log entities with Aria Operations resources and alerts
Related MCP server: Log Analyzer MCP Server
Quick Start
Install via uvx (recommended)
uvx vmware-aria-logsInstall via pip
pip install vmware-aria-logsRun with environment variables
export LI_BASE_URL=https://loginsight.example.com
export LI_USERNAME=admin
export LI_PASSWORD=your-password
export LI_PROVIDER=Local
vmware-aria-logsMCP Tools
Tool | Description |
| Search log events with time range, text filter, field constraints |
| Get appliance version and probe API surface |
| List saved dashboards (legacy vRLIC API, deprecated on 8.18+) |
| Mass incident detection via signature clustering |
| Find entities in Aria Operations by name |
| Get alerts for specific vROps resources |
Configuration
Required Environment Variables
Variable | Description | Default |
| Log Insight appliance URL | — |
| API username |
|
| API password | — |
| Auth provider (Local, ActiveDirectory) |
|
| Verify TLS certificates |
|
| HTTP request timeout (seconds) |
|
Optional (vROps Correlation)
Variable | Description | Default |
| Aria Operations URL | — |
| vROps username |
|
| vROps password | — |
| Auth source |
|
| Verify TLS certificates |
|
| HTTP request timeout (seconds) |
|
Claude Code / MCP Client Configuration
{
"mcpServers": {
"aria-logs": {
"command": "uvx",
"args": ["vmware-aria-logs"],
"env": {
"LI_BASE_URL": "https://loginsight.example.com",
"LI_USERNAME": "admin",
"LI_PASSWORD": "your-password"
}
}
}
}Why This Server?
VMware Aria Operations for Logs (Log Insight) is widely deployed in enterprise VMware environments, but lacks modern AI-assisted log analysis tooling. This MCP server bridges that gap:
Zero dependencies beyond the MCP SDK — uses Python stdlib
urllibfor HTTPStormbreaker engine — unique signature-based clustering that finds mass incidents humans miss
vROps correlation — cross-reference log events with infrastructure health in a single conversation
Works on v8.x+ — tested on Aria Operations for Logs 8.18.3, gracefully degrades deprecated APIs
Also Available On
License
MIT
Available Tools
6 toolsdetect_incidentsA
Detect mass log incidents using signature clustering (Stormbreaker engine).
Queries events, groups them by normalized signature pattern, and returns clusters that exceed the mass threshold — ranked by event count.
Args: lookback_minutes: How far back to search (default 60 minutes). search_term: Free-text search term (optional, empty = all events). event_limit: Max events to fetch for analysis (default 5000). mass_threshold: Min events per signature to qualify as incident (default 5). max_incidents: Max incidents to return (default 20).
Returns: JSON with ranked incidents including signature, event count, blast radius (affected sources), and sample text.
Inputs: lookback_minutes, search_term, event_limit, mass_threshold, +1 more. Returns: result
find_vrops_resourcesA
Find resources in VMware Aria Operations (vROps) by name.
Useful for correlating Log Insight events with vROps monitored entities. Requires VROPS_BASE_URL to be configured.
Args: name: Resource name to search for (VM name, host name, etc.).
Returns: JSON array of matching vROps resources with IDs, names, and types.
Inputs: name (required). Returns: result
get_versionA
Get VMware Aria Operations for Logs appliance version and API surface.
Returns version info and probes key API endpoints to determine which features are available on this deployment.
Inputs: no named parameters. Returns: result
get_vrops_alertsB
Get alerts from VMware Aria Operations for specific resources.
Args: resource_ids: Comma-separated vROps resource IDs.
Returns: JSON array of alerts with severity, status, and descriptions.
Inputs: resource_ids (required). Returns: result
list_dashboardsA
List saved dashboards from Aria Operations for Logs.
Uses the legacy vRLIC API (/vrlic/api/v1/content/dashboards).
This endpoint was deprecated in Aria Operations for Logs 8.18+
and will return an empty result on newer appliances.
Inputs: no named parameters. Returns: result
query_eventsA
Search log events in VMware Aria Operations for Logs.
Args: lookback_minutes: How far back to search (default 60 minutes). search_term: Free-text search term (optional). limit: Maximum number of events to return (default 100, max 10000). field_name: Optional field constraint name (e.g. 'hostname', 'appname'). field_operator: Constraint operator (CONTAINS, NOT_CONTAINS, HAS, etc.). field_value: Constraint value.
Returns: JSON array of log events with text, source, timestamp, and fields.
Inputs: lookback_minutes, search_term, limit, field_name, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: incident detection, resource lookup, version info, alerts, dashboards, and log queries. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., detect_incidents, find_vrops_resources, query_events.
6 tools is well-scoped for a log management server, covering core log analysis and cross-product integration without being too sparse or bloated.
Essential log query and incident detection are present, but missing CRUD for dashboards and incident management, leaving notable gaps in the tool surface.
Maintenance
Related MCP Connectors
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Analytics and debugging for your MCP server — explore usage and sessions, then root-cause errors.
AI-powered incident management and server monitoring via MCP.
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server for searching and visualizing SolarWinds Observability logs, allowing users to query log data with filtering options and generate visual representations of log events over time.22,252 npm6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for intelligent log analysis providing semantic search, error pattern clustering, and smart error detection. It enables users to process, vectorize, and query local logs to efficiently identify issues and generate AI-powered summaries.MIT
- FlicenseBqualityBmaintenanceMCP server that integrates with Sumo Logic's API to perform log searches, data discovery, metrics queries, and monitoring.1544 npm-
- AlicenseNot gradedqualityDmaintenanceA server that bridges MCP-compatible clients to VMware Log Insight, enabling natural-language log querying and analysis.ISC