Business operationsPublic source

Observability MCP Server

Full-stack observability for AI agents — logs, metrics, distributed traces, alerts, incidents, SLOs, dashboards, service maps, and runbooks. 28 tools for debugging, monitoring, and incident response.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides observability capabilities through a typed MCP contract.

Architecture

How Observability MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Observability MCP Server

Validates the request and owns 28 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Observability MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Observability MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

28 named tools

query_logs

Search logs by query, time, service, level

see documentation

get_log_stats

Log volume and error rate over time

see documentation

get_errors

Recent errors with stack traces

see documentation

tail_logs

Live tail (last 50 entries)

see documentation

query_metric

Query metric time-series (CPU, latency, etc.)

see documentation

list_metrics

Available metrics for a service

see documentation

get_system_health

Current CPU/memory/disk across services

see documentation

compare_metrics

Compare metric across services or periods

see documentation

search_traces

Find traces by service, duration, status

see documentation

get_trace

Full trace with all spans and timings

see documentation

get_service_map

Service dependency graph with latencies

see documentation

get_latency_breakdown

p50/p95/p99 by operation

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

28 see documentation

Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-observability

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-observability",
    ["mcp-observability"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring