"Assistance with reviewing and merging code changes in a merge request" matching MCP servers:

A Model Context Protocol server that provides AI assistants access to AWS CloudWatch Logs, enabling browsing, searching, summarizing, and correlating logs across multiple AWS services.

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.

MCP server that provides read-only analysis of Claude Code session transcripts, enabling queries about project activity, session details, and tool usage.

A Model Context Protocol server for Zoho Site24x7 that uses a JavaScript sandbox to execute API calls, enabling management of monitors, accounts, and MSP/BU tenancy through natural language.

Maintenance, recovery, and observability for Claude Code. CLI + MCP server + dashboard.

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.

Echo tool MCP server that extracts and logs W3C Trace Context from requests to verify propagation from Claude Code.

Surface Claude Code token usage, estimated cost, and plan-limit status in any MCP client. Enables agents to query usage data from local logs and Anthropic API.

Claude Code token usage and cost visibility for MCP-capable agents.

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.

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.

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

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.

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 an AI assistant to diagnose a broken application on a local Kubernetes cluster by inspecting pods, events, and logs, with server-side guardrails, least-privilege RBAC, and an audit log. It can also restart deployments in allowed namespaces only after a dry-run preview and host approval.

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 natural language analysis of network packet captures, including protocol detection, flow analysis, and security threat identification, integrated with AI assistants.

Provides governed MCP tools for querying optionally restricted Microsoft Sentinel/Log Analytics tables and optional Defender XDR hunting data, retrieving incidents and entities, and—for agent identities only—adding attributed incident comments, with Entra ID authentication, KQL validation, rate limits, and redacted audit logging.

Enables MCP clients to query and triage security findings published to BigQuery and correlate them with execution, sandbox, and diagnostic traces in Cloud Logging. Exposes tools, resources, and prompts for filtering issues by severity, status, repository, or CWE, retrieving patch diffs and verification results, and diagnosing why a remediation or verification run failed.