"Understanding File Reading in Programming" matching MCP servers:

Lets an assistant read recorded production AI agent runs — steps, model and tool calls with arguments, and outcomes — along with the findings of comparison runs that checked a prompt or model change against those recordings, and verify a signed evidence bundle offline with no account or network. It is strictly read-only: no tool starts a replay or comparison, so nothing can spend money or act without a person deciding.

Enables AI assistants to query and analyze AI agent sessions from observability providers like Shepherd (AIOBS) and Langfuse, allowing users to debug agent runs, compare sessions, track performance, and analyze LLM usage patterns.

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

MCP server for reading and searching SAP Commerce Cloud (CCV2) logs stored in Azure Blob Storage, enabling log listing, retrieval, and regex search via MCP tools.

Enables remote log searching, tailing, and file reading across servers via MCP tools, with pluggable execution via SSH, pyinfra, or local commands.

MCP servers for real-time development monitoring and interactive pair programming.

Enables external CLI agents to directly operate TauriTavern via MCP, including reading runtime data, executing STScript, sending messages, switching characters, and running JavaScript diagnostics in iframes.

MCP-native agent evaluation and observability server. Log traces, evaluate output quality with 12 built-in rules (PII detection, prompt injection, cost thresholds), and track agent costs. Real-time dashboard, OTel-compatible spans. Self-hosted, MIT licensed.

Production-grade MCP Gateway in Go featuring dynamic OpenAPI tool registration, RBAC governance, in-flight PII/DLP redaction, and structured JSON audit logging.

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.

Enables AI assistants to search, summarize, and inspect Kibana/OpenSearch Dashboards logs through the user's logged-in browser session, eliminating the need for API keys or service accounts.

Enables read-only triage of Microsoft Entra ID sign-in and audit logs through fixed tools for sign-in failure analysis, user lookup, directory audits, and daily briefs.

Enables interaction with Jira Service Management Operations alerts and on-call schedules, including searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations.

Laravel Telescope-style debugging for Hono apps whose dashboard endpoint is also an MCP server: read recent exceptions with the request that produced them, recent requests filtered by status or duration, one request in full, and the slowest queries. Five read-only tools, zero runtime dependencies.

MCP server for analyzing Perfetto traces with LLMs — query .pftrace files in PerfettoSQL via Claude Code or any MCP client

Shows what is consuming your agent context window before a session starts: always-loaded skill descriptions ranked by token cost, skills installed more than once under different names, CLAUDE.md/AGENTS.md sizes including what their @import lines pull in, and MCP servers configured across clients. Read-only: no child processes, no network.

Every agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.

Lets an AI assistant answer performance questions from Tideways data by reading projects, metrics, issues and traces through the read-only REST API.

An MCP server that gives coding agents programmatic access to Sumo Logic logs via the Search Job API, enabling issue triage in preview deployments and production without leaving the editor.

A drop-in Model Context Protocol (MCP) server that lets an AI agent query PostgreSQL — read-only, enforced at the database level, with real SQL validation, timeouts, cost limits, OAuth 2.1, and an audit trail.