Log Insight MCP Server
Provides tools for querying logs and searching for error patterns in VMware Log Insight, enabling natural-language log analysis and retrieval.
Click on "Install 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., "@Log Insight MCP ServerShow me all error logs from the past 30 minutes"
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.
Log Insight MCP Server
A Model Context Protocol (MCP) server that connects AI assistants like Claude to VMware Log Insight, enabling natural-language log querying and analysis.
Overview
This server acts as a bridge between MCP-compatible clients (such as Claude Code or Claude Desktop) and a VMware Log Insight instance. It exposes two tools that allow an AI assistant to query and analyze logs on your behalf:
query_logs— Query logs between a start and end time, with an optional keyword filter.search_logs_for_errors— Search for error patterns (e.g.error,critical,exception,fatal,fail) within a time range.
The server manages authentication with Log Insight automatically, including session renewal and retry on expiry.
Related MCP server: grafana-mcp
Architecture
MCP Client (Claude) ──HTTP POST──▶ MCP Server (:3000) ──HTTPS──▶ Log Insight API (:9543)
│
├─ /mcp (MCP protocol endpoint)
└─ /health (health check)Key components:
File | Role |
| HTTP server, MCP session management |
| Log Insight REST API client with auth handling |
| MCP tool definitions and handlers |
Prerequisites
Node.js v18 or later
npm
A running VMware Log Insight instance accessible over the network
Local Setup
1. Clone the repository
git clone <repo-url>
cd log-insight-mcp-server2. Install dependencies
npm install3. Configure environment variables
Create a .env file in the project root (or copy and edit the existing one):
LOGINSIGHT_URL=https://your-loginsight-host
LOGINSIGHT_USERNAME=admin
LOGINSIGHT_PASSWORD=your-passwordVariable | Required | Description |
| Yes | Base URL of your Log Insight instance (e.g. |
| Yes | Log Insight user with API access |
| Yes | Password for the above user |
| No | Server port (defaults to |
The server will exit with an error if any required variable is missing.
4. Build
npm run buildThis compiles TypeScript from src/ into dist/.
5. Run
Production:
npm startDevelopment (watch mode):
npm run devThe server starts on http://localhost:3000. Verify it is running:
curl http://localhost:3000/healthConnecting an MCP Client
Claude Code
Add the server to your Claude Code MCP configuration:
{
"mcpServers": {
"log-insight": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"log-insight": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}Once connected, you can ask Claude questions like:
"Show me all logs from the last hour"
"Search for errors between 2025-01-01T00:00:00Z and 2025-01-01T12:00:00Z"
"Find any fatal or critical log entries from yesterday"
Available Tools
query_logs
Query logs within a time range.
Parameter | Type | Required | Description |
| string (ISO 8601) | Yes | Start of the time range |
| string (ISO 8601) | Yes | End of the time range |
| string | No | Text to search for in log messages |
| number (1–20000) | No | Max results to return (default: 200) |
search_logs_for_errors
Search for error-pattern logs within a time range.
Parameter | Type | Required | Description |
| string (ISO 8601) | Yes | Start of the time range |
| string (ISO 8601) | Yes | End of the time range |
| string | No | Error keyword to match (default: |
| number (1–20000) | No | Max results to return (default: 500) |
Cloud Foundry Deployment
Prerequisites
CF CLI installed and logged in (
cf login)Your Log Insight instance must be reachable from the CF environment
Push with inline variables
The Node.js buildpack automatically runs npm run build during staging, so no local pre-build is needed. Supply credentials at deploy time so they never appear in committed files:
cf push \
--var loginsight-url=https://your-loginsight-host \
--var loginsight-username=admin \
--var loginsight-password=your-passwordPush with a vars file
Alternatively, create a vars.yml file (already gitignored):
loginsight-url: https://your-loginsight-host
loginsight-username: admin
loginsight-password: your-passwordThen deploy:
cf push --vars-file vars.ymlVerify
cf app log-insight-mcp
curl https://<your-app-route>/healthScripts
Command | Description |
| Run the server |
| Run in watch mode (auto-restart on changes) |
| Compile TypeScript to |
License
ISC
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.
Latest Blog Posts
- 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/trevorputbrese/log-insight-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server