"Managing a Database" matching MCP servers:

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 LLMs to query real job data and summarize backend job failures using MCP tools backed by a SQLite database.

An MCP server that analyzes SQL schemas, generates realistic test data, benchmarks queries, and provides optimization recommendations to improve database performance.

Enables AI assistants to interact with DataDog's observability platform through a standardized interface. Supports monitoring infrastructure, managing events, analyzing logs and metrics, and automating operations like alerts and downtimes.

MCP server for multiple databases (PostgreSQL, MySQL, MariaDB, SQLite, MongoDB, Redis) with tools for schema inspection, querying, performance diagnostics, and safe write operations, featuring access modes, PII masking, and audit logging.

Enables read-only querying and analysis of Kibana logs through a logged-in sid Cookie, including keyword/time/index searches, traceId lookups, surrounding log context, and aggregations by service, level, or host. It also validates Kibana connection status and redacts sensitive fields such as cookies, tokens, and passwords.

Provides a scalable, containerized infrastructure for deploying and managing Model Context Protocol servers with monitoring, high availability, and secure configurations.

Enables querying and managing AI logs through tools like listing logs, retrieving jobs, and performing AI-powered chat queries. Also provides access to gateway security reports and guardrail testing.

Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.

An MCP server for querying Grafana Loki directly with a discovery-first workflow — labels, values, series, and LogQL queries without requiring Grafana.

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

MCP server that diagnoses Apache Spark job failures and optimizes performance using stack-trace analysis and LLM providers, supporting EMR and local sources.

A read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.

Compares AI coding tool spend before and after a migration -- Cursor, Claude Code, GitHub Copilot, OpenCode, Codex CLI -- via an MCP server, real numbers from each vendor's own API or local logs.

Enables analysis of JVM thread dumps to detect deadlocks, CPU spikes, pool exhaustion, and virtual thread pinning, returning a health score and interactive report link.

Provides a local MCP interface to query captured, PII-scrubbed prompt telemetry from coding agents and browser chats, enabling time summaries, prompt search, and activity analysis without data leaving the machine.

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.

Ariadne's thread — a way out of the microservice maze. Local cross-service semantic chain hinter for microservices (GraphQL/HTTP/Kafka/frontend)