"Understanding Call Hierarchy in Software Development or Programming" matching MCP servers:

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

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

Enables agents to govern evolving software by measuring trajectory, drift, invariants, and incidents, and by forking and measuring alternative futures before adoption.

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.

A Model Context Protocol server for the resQ emergency response system that integrates with digital twin simulations and coordination engines. It allows users to trigger simulations, generate deployment strategies, and monitor real-time drone status for incident response analysis.

A read-only MCP server for querying AI provider administration APIs, providing normalized usage, cost, and dashboard data for OpenAI and Anthropic.

MCP server that reads Spark profiler files to give accurate Minecraft server tuning advice, parsing binary protobuf directly and diagnosing TPS, MSPT, GC, heap, and call-tree issues.

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 state-aware Terraform/OpenTofu plan evaluation against live AWS topology and CloudWatch telemetry, detecting reliability blast radius and FinOps waste before merge.

Registers a set of inert, tempting decoy tools with any MCP-capable client so that any call from a hijacked or prompt-injected agent instantly raises an alert with full attack context and a per-call trace token. Also plants worthless canary tokens in honeypot files that trigger zero-false-positive leak alerts when they surface in agent output, files, or outbound requests.

Enables AI agents to raise and resolve incidents in ITOC360, triggering escalation policies that page on-call responders and closing alerts when problems clear.

Bridges Claude (or any MCP client) to manufacturing data via the i3X standard, enabling natural language queries about equipment status, hierarchy, and historical trends.

MCP server for the Wasabi WACM Connect API, enabling management of account hierarchy, storage, and billing data through Claude with 18 read-only and 12 opt-in write tools.

An MCP server connecting Claude AI with game engine runtimes (Unity & Godot) for automated testing, log filtering, and scene hierarchy inspection.

Enables AI assistants to check software end-of-life dates and support status using the endoflife.date API, providing accurate information on software lifecycle, security status, and upgrade recommendations in real-time.

Enables AI agents and MCP clients to route every tool call through configurable rules that allow, block, or hold risky actions for human approval, while recording decisions in a tamper-evident audit trail.

Enables MCP clients to interact with the current xMatters REST API over stdio, covering people, devices, groups, on-call schedules, events, incidents, workflows, services, integrations, and subscriptions. It is read-only by default and requires explicit operator opt-in plus per-call confirmation for mutations.

Enables interaction with EPICS (Experimental Physics and Industrial Control System) process variables through natural language. Supports reading PV values, setting PV values, and retrieving detailed PV information for monitoring and controlling hardware or software parameters.

Patent-pending diagnostic + decisions-ledger engine for any host software system — operator briefs and a severity-gated MCP console.

Monitors development commands and exposes terminal output to Claude in real-time, allowing AI assistants to see errors, logs, and stack traces without copy-pasting.