"How to update an MCP configuration file" matching MCP servers:

Enables AI agents to debug and repair historical Solaris/SPARC systems by providing an out-of-band control plane with guest DTrace, QEMU monitor access, SPARC-aware GDB, host eBPF/perf tracing, and an immutable evidence ledger for cross-layer hypothesis testing.

Fetches Langfuse observability traces directly into a VS Code coding agent's context, enabling querying and viewing trace data through natural language.

Enables secure analysis of log files by listing, summarizing, and searching for error patterns, with defenses against path traversal, symlink attacks, and data leakage.

An MCP server that enables coding agents to log their work, decisions, test runs, PRs, and progress as structured events, either to a local JSONL file or an HTTP endpoint.

An MCP server implementation that enables dynamic configuration of OpenTelemetry Collectors, allowing users to add, remove, and configure receivers, processors, and exporters through MCP tools.

Enables natural language interaction with SumoLogic for log management and analytics, with contextual awareness through a configuration file that maps your environment.

Enables an AI assistant to diagnose on-premise Windows pm2-managed Node/Nitro services by answering read-only questions about deployed builds, process liveness, logs, current configuration, and whether the running process started with the configuration currently on disk.

An MCP server that demonstrates comprehensive observability with Sentry, OpenTelemetry, and Braintrust, providing tools for file, data, and HTTP operations along with real-time status and configuration resources.

Real-time analytics dashboard for Claude Code, tracking sessions, tool usage, file changes, and token costs via an MCP server.

Enables comprehensive management of Tailscale networks including device management, DNS configuration, file sharing via Taildrop, security monitoring, and network automation with built-in Grafana/Prometheus observability stack.

Analyzes how search engines and AI systems discover, crawl, cite, and convert traffic via CLI and MCP tools.

A multi-target MCP server that gives AI clients read and, when permitted, write access to Ignition 8.3 gateways across configuration, project exports, live runtime values, and an offline Ignition reference corpus. It enables browsing, explaining, diagnosing, and gated changes to gateway configuration, projects, tags, and live values through 81 tools with per-target credentials and write policies.

Enables AI assistants to query Hadoop MapReduce job history, including job listing, details, counters, configuration, and logs via the JobHistory REST API.

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

Web analytics and AI session replay for agents: visitors, breakdowns, funnels, goals, revenue attribution, and AI-found site issues. Connects to the hosted Flowsery MCP server.

Provides MCP tools to create and query SigNoz trace funnels, enabling agents to measure their own step conversion rates from within the agent loop.

MCP server for Kibana / Elasticsearch — log search, aggregations, index discovery, and dashboard browsing. Hits Elasticsearch REST API directly for log queries; falls back to Kibana Console proxy when no direct ES URL is configured. Supports ApiKey auth (best for agents), Basic auth, and anonymous access. All 5 tools are read-only (readOnlyHint: true). Returns structured JSON (outputSchema).