"How to set up a local environment" matching MCP servers:

Get information about the current operating environment

A 100% local development monitoring tool that captures browser console logs, network requests, and backend server output for analysis by AI assistants via MCP. It enables LLMs to debug applications by providing structured, real-time access to full-stack log data and persistent local storage.

A fail-closed MCP server for Msty Studio on macOS that provides read-only diagnostics and an optional bounded local-generation tool, without accessing chats, keys, or configuration.

Enables monitoring and analysis of local application log files with real-time tailing, error tracking, and search capabilities. Perfect for debugging Node.js applications, web servers, or any application that writes to log files through natural language commands.

MCP server enabling local network interaction, shell command execution, system resource monitoring, and SSH-based remote device management.

Enables MCP-aware AI agents to query the local machine's health over stdio, retrieving CPU, memory, disk, and load-average metrics along with boot time and the top processes by CPU usage. It gives coding agents a structured, protocol-standard way to answer questions like whether it is safe to run a build or what is currently consuming resources.

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.

Enables read-only querying of a local Grafana Loki instance, providing log search, service listing, and health check capabilities.

MCP server that stream-parses NDJSON log files without loading them into memory — filter by pattern, detect error spikes via Z-score analysis, summarize severity timelines by time window.

Enables AI coding assistants to search local log files, inspect Docker containers, and clean up JSON payloads through a local stdio MCP server.

An MCP server that provides cost and reliability observability for LLM and agent workflows. It records model calls and allows querying and aggregating telemetry data through MCP tools.

Lets Claude or any MCP client inspect a TP-Link Deco mesh locally — nodes, backhaul, clients, WAN, firmware — and carefully change settings with graded, read-back-verified writes, secrets redacted by default and an optional read-only mode. No cloud or app involved.

Enables AI assistants to access Scout Monitoring performance and error data through Scout's API. Provides traces, errors, metrics, and insights for Rails, Django, FastAPI, Laravel and other applications to help identify and fix performance issues like N+1 queries, slow endpoints, and memory bloat.

Enables AI agents to monitor Docker containers, system resources, ports, and logs in real-time.

Enables agents to inspect GPU status, size KV cache and vLLM/llama.cpp deployments, read live backend metrics, and run benchmarks over MCP.

Measures what MCP servers cost in context tokens: probes a URL or a local command now, measures a whole config file, and looks up the daily results for every server in the official MCP registry on mcpcost.ulehla.dev.

Enables agents to inspect app status, uptime, response times, incidents, and certificate/domain expiry; set up and manage monitors and status pages; and draft incident updates through authenticated MCP tools.

Uptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.

Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

Zero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment. Detects framework, running services, recent errors, git state, and provides a health diagnosis in one call.