by jakenuts
Integrate with SolarWinds Observability Logs for advanced log searching, visualization, and analysis—ideal for DevOps an
Connects to SolarWinds Observability to search and analyze log data with filtering and time-based visualization capabilities. Currently has limitations with structured data search.
SolarWinds Observability Logs is a community-built MCP server published by jakenuts that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with SolarWinds Observability Logs for advanced log searching, visualization, and analysis—ideal for DevOps an It is categorized under developer tools, analytics data.
You can install SolarWinds Observability Logs in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
SolarWinds Observability Logs is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
SolarWinds Observability Logs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
SolarWinds Observability Logs reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired SolarWinds Observability Logs into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated SolarWinds Observability Logs against two servers with overlapping tools; this profile had the clearer scope statement.
SolarWinds Observability Logs is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired SolarWinds Observability Logs into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated SolarWinds Observability Logs against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: SolarWinds Observability Logs is the kind of server we cite when onboarding engineers to host + tool permissions.
SolarWinds Observability Logs is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
SolarWinds Observability Logs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 65
A Model Context Protocol (MCP) server for accessing and visualizing SolarWinds Observability logs.
This server is currently incomplete as it does not support structured data search (a limitation of the REST API?). I'm uncertain if it also needs to accept a data center to use in the api endpoint calls. Will address both when time allows (needed it for a real work problem, have to fix that first)
Search SolarWinds Observability logs with optional filtering
Generate a histogram json response for of log events
solarwinds://{query}/searchsolarwinds://error/searchOptionally install from npm:
npm install -g mcp-solarwinds
Or clone and build from source:
git clone https://github.com/@jakenuts/mcp-solarwinds.git
cd mcp-solarwinds
npm install
npm run build
Or just use npx in your configurations
Add to %APPDATA%/Code - Insiders/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:
{
"mcpServers": {
"solarwinds": {
"command": "npx",
"args": ["-y", "mcp-solarwinds"],
"env": {
"SOLARWINDS_API_TOKEN": "your-api-token"
},
"autoApprove": ["search_logs", "visualize_logs"]
}
}
}
Add to the appropriate config file:
Windows: %APPDATA%/Claude/claude_desktop_config.json
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"solarwinds": {
"command": "npx",
"args": ["-y", "mcp-solarwinds"],
"env": {
"SOLARWINDS_API_TOKEN": "your-api-token"
}
}
}
}
If you encounter the ENOENT spawn npx issue on Windows, use this alternative configuration that specifies the full paths:
{
"mcpServers": {
"solarwinds": {
"command": "C:\Users\[username]\AppData\Roaming\
vm\[node-version]\
ode.exe",
"args": [
"C:\Users\[username]\AppData\Roaming\
pm\
ode_modules\
pm\bin\
px-cli.js",
"-y",
"mcp-solarwinds"
],
"env": {
"SOLARWINDS_API_TOKEN": "your-api-token"
}
}
}
}
The SolarWinds Observability MCP server requires an API token to authenticate with the SolarWinds Observability API.
There are multiple ways to provide the API token:
SOLARWINDS_API_TOKEN environment variable.env file in the project root with SOLARWINDS_API_TOKEN=your-tokenFor local testing, you can:
.env.example to .env and add your tokennode examples/local-test.jsBasic search:
{
"filter": "error"
}
Advanced search with time range and pagination:
{
"filter": "error",
"entityId": "web-server",
"startTime": "2025-03-01T00:00:00Z",
"endTime": "2025-03-05T23:59:59Z",
"pageSize": 100,
"direction": "backward"
}
Basic histogram (ASCII chart):
{
"filter": "error",
"interval": "hour"
}
Advanced visualization (ASCII chart):
{
"filter": "error",
"entityId": "web-server",
"startTime": "2025-03-01T00:00:00Z",
"endTime": "2025-03-05T23:59:59Z",
"interval": "day",
"use_utc": true
}
Claude visualization (JSON format):
{
"filter": "error",
"interval": "hour",
"format": "json"
}
The JSON format returns data that Claude can visualize as a chart:
{
"timeRanges": ["12:02", "12:03", "12:04", "12:05", "12:06", "12:07", "12:08", "12:09"],
"counts": [261, 47, 48, 48, 31, 262, 270, 33],
"total": 1000,
"queryParams": {
"query": "error",
"startTime": "2025-03-05T00:00:00.000Z",
"endTime": "2025-03-05T23:59:59.000Z"
}
}
Install dependencies:
npm install
Build the server:
npm run build
Since MCP servers communicate over stdio, debugging can be challenging. The MCP Inspector provides helpful debugging tools:
npm run debug:inspector
This will provide a URL to access the inspector in your browser, where you can:
For local testing without the MCP framework:
# Create a .env file with your token
cp .env.example .env
# Edit .env to add your token
# Run the example script
node examples/local-test.js
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.