"A command-line fuzzy finder" matching MCP servers:

这是面向智能运维场景的 MCP 工具服务，让 Agent 能够按需检索日志内容并获取主机与应用的监控指标数据。它把实时的日志与指标证据接入 Plan-Execute-Replan 诊断流程，从而支撑自动故障排查与根因分析。

An MCP server for Grafana Loki that enables LLMs to query, tail, and analyze logs, featuring fuzzy container-name matching, compact output, and tools for log patterns, volume, and label discovery. It can run as a local stdio server or a containerized HTTP service.

First-line incident triage you can trust: ranked root-cause hypotheses where every claim cites a real evidence handle — and the agent abstains rather than guess.

A secure MCP server for Grafana that provides read-only access by default, with a separate write-capable command for mutations.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r

Enables users to log AI tool activity without conversation text and contribute back only user-approved, small-cell-suppressed counts through a local MCP interface.

Enables evidence-first incident command: investigate outages, analyze evidence, approve simulated responses, verify recovery, and export postmortems through MCP tools.

Enables AI assistants to interact with tshark and related command-line tools for live packet capture, PCAP analysis, filtering, stream following, and capture file merging.

A CLI wrapper that monitors and captures output from any running command and exposes it as an MCP server, providing tools to retrieve and search logs.

Enables AI agents to analyze, cluster, compare, and export reports from local log files through seven read-only tools, returning compact evidence packs with line-number citations instead of raw log dumps. All processing happens on the local machine, so log data never leaves the environment.

Exposes the ConnectWise Command (Continuum) ITSupport247 Reporting API as MCP tools, enabling querying of sites, devices, patches, antivirus, performance, and more.

MCP server that drives cdb.exe/kd.exe to provide WinDbg debugging to LLM agents, enabling crash dump analysis, live process debugging, kernel debugging, and a searchable command reference.

A command-line tool for monitoring and analyzing New Relic application metrics using MCP.

A command-line tool for monitoring and analyzing Coralogix logs using the Model Control Protocol, providing tools to query and summarize log data.

A lightweight, self-hostable MCP server for shared memory, structured command relay, and traceable decision evidence across AI runtimes.

Enables read-only querying and analysis of Kibana logs through a logged-in sid Cookie, including keyword/time/index searches, traceId lookups, surrounding log context, and aggregations by service, level, or host. It also validates Kibana connection status and redacts sensitive fields such as cookies, tokens, and passwords.

An MCP server for querying Grafana Loki directly with a discovery-first workflow — labels, values, series, and LogQL queries without requiring Grafana.

An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.

Provides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.

8 standalone MCP servers for SMBs — Guardrails (prompt injection, PII, secrets detection), FinOps (AI cost tracking and budgets), Observability (agent tracing), Smart Router (17+ models, 9 providers), Trust Score (governance scoring 0-100), Memory (persistent agent memory), ThinkSecure (runtime security + SOC2/GDPR audit), and A2A Lite (agent-to-agent protocol). 37 tools total, TNC credits

Tells an agent what went wrong with its own Ollama calls, in sentences with the fix: lost prompt cache and where the prompt stopped matching, context overflow, a model running partly on CPU, tool schemas crowding the prompt. Also the last turn in numbers and which local models fit in video memory. Local, read-only, nothing leaves the machine.

MCP server that diagnoses Apache Spark job failures and optimizes performance using stack-trace analysis and LLM providers, supporting EMR and local sources.

A read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.

Compares AI coding tool spend before and after a migration -- Cursor, Claude Code, GitHub Copilot, OpenCode, Codex CLI -- via an MCP server, real numbers from each vendor's own API or local logs.

Enables analysis of JVM thread dumps to detect deadlocks, CPU spikes, pool exhaustion, and virtual thread pinning, returning a health score and interactive report link.

Provides a local MCP interface to query captured, PII-scrubbed prompt telemetry from coding agents and browser chats, enabling time summaries, prompt search, and activity analysis without data leaving the machine.

Enables agents to interact with the Logflare API by writing JavaScript functions that run in a Vercel Sandbox, using three tools: search, execute_read, and execute_write.

An MCP server that connects language models to a Wazuh SIEM cluster, enabling read-only plain-language queries, schema inspection, field coverage analysis, and decoder testing.

Enables natural language queries of the Chrome UX Report API to fetch Core Web Vitals (LCP, INP, CLS, FCP, TTFB), compare form factors, benchmark pages against site averages, and analyze up to 40 weeks of performance trends.

Enables an LLM agent to investigate a Kong Gateway through fourteen read-only, schema-validated tools and a deterministic diagnostic engine, so it can trace routes, services, plugins and upstream health and explain faults such as why authentication is failing on a path. Every fact comes from the gateway itself, and the model only selects tools and writes the evidence-backed explanation.