The first wave of MCP Apps shipped standalone tool surfaces, each with its own auth, routing, and conventions. That works for one app. It fails the moment a responder (an on-call engineer or an AI agent) has to move from a firing alert, to the trace that explains it, to the logs the span emitted, to the dashboard tracking the trend. Every hop loses context.

We took the opposite path. Our team built and operates OpenSearch observability as a single MCP server with shared capabilities: auth, time-and-data routing, correlation, saving, and inspectability, defined once at the server and inherited by every app. The result: 295 jobs across 15 families (triage, logs, traces, metrics, SLOs, agent observability, dashboards, ingestion, stack health) served by ~51 composable MCP apps, all sharing a universal traceId/spanId correlation pivot so context follows the responder across tools.

This talk walks through what that buys responders: faster jumps from alert to root cause, consistent auth and routing across clusters, correlation that just works, and how a five-person team ships two new apps a week without rebuilding the same plumbing.

Session details: https://events.linuxfoundation.org/agntcon-mcpcon-north-america/program/schedule/?id=1254998

Session Slides: https://sessionize.com/download/llaxgem~V1UQ4doP9hwq1YZpmgce6j.pdf~oneservermanyapps_agntcon2026.pdf