"How to modify local files" matching MCP servers:

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.

A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.

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 AI assistants to interact with local Docker containers, Kubernetes clusters, and system logs using the Model Context Protocol.

Enables local LLMs to perform enterprise-grade code auditing, AST security screening, architectural planning, and real-time Discord observability with zero cloud API costs.

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.

Exposes configured log files as MCP tools, enabling agents to list, query, and follow logs from local and SSH sources.

MCP server for managing UniFi Network Controllers, providing tools to read and modify network configurations, clients, devices, events, diagnostics, and backups via API key.

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

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

Enables uploading PyPTO swimlane files and querying task durations and dependencies for performance analysis with swimlane diagrams in Codex.

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 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 exposing rlg (RustLogs) log files as tools for on-call / SRE agent workflows. Three tools over JSON-RPC stdio — tail_log (last N events, filtered by level/target), filter_log (predicate filtering), summarize_errors (grouped error taxonomy). Pure Rust. MIT OR Apache-2.0.

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).

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.