"How to find and read files on a computer" matching MCP servers:

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

Enables interaction with Google Cloud services including billing cost analysis, log querying, and metrics monitoring through natural language commands. Provides comprehensive tools for managing GCP resources, analyzing costs, detecting anomalies, and retrieving operational insights.

Enables safe, read-only interaction with Kubernetes clusters, allowing users to list resources and fetch logs without any create/update/delete operations.

Enables diagnosing Kubernetes clusters without creating or changing cluster objects, with tools to inspect health, workloads, events, storage, RBAC, custom resources, logs, and configuration.

MCP server that diagnoses ML model regressions by correlating drift reports, eval runs, and deploy logs, providing evidence-cited incident reports through a set of investigation tools.

Provides read-only access to OpenClaw and Codex operational data like status, tasks, sessions, logs, and Git changes. Ensures safety via redaction, allowlists, and bounded outputs.

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.

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

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

MCP server for On-Call Health burnout analysis. Connects AI assistants to your on-call data for workload insights.

Read-only MCP server for TrueNAS Scale debugging, providing k3s tools for kubectl operations and whitelisted midclt calls for system info, apps, and pools.

Enables precise measurement of live HTTP and WebSocket services while maintaining an append-only, evidence-based ledger of claims that agents can query with explicit timestamps, staleness indicators, and instructions for re-verification.

A production-oriented reliability, benchmarking, and evaluation system that layers multi-version protocol negotiation, adaptive streaming, connection pooling, and resilience onto an MCP agent runtime.

Enables agents to query GPU availability across SSH hosts, find free GPUs, list hosts, and inspect fleet status using only nvidia-smi on the remote side.

MCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.

A read-only MCP server that enables AI agents to act as GCP platform engineers, allowing them to investigate incidents, take inventory, and find cost-optimization opportunities in Google Cloud projects without mutating any infrastructure.

Enterprise AI operator evaluation MCP server. 27 tools (22 read + 5 write) for measuring, benchmarking, diagnosing, and interv ening on how human operators use AI tools across 5 canonical metrics.

Checks what local coding agents such as Claude Code, Codex and Cursor really did: files changed, commands run and test results read from test output, not the agent's word. Unclear test results can be double-checked by Laya (on your computer) or TypeSafe's Jev (cloud, your own API key). Read-only.

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 an MCP-capable agent to operate a heterogeneous cluster of Debian/Armbian Linux nodes over SSH from a single inventory, inspecting status and logs, managing packages, services, files, storage and NFS, and deploying new capabilities to nodes through installable modules. Built-in cluster tools fan out to nodes by explicit names, roles or tags with bounded concurrency, while modules can be installed on compatible nodes and run on demand or as systemd services.